[OASIS Issue Tracker] (TOSCA-197) Add "requirements" section in nested templates

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

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

Matthew Rutkowski  commented on TOSCA-197:
------------------------------------------

If we effectively create a nested template (which is essentially a virtual node type) it should have all the keynames / features of a node type (in this case requirements).

See TOSCA-186 which is the master issue for this

> Add "requirements" section in nested templates
> ----------------------------------------------
>
>                 Key: TOSCA-197
>                 URL: https://issues.oasis-open.org/browse/TOSCA-197
>             Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
>          Issue Type: Improvement
>          Components: Profile-YAML
>            Reporter: Chris Lauwers
>            Priority: Minor
>
> Nested templates have a "capabilities" section that specifies which capabilities should be exposed by the nested template. For symmetry reasons, there should also be a "requirements" section that specifies which requirements need to be fulfilled by components external to the nested template.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)