1. © Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. TOSCA 115 Capability Interfaces Kevin Wilson, Travis Tripp, Kishore Jagannath Nov4, 2013

2. © Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. 2 TOSCA 115 – Issue Description Requirements and capabilities should provide specific interface definitions. So that the designer of a app can depend on a contract set of public properties that are to be provided and a contracted set method/interfaces that are provided by the requirement. For example: If I have a dependency on a DB Server, and need to run SQL on that server, at design time, I would like to know the methods supported by the DBServer requirement so that I can leverage that in my component scripting. On the implementation side providing the component, the script/method to execute the script may be different for each DBServer type. IE commands to run SQL on MySQL are not the same commands that would be used for Oracle. However, the SQL may the same in some cases. Similar methods/use cases exist for J2EE server deploy methods etc. By providing a interface on the Requirement/Capability we can leverage the workflows specific to the capability in a generic way. And the designer would be able to identify the contracted calls that are made available.

3. © Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. 3 Highlights of Proposal Capability Types should have the ability to expose interfaces with one to many operations in addition to property definition. Node Type possessing the capability will now inherit the interface operations defined in the capability. Node Type having multiple capabilities will now inherit the interface operations declared in each of the capability NodeTypeImplementation will provide implementation for all the interface operations that the Node Type inherits from the capabilities + any interface operations that are define within Node Type. TBD- Do we still need to have interface operations within Node Types. 3

4. © Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. 4 User Profiles Node Type Capability Type properties interfaces Node Type Implementation Implementation artifacts Deployment artifacts

5. © Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. 5 Reusable Interface Methods Node Type Capability Type properties interfaces Node Type

6. © Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. 6 Design Experience Node Type Capability Type properties interfaces Node Type Requirement Type properties interfaces Relationship Type

7. © Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. 7 Reuse via Composition Software > ApacheWebServer > properties operations MySql Database > properties operations ApacheWebServer > properties operations MySql Database > properties operations ApacheWebServer > MySql DB >

8. © Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. 8 Behavioral Reusability 8 Node Type1 Capabilities Snapshotcapability Snapshot Capability Properties Operations takesnapshot revertSnapshot Clone Capability Properties Operations createClone Node Type2 Capabilities Snapshotcapability clonecapability Normative Capability Types

9. © Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. 9 Tosca Schema <xs:element name="Interface" type="tInterface" maxOccurs="unbounded"/> 9

10. © Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. 10 <CapabilityType name="xs:NCName" targetNamespace="xs:anyURI"? abstract="yes|no"? final="yes|no"?> ? ? <InputParameter name="xs:string" type="xs:string" required="yes|no"?/> + ? <OutputParameter name="xs:string" type="xs:string" required="yes|no"?/> + ? + ? 10