[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=51667#comment-51667 ] 

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

My personal view on issues #1 and #2 above:

#1: IMO, inputs and outputs are more intuitive at topology_template level, especially when used standalone. It is not properties or attributes of the topology, but input that gets mapped to properties of contained nodes (by intrinsic function), or outputs mapped from attributes of nodes.
Only in case of nesting, inputs and outputs get mapped to properties/attributes of the substituted node, but this should not affect syntax of the topology template itself.

#2: Everything within one service template (incl. plans) only has access to the information available in that context. For nesting, only the abstraction level of the substituted node is available in the current context. So I don't think there is a need to dig deeper, but keep encapsulation.

> 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)