[OASIS Issue Tracker] (TOSCA-201) Harmonize Properties and Capabilities in Node Types

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

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

Matthew Rutkowski  commented on TOSCA-201:
------------------------------------------

In the requirement, we are fundamentally asking for a named feature as a Capability, the chosen exported properties of the capability can never be required apart from the Capability. The anchor of the relationship is to the capability not its properties.  Requirements and Capabilities are fundamental to TOSCA and part of v1.0.  Properties were added to capabilities later as it was desired to have features be moveable and allowed to decorate nodes.  In addition, constraints were only for properties on nodes and no we had to add a node filter to allow the same concept to be applied to properties of capabilities.   Nodes, Caps/Req and properties will remain in schema.  It is for us to give best practice and provide normative types to show how we intend them to be used. 


> Harmonize Properties and Capabilities in Node Types
> ---------------------------------------------------
>
>                 Key: TOSCA-201
>                 URL: https://issues.oasis-open.org/browse/TOSCA-201
>             Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
>          Issue Type: Improvement
>          Components: Profile-YAML
>            Reporter: Chris Lauwers
>            Priority: Minor
>
> It appears that both Properties and Capabilities are used to map Node Types to requirements without any clear distinction between the two mechanisms. Or, said a different way, both Properties and Capabilities are used to express the capabilities of node types. We should simplify things by harmonizing these two approaches and settle on one single way to express capabilities (e.g. by doing away with Properties on Node Types and only using Capabilities). 



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