OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

tosca message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [OASIS Issue Tracker] Commented: (TOSCA-5) Support of <ImplementationArtifacts> within <NodeTemplate> element

    [ http://tools.oasis-open.org/issues/browse/TOSCA-5?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=29777#action_29777 ] 

Frank Leymann  commented on TOSCA-5:

Thomas and I worked on a new Redline Version as requested by the TC. We realized that TOSCA-5 depends on the resolution for TOSCA-4, which introduces the distinction between deployment artifacts and implementation artifacts. Thus, we suggest to defer the resolution of TOSCA-5 until TOSCA-4 has been resolved. 

> Support of <ImplementationArtifacts> within <NodeTemplate> element
> ------------------------------------------------------------------
>                 Key: TOSCA-5
>                 URL: http://tools.oasis-open.org/issues/browse/TOSCA-5
>             Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
>          Issue Type: Improvement
>          Components: Spec
>            Reporter: Frank Leymann 
>            Assignee: Frank Leymann 
> Today, a <NodeType> element supports the definition of <DeploymentArtifacts> representing executable entities of the node type itself. These deployment artifacts may be overridden or extended or provided first time by another <DeploymentArtifact> element of the referencing <NodeTemplate>.
> This mechanism should be supported for <ImplementationArtifacts> too: A node type may define the implementation artifacts for its operations, but a node template derived from this node type should be able to actually provide an implementation artifact, override an implementation artifact or extend the set of implementation artifacts. For this purpose, the proposal is to add an <ImplementationArtifacts> element to the <NodeTemplate> element as sibling of the <DeploymentArtifacts> element. 

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]