1 / 4

Node Type Implementations

Node Type Implementations. How does Required Container Feature interact with Artifact T ype?

shalom
Download Presentation

Node Type Implementations

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. Node Type Implementations How does Required Container Feature interact with Artifact Type? • It seems that any given implementation will be based on artifacts of various types and the container must be able to support executing them. Node Type Implementations include RequiredContainerFeatures, but this is not used in the examples. As it stands today, it seems to be implying one or all of the following assumptions: • You have to look at both the artifact types and the required container features to determine if a node type implementation is actually supported • There isn’t any normative set of required container features.

  2. Artifact Types and RequiredContainerFeatures xyz Impl Chef Cookbook Node Type Chef Impl Script Impl Script execution

  3. What are normative container features? <RequiredContainerFeatures> <RequiredContainerFeature feature="local.linux.script.execution"/> </RequiredContainerFeatures> <RequiredContainerFeatures> <RequiredContainerFeature feature="opscode.chef.cookbook.adhoc"/> </RequiredContainerFeatures>

  4. RequiredContainerFeature • RequiredContainerFeatures: An implementation of a Node Type might depend on certain features of the environment it is executed in, such as specific (potentially proprietary) APIs of the TOSCA container. For example, an implementation to deploy a virtual machine based on an image could require access to some API provided by a public cloud, while another implementation could require an API of a vendor-specific virtual image library. Thus, the contents of the RequiredContainerFeatures element provide “hints” to the TOSCA container allowing it to select the appropriate Node Type Implementation if multiple alternatives are provided. Each such dependency is defined by a separate RequiredContainerFeature element.The RequiredContainerFeature element has the following properties: feature: The value of this attribute is a URI that denotes the corresponding needed feature of the environment.

More Related