[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=33739#action_33739 ] 

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

I think I got your point, Travis :-)   No, you should not be forced to define a new Node Type "just because" you have a one-time resource requirement wrt to a Node Template you want to deploy. But that's the current state if I don't miss something...

Admittedly, Node Types are more stable as can be somehow derived from the TOSCA Primer. The Type Architect role defines that Node Types and the Application Architect role makes use of these types in defining his topology template. And in this picture, the application architect in fact has no chance to add a new requirement to a certain Node Template (i.e. his use of the formerly defined Node Type). I.e. currently the corresponding Node Type has to be modified to reflect the new requirement. 

> 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