1 / 8

ImplementedBy

ImplementedBy. SDD 1.1 Proposal. Current Situation. SDD runtime “walks” resources in topology Resources are cataloged and cross referenced w/ profile(s) If a resource in topology is encountered that is not referenced in a profile, the runtime aborts. Scenario(s)/Use Case(s) .

zarita
Download Presentation

ImplementedBy

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. ImplementedBy SDD 1.1 Proposal

  2. Current Situation • SDD runtime “walks” resources in topology • Resources are cataloged and cross referenced w/ profile(s) • If a resource in topology is encountered that is not referenced in a profile, the runtime aborts

  3. Scenario(s)/Use Case(s) • SDD producer may want to type cast a resource for future management ops but use generic properties at deployment time • Example: A producer wants to deploy a database system and there is a need post-deployment to identify that resource as a database system. However, at install time the only property needed is install location

  4. Proposal • Allow SDD producers to type cast resources • Add an optional attribute to ResourceType • Call the attribute implementedBy and have it be an IDREF to another hosted resource in topology

  5. Proposed Schema In sdd-common add the following <xsd:complexType name="ResourceType"> <xsd:sequence> <xsd:group ref="sdd-dd:DescriptionGroup" minOccurs="0"/> <xsd:element name="Name" type="sdd-dd:ElementValueType" minOccurs="0" /> <xsd:element name="Property" type="sdd-dd:PropertyType" minOccurs="0" maxOccurs="unbounded"/> <xsd:element name="HostedResource" type="sdd-dd:ResourceType" minOccurs="0" maxOccurs="unbounded"/> <xsd:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/> </xsd:sequence> <xsd:attribute name="id" type="xsd:ID" use="required"/> <xsd:attribute name="type" type="sdd-dd:ResourceTypeNameType" use="required"/> <xsd:attribute name="implementedBy" type="xsd:IDREF" use="optional"/> <xsd:anyAttribute namespace="##other" processContents="lax"/> </xsd:complexType>

  6. Proposed Schema

  7. Example <sdd-dd:Topology> <sdd-dd:Resource id="os" type="sp:CIM_OperatingSystem"> <sdd-dd:HostedResource id="DatabaseServer" type="sp:CIM_DatabaseSystem"> <sdd-dd:HostedResource id="SimpleDatabase" type="sp:CIM_CommonDatabase" implementedBy="OSInstallofDBProduct" /> </sdd-dd:HostedResource> <sdd-dd:HostedResource id="OSInstallofDBProduct" type="sp:CIM_InstalledProduct"/> </sdd-dd:Resource> </sdd-dd:Topology>

  8. Actions if approved • Minor schema change • Specification update to document the new attribute

More Related