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-161) WD02 - Need examples of using the built-in feature (Capability) and dependency (Requirement) of tosca.nodes.Root


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

Matthew Rutkowski  edited comment on TOSCA-161 at 8/28/14 5:14 PM:
-------------------------------------------------------------------

Hi Luc,

In terms of the definition, it is correct using our existing semantics, as a requirement is fulfilled either by a Node Type (which has implicit capabilities) or a an explicit Capability which is included on a Node Type.   I believe the "gap" is that no where do we say (nor in schema can we prove) that a Node Type represents a a packaged set of Capabilities.  This is an interesting question and could be addressed in schema or addressed in prose/text.

In any event, I do not want to lose your commentary when we get back to this issue.

FYI, I had been in favor of removing the built-in "dependency"; however Thomas points out this allows "simple" (optional) declaration of dependencies as template authors create node templates (which is very good) without needed to create (subclass a new type) which I am completely in support of.


was (Author: mrutkows):
Hi Luc,

In terms of the definition, it is correct using our existing semantics, as a requirement is fulfilled either by a Node Type (which has implicit capabilities) or a an explicit Capability which is included on a Node Type.   I believe the "gap" is that no where do we say (nor in schema can we prove) that a Node Type represents a a packaged set of Capabilities.  This is an interesting question and could be addressed in schema or addressed in prose/text.

In any event, I do not want to lose your commentary when we get back to this issue.

FYI, I have been in favor of removing the built-in "dependency"; however Thomas believes this allows "simple" (optional) declaration of dependencies as template authors create node templates (which is very good) without needed to create (subclass a new type) which I am completely in support of.

> WD02 - Need examples of using the built-in feature (Capability) and dependency (Requirement) of tosca.nodes.Root
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: TOSCA-161
>                 URL: https://issues.oasis-open.org/browse/TOSCA-161
>             Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
>          Issue Type: Improvement
>          Components: Profile-YAML
>    Affects Versions: CSD2
>            Reporter: Matthew Rutkowski 
>            Assignee: Thomas Spatzier 
>             Fix For: CSD2
>
>




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