[OASIS Issue Tracker] (TOSCA-140) CSD04 - Constraining the capabilities of multiple node templates

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

     [ https://issues.oasis-open.org/browse/TOSCA-140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matthew Rutkowski  updated TOSCA-140:
-------------------------------------

    Summary: CSD04 - Constraining the capabilities of multiple node templates  (was: CSD03 - Constraining the capabilities of multiple node templates)

> CSD04 - Constraining the capabilities of multiple node templates
> ----------------------------------------------------------------
>
>                 Key: TOSCA-140
>                 URL: https://issues.oasis-open.org/browse/TOSCA-140
>             Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
>          Issue Type: New Feature
>          Components: Profile-YAML
>    Affects Versions: CSD1
>         Environment: Derek to review, see if can be updated to reflect current spec/approach/thinking.
>            Reporter: Derek Palma
>            Assignee: Derek Palma
>             Fix For: CSD04
>
>
> In section 12 Grouping Node Templates, a membership construct is used to associate scaling constraints to node template instances. This construct has the following weaknesses:
> 1)	The members are not constrained, i.e. the types of the members are not specified
> 2)	The constraints enforced on the members are not defined. I.e. there is no reference to or ability to infer a schema for the constraints
> A "type" approach which supports strong validation is more desirable. So far we have this for other aspects of the DSL so why not strive for strong validation for this construct too. 



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