[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=36780#action_36780 ]
Travis Tripp commented on TOSCA-117:
------------------------------------
The operator keynames as described in the TOSCA Simple Profile YAML have captured these concepts:
The following is the list of recognized operators (keynames) when defining constraint clauses:
Operator Type Value Type Description
equal scalar any Constrains a property or parameter to a value equal to ('=') the value declared.
greater_than scalar comparable Constrains a property or parameter to a value greater than ('>') the value declared.
greater_or_equal scalar comparable Constrains a property or parameter to a value greater than or equal to ('>=') the value declared.
less_than scalar comparable Constrains a property or parameter to a value less than ('<') the value declared.
less_or_equal scalar comparable Constrains a property or parameter to a value less than or equal to ('<=') the value declared.
in_range dual scalar comparable Constrains a property or parameter to a value in range of (inclusive) the two values declared.
valid_values list any Constrains a property or parameter to a value that is in the list of declared values.
length scalar string
Constrains the property or parameter to a value of a given length.
min_length scalar string
Constrains the property or parameter to a value to a minimum length.
max_length scalar string
Constrains the property or parameter to a value to a maximum length.
pattern regex string
Constrains the property or parameter to a value that is allowed by the provided regular expression.
Note: Future drafts of this specification will detail the use of regular expressions and reference an appropriate standardized grammar.
> 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: Spec
> Affects Versions: V1.1_CSD01
> Reporter: Matthew Rutkowski
> Assignee: Travis Tripp
> Priority: Critical
> Fix For: V1.1_CSD01
>
>
> 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]