[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=50273#comment-50273 ] 

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

Properties are NOT used to map Node Types to one another.  Requirements is a tuple that maps to Node Types (or templates) as a general "capability", and optionally a specific named capability (within the node identified) and lastly identifies the relationship to use (when it is necessary to make it explicit. 

Properties are NOT used to express the capabilities of Node Types.  The Node Type name (fully qualified URI) implies its capabilities, properties are the normative settings/parameters that help provide input to the orchestrator as to its desires state once deployed.

Capabilities, again by name, imply a feature set which may or may NOT have properties.

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