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] (TOSCA-186) DEFER - model composition (Nested templates)

    [ https://issues.oasis-open.org/browse/TOSCA-186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=52941#comment-52941 ] 

Thomas Spatzier  commented on TOSCA-186:

There was some discussion in the YAML WG call on December 9th about different substitution scenarios (whole tier substitution vs. partial substitution). I tried to outline those in two diagrams:


From my perspective, the current proposal covers at least the first scenario. I also think, the second scenario is covered, provided there are appropriate node types that expose the right set of requirements and capabilities for correct wiring in the outer context.

It was discussed whether we need some way of overriding requirement/capability binding in the substituting template, but in my opinion that should be treated as a new features and be handled post CSD02.

> DEFER - model composition (Nested templates)
> --------------------------------------------
>                 Key: TOSCA-186
>                 URL: https://issues.oasis-open.org/browse/TOSCA-186
>             Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
>          Issue Type: Improvement
>          Components: Profile-YAML, Spec - Simple Profile
>            Reporter: Shitao Li
>            Assignee: Thomas Spatzier 
> In TOSCA 1.0, it defined the composition of service templates(clause 3.5), which allow a service template to be used as a node template in another service template. 
> In many cases, this is very important and useful feature, especially when describe the complicated service.
> However, in TOSCA-simple-profile-YAML, it seems that this feature does not support.

This message was sent by Atlassian JIRA

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