[OASIS Issue Tracker] (TOSCA-190) Fix grammar for "Constraints" on a Target node of a requirement (Chapter 11)

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

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

Matthew Rutkowski  commented on TOSCA-190:
------------------------------------------

Jacques: Are the filter expressions an <or> semantic (either or?) if multiple options exist?  We need to express combinations at some point.
Derek: allow target filter to allow multiple, could use conjunctive logic in some way.  Current interp. is it is a conjunction.  Filters <could> be named at some point
Jacques: evolutionary approach can be taken.  
Matt: perhaps advantage a regex. (as we have loosely defined so far as an allowed constraint clause)
Derek: as long as the domain of the property is usable (accessible) to expression it should be allowed.
Jacques: if only 1 property is truly needed, need a way to express this (or even 1 from an allowed set of values).

> Fix grammar for "Constraints" on a Target node of a requirement  (Chapter 11)
> -----------------------------------------------------------------------------
>
>                 Key: TOSCA-190
>                 URL: https://issues.oasis-open.org/browse/TOSCA-190
>             Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
>          Issue Type: Task
>          Components: Profile-YAML
>    Affects Versions: CSD03
>            Reporter: Matthew Rutkowski 
>            Assignee: Thomas Spatzier 
>            Priority: Critical
>
> Section 11  of WD03, Rev05 has the following example which shows constraints on a requirement.  The intent is to constrain the properties used for finding/matching the Target (Compute) node of a relationship.  If we still want to allow this, we have no grammar for doing this and need one. Also, the grammar implied by the example perhaps is not sufficient to indicate that these constraints are on the properties of the Target node.  
> Here is the example as written:
> node_templates:
>   mysql:
>     type: tosca.nodes.DBMS.MySQL
>     properties:
>       # omitted here for sake of brevity
>     requirements:
>       - host: tosca.nodes.Compute
>         constraints:
>           - num_cpus: { in_range: [ 1, 4 ] }
>           - mem_size: { greater_or_equal: 2 }
>           - os_arch: x86_64
>           - os_type: linux
>           - os_distribution: ubuntu



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