[OASIS Issue Tracker] (TOSCA-186) DEFER - model composition (Nested templates)

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

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

Thomas Spatzier  commented on TOSCA-186:
----------------------------------------

Yes, I am postulating the need for substitutability. We have implemented this based on TOSCA v1.0 and find this a very powerful concept.

And again, your nested node templates proposal is incomplete in my opinion, since all the mappings of the top-level node's properties, attributes, requirements and capabilities (and operations in the furture - TOSCA-194) is missing. If this is added, the proposal will be a lot more invasive into current TOSCA simple profile syntax than the current proposal.
The current proposal leaves all existing concepts untouched and "just" adds the new top-level mapping mechanisms, which as I said could well be in its own file.

BTW, in you first comment and in last Tuesday's call you said you would want the nested template designed in a way that its use as a nested template is transparent (e.g. by not having to introduce new top level keywords). I claim that the your proposal with the nested node_templates sections misses this goal more than the original proposal, since using that template standalone would be completely confusing.

> 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
(v6.2.2#6258)