[OASIS Issue Tracker] Commented: (TOSCA-117) Use Case: Requirement and Capability Matching using Capability Properties (Travis, HP)

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

    [ http://tools.oasis-open.org/issues/browse/TOSCA-117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=33707#action_33707 ] 

Frank Leymann  commented on TOSCA-117:
--------------------------------------

A Node Type declares the Capability Types it provides by referring to them in the list of Capability Definitions.  The reason why the spec does not support values for properties in a Capability Definition is because we are still at the type level: when using the Node Type in a Node Template the spec allows to provide actual values for the properties of a Capability.

The purpose of the Constraint in a Capability Definition of a Node Type is to allow further restrictions of an offered Capability Type.  For example, if the MyRDBMS Node Type supports the SQL Capability Type by declaring it as one of its Capability Definitions, a nested Constraint my specify that nested queries are not supported (please forgive the ad hocness of this example...). 

> Use Case: Requirement and Capability Matching using Capability Properties (Travis, HP)
> --------------------------------------------------------------------------------------
>
>                 Key: TOSCA-117
>                 URL: http://tools.oasis-open.org/issues/browse/TOSCA-117
>             Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
>          Issue Type: Improvement
>          Components: Interop
>            Reporter: Matthew Rutkowski 
>            Assignee: Travis Tripp
>            Priority: Critical
>
> Use case described in this SC email:
> https://www.oasis-open.org/apps/org/workgroup/tosca-interop/email/archives/201306/msg00008.html
> ---- copied here below ----
> I have attached a use case document on the topic of "Requirement and Capability Matching using Capability Properties".
> A few months ago, I spent some time trying to figure out how to do part of the use case in TOSCA using the current spec and didn't feel that it was addressed properly in the spec for me to feel confident in how to accomplish it.  I've attached that attempt in the xml (Tomcat-TOSCA-Declare-Resource-Requirements.xml), but please be aware that it was just some playing around that I did.
>  
> I'm more than happy to talk through this document at the next interop meeting that I can attend.  As of now, I should be able to attend the next meeting.
> Thanks, Travis

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira