[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=33837#action_33837 ] 

Travis Tripp commented on TOSCA-117:
------------------------------------

Frank, 

I have additional material I can talk to, but what about something like this.  If we had an Abstract Compute Type, and on that type we would dynamically associate the requirements / capabilities of it. So, then, my application template would only include the topology I choose to express.  For example, if I had SugarCRM, Apache, and PHP in the template, but then Apache was just associated directly with the Abstract Compute Type via a Hosted On relationship (the others could be as well if desired). That is where the template would stop.  A wrapping template or the engine itself could the substitute in a different topology to fulfill everything else that the abstract compute type expressed (OS, CPU, Memory, Storage).

In the below example, Abstract Compute Type would not define the requirements (which I think could be expressed as capabilities depending on your point of view), but they would only be on the node template.  In OpenStack terms, the ubuntu and ephemeral requirement would be fulfilled by the image, the cpu and memory by an actual flavor, and finally the persistent block storage by a storage volume.

<t:NodeTemplate name="Web Servers" id="WebServers0001" type="c:AbstractComputeType">
                <Requirements>
                    <Requirement id="WebServers0001_Ubuntu001" name="ubuntu" type="c:Ubuntu">
                        <Properties>
                            <version>11.04</version>
                            <architecture>amd64</architecture>
                        </Properties>
                        <PropertyConstraints>
                            <PropertyConstraint property="number" constraintType="greater_than_or_equal_to"/>
                            <PropertyConstraint property="architecture" constraintType="equal"/>
                        </PropertyConstraints>
                    </Requirement>
                    <Requirement id="WebServers0001_cpu001" name="Minimum CPU" type="c:cpu">
                        <Properties>
                            <number>1</number>
                        </Properties>
                        <PropertyConstraints>
                            <PropertyConstraint property="number" constraintType="greater_than_or_equal_to"/>
                        </PropertyConstraints>
                    </Requirement>
                    <Requirement id="WebServers0001_memory001" name="Minimum memory" type="c:memory">
                        <Properties>
                            <mb>512</mb>
                        </Properties>
                        <PropertyConstraints>
                            <PropertyConstraint property="mb" constraintType="greater_than_or_equal_to"/>
                        </PropertyConstraints>
                    </Requirement>
                    <Requirement id="WebServers0001_storage001" name="Minimum local storage" type="c:ephemeral volume">
                          <Properties>
                            <gb>5000</gb>
                        </Properties>
                        <PropertyConstraints>
                            <PropertyConstraint property="gb" constraintType="greater_than_or_equal_to"/>
                        </PropertyConstraints>
                    </Requirement>
			<Requirement id="DBServers0001_storage0002" name="Minimum persistent storage" type="c:persistent block storage">
				<Properties>
				    <gb>10000</gb>
				</Properties>
					<PropertyConstraints>
						<PropertyConstraint property="gb" constraintType="greater_than_or_equal_to"/>
					</PropertyConstraints>
			</Requirement>
                </Requirements>
            </t:NodeTemplate>

> 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