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=33827#action_33827 ] 

Travis Tripp commented on TOSCA-117:

Hi Frank,

If we couple your first paragraph with the notion that I can add new requirements / capabilities directly on a NodeTemplate, then I think this addresses a lot of my questions.  I had essentially put what you proposed in the example xml I included. I think it works, but is somewhat clumsy. Copied with slight modification at end of this message.

I would propose the following constraints:


<NodeTemplate id="Tomcat" name="Tomcat" type="ApacheTomcatType">
					<Requirement id="TomcatDeployment_minimunHostServerRequirements" name="minimunHostServerRequirements" type="SoftwareHostRequirement">
						<!-- User properties to specify mapping or use constraints?-->


							<!-- How does xpath work in the property? Capability may not be defined here and the properties are defined external to the capability-->
                                                        <!-- Can we limit to flat properties only - no structured or nested property structures? -->
							<PropertyConstraint property="/NumCpus" constraintType="greater_than_or_equal_to"/>
							<PropertyConstraint property="/MemoryInMB" constraintType="greater_than_or_equal_to"/>
							<PropertyConstraint property="/DiskInGB" constraintType="greater_than_or_equal_to"/>

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