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

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

I uploaded an initial draft as WD04, Rev09 based on Matt's last version:
https://www.oasis-open.org/apps/org/workgroup/tosca/download.php/54624/latest

That's what we discussed in the YAML WG call on Nov 25th 2014. Quick summary of the proposal:
- introduce topology_template top-level section
- move node_templates under topology_template
- move inputs and outputs under topology_template (really only makes sense for topology template)
- add substitution information under topology_template (substitutable_node_type, exposed_capabilities, exposed_requirements)

topology_template is the entity from which applications can be deployed.
a node template can be substituted by a complete topology_template -> nesting

Some open issues that came up during call:
1) renaming inputs/outputs to properties/attributes to only have one concept.
2) do we need intrinsic functions to dig into nested structures (to a certain level)

Please all have a look at the current draft proposal in the linked document and provide feedback. Goal is to agree on a proposal in next week's call so the edits can be completed (with option to defer additional detail issues).

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