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] Commented: (TOSCA-117) Use Case: Requirement and Capability Matching using Capability Properties (Travis, HP)


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

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

Hi Travis,  I discussed this today with Thomas.  

We think that this could be solved by adding Constraints to Requirements (and Capabilities), i.e. on Node Templates.  Furthermore, we would need to define a simple constraint language (under the TOSCA namespace) that allows comparisons on Properties.  Such constraints specified on Requirements (or Capabilities) will refer to Properties of Capabilities (or Requirements).  This will support your scenario. 

For the time being one could go ahead as defined above, i.e. by instrumenting the Requirement Types (and, thus, the using Node Types) accordingly.  Especially, this will be upward compatible with the new features in the spec. 

Alternatively, we could define a convention to (mis)use PropertyConstraints of a Requirement to refer to (i.e. constrain) Properties of a Capability for the sake of the interop scenarios. Note though, that the PropertyConstraints on Requirements or Capabilities in todays spec are actually meant to refer to the Properties of the Requirements or Capabilities themselves. They allow to express other kinds of constraints, e.g. expressing "read-only" etc.. 

Anyway, using one of those two approaches, we could implement this today and would have easy migration to a future spec enhancement.

> 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

        


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