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-136

OPEN - CSD04 - Need rules to assure non-collision (uniqueness) of requirement or capability names

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: CSD1
    • Fix Version/s: None
    • Component/s: Profile-YAML
    • Labels:
      None
    • Resolution:
      Hide

      Fixed in v1.2 CSD01

      Show
      Fixed in v1.2 CSD01

      Description

      When defining node types/templates we allow authors to defined named requirements (or capabilities). How do we prevent (name) collision if we allow others to augment a type or template definition with their own requirements or capabilities?

      For example,with the following node template:

      node_templates:
      mysql:
      type: tosca.nodes.MySQL
      properties:
      mysql_root_password:

      { get_input: my_mysql_rootpw }

      mysql_port:

      { get_input: my_mysql_port }

      requirements:

      • host: db_server

      What happens of a second named requirement of "host" is added?

      What happens if a new Node Type that derives from MySQL is created and attempts to use the requirement name "host" which is already defined on the MySQL type?


      Need prose and/or examples to discuss if these are errors or are side effects created (such as "choice" of "host".


      In relation to this last thought, another bug will be opened in JIRA to ask this question.

        Attachments

          Activity

            People

            • Assignee:
              spzala Sahdev Zala
              Reporter:
              mrutkows Matthew Rutkowski
            • Watchers:
              2 Start watching this issue

              Dates

              • Due:
                Created:
                Updated: