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


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

Luca Gioppo commented on TOSCA-253:
-----------------------------------

Reference to the discussion in the last TC meeting
Luca: issue on the semantic of the standard. "Capability" need properties read-only. But also used to set properties. Should not be allowed. Capability is overused here.

scribe (Jacques): Luc: property on the node vs. directly in the capability, not much difference.

scribe (Jacques): Luca: orchestrator implementation issue. Makes impl more complicated.

scribe (Jacques): Luc: but more usable to use prop directly in capability...

scribe (Jacques): Derek: capabilities are reusable semantics, at node design time. Useful to have Capabilities include properties.

scribe (Jacques): Discussion still open.

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


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