Uploaded image for project: 'OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC'
  1. OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
  2. TOSCA-223

Need a mechanism to express cardinality on a Requirement

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: Closed
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: CSD2
    • Fix Version/s: CSD03
    • Component/s: Profile-YAML
    • Labels:
      None
    • Resolution:
      Hide

      The Requirement definition now includes the keyname "occurrences" for cardinality expression which allows a range to be declared. The default is [1,1].

      The update appears around WD5, Rev.8.

      Show
      The Requirement definition now includes the keyname "occurrences" for cardinality expression which allows a range to be declared. The default is [1,1] . The update appears around WD5, Rev.8.

      Description

      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 ]

        Attachments

          Activity

            People

            • Assignee:
              thomas.spatzier Thomas Spatzier (Inactive)
              Reporter:
              mrutkows Matthew Rutkowski (Inactive)
            • Watchers:
              1 Start watching this issue

              Dates

              • Due:
                Created:
                Updated: