OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

tosca message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


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


Luca Gioppo created TOSCA-253:
---------------------------------

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


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)


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]