Uploaded image for project: 'OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC'
  1. OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
  2. TOSCA-34

Section/Appendix: Mapping Service Template data to OVF Envelope Elements

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: New
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Primer
    • Labels:
      None
    • Proposal:
      Hide

      An ovfRef type DeploymentArtifact should contain a sub-element <reference> referring to an OVF package.
      If all the virtual resources in the referenced OVF Package are used to instantiate a node only, then a <reference> element is sufficient to supply all information needed for instantiating the node. However, an OVF package may contain some other virtual system elements that are used for instantiating other nodes specified in TOSCA Service Template.
      For example, a web service is supported by an appserver and a DB server. Two VM images are used to deploy these two servers, one image installing Linux OS and Tomcat and the other one installing Linux OS and MySQL. These two images are described by a VirtualSystemCollection element in an OVF descriptor file and included in one OVF package. Developers define two node types in TOSCA for the appserver and DB server respectively. But these two node types reference the same OVF package as the deployment artifact. In this case, element < VirtualArtifacts > should be given in the body of DeploymentArtifact. Developers should give the ID of VirtualSystem or VirtualSystemCollection in <VirtualArtifacts> to specify images for deploying the node. When the OVF package is imported, only the virtual systems that are included in <VirtualArtifacts> are deployed. An example is given below.

      <NodeTypes>
      <NodeType id="appServer" name="My Application Server">
      <DeploymentArtifacts>
      <DeploymentArtifact name=" VM image with Linux and Tomcat "
      type="http://docs.oasis-open.org/tosca/ns/2011/12/deploymentArtifacts/ovfRef">
      <Reference> http://www.example.com/ovfpackage/ovf_example</Reference>
      <VirtualArtifacts>
      <VirtualArtifact>virtualSystem_appserver</VirtualArtifact>
      <VirtualArtifacts>
      </DeploymentArtifact>
      </DeploymentArtifacts>
      </NodeTypes>

      <NodeTypes>
      <NodeType id="dbServer" name="My DB Server">
      <DeploymentArtifacts>
      <DeploymentArtifact name="VM image with Linux and mySQL"
      type="http://docs.oasis-open.org/tosca/ns/2011/12/deploymentArtifacts/ovfRef">
      <Reference> http://www.example.com/ovfpackage/ovf_example</Reference>
      <VirtualArtifacts>
      <VirtualArtifact> virtualSystem_dbserver </VirtualArtifact>
      <VirtualArtifacts>
      </DeploymentArtifact>
      </DeploymentArtifacts>
      </NodeTypes>

      Show
      An ovfRef type DeploymentArtifact should contain a sub-element <reference> referring to an OVF package. If all the virtual resources in the referenced OVF Package are used to instantiate a node only, then a <reference> element is sufficient to supply all information needed for instantiating the node. However, an OVF package may contain some other virtual system elements that are used for instantiating other nodes specified in TOSCA Service Template. For example, a web service is supported by an appserver and a DB server. Two VM images are used to deploy these two servers, one image installing Linux OS and Tomcat and the other one installing Linux OS and MySQL. These two images are described by a VirtualSystemCollection element in an OVF descriptor file and included in one OVF package. Developers define two node types in TOSCA for the appserver and DB server respectively. But these two node types reference the same OVF package as the deployment artifact. In this case, element < VirtualArtifacts > should be given in the body of DeploymentArtifact. Developers should give the ID of VirtualSystem or VirtualSystemCollection in <VirtualArtifacts> to specify images for deploying the node. When the OVF package is imported, only the virtual systems that are included in <VirtualArtifacts> are deployed. An example is given below. <NodeTypes> <NodeType id="appServer" name="My Application Server"> <DeploymentArtifacts> <DeploymentArtifact name=" VM image with Linux and Tomcat " type="http://docs.oasis-open.org/tosca/ns/2011/12/deploymentArtifacts/ovfRef"> <Reference> http://www.example.com/ovfpackage/ovf_example </Reference> <VirtualArtifacts> <VirtualArtifact>virtualSystem_appserver</VirtualArtifact> <VirtualArtifacts> </DeploymentArtifact> </DeploymentArtifacts> </NodeTypes> <NodeTypes> <NodeType id="dbServer" name="My DB Server"> <DeploymentArtifacts> <DeploymentArtifact name="VM image with Linux and mySQL" type="http://docs.oasis-open.org/tosca/ns/2011/12/deploymentArtifacts/ovfRef"> <Reference> http://www.example.com/ovfpackage/ovf_example </Reference> <VirtualArtifacts> <VirtualArtifact> virtualSystem_dbserver </VirtualArtifact> <VirtualArtifacts> </DeploymentArtifact> </DeploymentArtifacts> </NodeTypes>

      Description

      In the TOSCA specification, "if the type attribute of Deployment Artifact contains the value http://docs.oasis-open.org/tosca/ns/2011/12/deploymentArtifacts/ovfRef, the body will contain an XML fragment with a reference to an OVF package and a mapping between service template data and elements of the respective OVF envelope." The specification does not make it clear how to map the service template data to elements of OVF envelope. I suggest standardizing the body of Deployment Artifact for the ovfRef type artifact.

        Attachments

          Activity

            People

            • Assignee:
              zhangchuxiong Aaron Zhang (Inactive)
              Reporter:
              PaulZhang Paul Zhang
            • Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated: