[OASIS Issue Tracker] (TOSCA-223) Need a mechanism to express cardinality on a Requirement

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

Matthew Rutkowski  created TOSCA-223:
----------------------------------------

             Summary: Need a mechanism to express cardinality on a Requirement
                 Key: TOSCA-223
                 URL: https://issues.oasis-open.org/browse/TOSCA-223
             Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
          Issue Type: New Feature
          Components: Profile-YAML
    Affects Versions: CSD2
            Reporter: Matthew Rutkowski 
            Assignee: Thomas Spatzier 
            Priority: Minor
             Fix For: CSD03


It has been proposed that Requirements have cardinality. 

Even our Tosca "Root" node has a built-in requirement that should have a [0-n] cardinality; as it reads now, this requires a "dependency" to be fulfilled for EVERY TOSCA node that has derived from it.  Either we remove it, add a [0,n] cardinality <or> both:

tosca.nodes.Root:
  description: The TOSCA Node Type all other TOSCA base Node Types derive from
  attributes:
    tosca_id:
      type: string
    tosca_name:
      type: string
  requirements:
    - dependency:
        node: tosca.capabilities.Root
  interfaces: [ tosca.interfaces.node.lifecycle.Standard ] 




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