[OASIS Issue Tracker] (TOSCA-253) capability instead of property in Compute

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

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

Matthew Rutkowski  commented on TOSCA-253:
------------------------------------------

The design of the Compute node is a intended.  The properties inside the capabilities that are declared on the Compute node (as any other node) are an extension of properties of the node itself.

Working as designed.

> capability instead of property in Compute
> -----------------------------------------
>
>                 Key: TOSCA-253
>                 URL: https://issues.oasis-open.org/browse/TOSCA-253
>             Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
>          Issue Type: Bug
>          Components: Profile-YAML
>    Affects Versions: CSD03
>            Reporter: Luca Gioppo
>            Priority: Critical
>              Labels: misinterpretation
>
> In example H.1.2.4, but in general in all the specification the Compute node has not properties and the properties inside the Capability definition are used, but this does not respect the spcification where the "expected state is written in the property section" the Capability just state that that node offer the capability of being a host and having a OS but should not used in place of "state" declaration



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