1 / 8

N10 Profile Revisit

N10 Profile Revisit. SDD 1.1 Proposal. Current Situation. Profiles are an incomplete subset of a resource model Incompletion causes confusion How does one extend a profile? Which resources should come from a resource model?

lester
Télécharger la présentation

N10 Profile Revisit

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. N10 Profile Revisit SDD 1.1 Proposal

  2. Current Situation • Profiles are an incomplete subset of a resource model • Incompletion causes confusion • How does one extend a profile? • Which resources should come from a resource model? • Which resources have to be defined that do not exist in a resource model? • When is it appropriate to use a particular resource, extend a resource or add a new resource?

  3. Scenario(s)/Use Case(s) • Basic use case • The starter profile includes a resource class called CIM_InstalledProduct • An SDD author needs to declare a resource in topology and reference a property of that resource in a constraint • The resource to be declared does not have a corresponding resource class in the profile • Does the SDD author extend the profile or use CIM_InstalledProduct?

  4. Proposal • Do away with the profile in it’s current form • Use the resource model directly • Reference the resource model in namespace declarations • Use and/or extend the resource model using prescribed methodologies as defined by that model

  5. Proposal • Keep the concept of the profile as a contract between producer and consumer • Reference the profile type/serial number in the SDD but not elements of the profile • Publish a known set of profiles (for producers and consumers) • Implementations refer to profile serial numbers and cross reference with declarations in the SDD to determine compatibility • Vice versa for authoring tools

  6. Proposed Schema • Add a ProfileIDType to sdd-common <xsd:complexType name="ProfileIDType"> <xsd:sequence> <xsd:element name="ProfileID" type="xsd:string" maxOccurs="unbounded"/> <xsd:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/> </xsd:sequence> </xsd:complexType> • Reference ProfileIDType in the deployment descriptor … <xsd:element name="DeploymentDescriptor" type="sdd-dd:DeploymentDescriptorType"/> <xsd:element name="ProfileID" type="sdd-dd:ProfileIDType"/> …

  7. Proposal • The profile needs to be amended as well • What is needed in the profile? • Resource model definition • Resource names used • Properties used • To do, draft the amended profile and disseminate

  8. Proposed Specification Change • To do

More Related