[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=52840#comment-52840 ] Chris Lauwers commented on TOSCA-186: ------------------------------------- As per our discussion in Tuesday's meeting, I reworked Chapter 13 to reflect nesting of node templates (rather than substitution of topology templates). The document can be found at https://www.oasis-open.org/apps/org/workgroup/tosca/download.php/54676. As you'll see, this proposal eliminates all the mapping mechanics from the original proposal. Instead, it introduces the need for one or two additional model navigation functions. I did not make an attempt to design these functions. Instead, i left comments in the documents where those functions are required. I don't believe any other changes are required (i.e. no changes to Node Types, Relationship Types, etc.) > 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)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]