[OASIS Issue Tracker] (TOSCA-141) CSD04 - Specifying Environment Constraints for Node Templates (Policy related)

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

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

Matthew Rutkowski  updated TOSCA-141:
-------------------------------------

          Summary: CSD04 - Specifying Environment Constraints for Node Templates (Policy related)  (was: REVIEW - WD02 - Specifying Environment Constraints for Node Templates (Policy related))
    Fix Version/s: CSD04

> CSD04 - Specifying Environment Constraints for Node Templates (Policy related)
> ------------------------------------------------------------------------------
>
>                 Key: TOSCA-141
>                 URL: https://issues.oasis-open.org/browse/TOSCA-141
>             Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
>          Issue Type: Bug
>          Components: Profile-YAML
>            Reporter: Derek Palma
>            Assignee: Derek Palma
>             Fix For: CSD04
>
>
> In section 12 Grouping Node Templates, a membership construct is used to associate a TOSCA runtime constraint (a capability not provided by the nodes in the service template but by the environment that is processing it) to a set of node templates, the subjects of the constraint.
> The specific use cases is an anti-colocation constraint to ensure two SoftwareComponents are not placed on the same Compute node which is certainly a valid and common use case.
> My concern with the proposed syntax is that is that it is not able to support strong validation. This construct should capture the following semantics:
> 1)	The capability of the TOSCA Runtime to be applied (constrained)
> 2)	The subjects of the action implied by the declarative constraint



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