[OASIS Issue Tracker] Updated: (TOSCA-136) WD01 - Need rules to assure non-collision (uniqueness) of requirement or capability names

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

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

Matthew Rutkowski  updated TOSCA-136:
-------------------------------------

    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. 


  was:
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:



> WD01 - Need rules to assure non-collision (uniqueness) of requirement or capability names
> -----------------------------------------------------------------------------------------
>
>                 Key: TOSCA-136
>                 URL: http://tools.oasis-open.org/issues/browse/TOSCA-136
>             Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
>          Issue Type: Improvement
>          Components: Profile-YAML
>    Affects Versions: CSD1
>            Reporter: Matthew Rutkowski 
>            Assignee: Thomas Spatzier 
>             Fix For: CSD1
>
>
> 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. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira