implementedby sdd 1.1 proposal. current situation sdd runtime “walks” resources in topology...

8
ImplementedBy SDD 1.1 Proposal

Upload: lionel-scott

Post on 13-Dec-2015

212 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: ImplementedBy SDD 1.1 Proposal. Current Situation SDD runtime “walks” resources in topology Resources are cataloged and cross referenced w/ profile(s)

ImplementedBy

SDD 1.1 Proposal

Page 2: ImplementedBy SDD 1.1 Proposal. Current Situation SDD runtime “walks” resources in topology Resources are cataloged and cross referenced w/ profile(s)

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

Page 3: ImplementedBy SDD 1.1 Proposal. Current Situation SDD runtime “walks” resources in topology Resources are cataloged and cross referenced w/ profile(s)

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

Page 4: ImplementedBy SDD 1.1 Proposal. Current Situation SDD runtime “walks” resources in topology Resources are cataloged and cross referenced w/ profile(s)

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

Page 5: ImplementedBy SDD 1.1 Proposal. Current Situation SDD runtime “walks” resources in topology Resources are cataloged and cross referenced w/ profile(s)

Proposed SchemaIn 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>

Page 6: ImplementedBy SDD 1.1 Proposal. Current Situation SDD runtime “walks” resources in topology Resources are cataloged and cross referenced w/ profile(s)

Proposed Schema

Page 7: ImplementedBy SDD 1.1 Proposal. Current Situation SDD runtime “walks” resources in topology Resources are cataloged and cross referenced w/ profile(s)

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>

Page 8: ImplementedBy SDD 1.1 Proposal. Current Situation SDD runtime “walks” resources in topology Resources are cataloged and cross referenced w/ profile(s)

Actions if approved

• Minor schema change• Specification update to document the new

attribute