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

Chris Lauwers commented on TOSCA-201:
-------------------------------------

The rationale behind requirements and capabilities makes perfect sense, but it doesn't clarify the distinction between properties on node types vs. properties on capabilities. In Compute nodes, for example, what is it about "mem_size" that makes it a property of the node itself, whereas "architecture" is a property of the os capability of the node. If there is a "best practice" that drives the distinction, then perhaps we need to clarify that "best practice".

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