1 / 18

TOSCA Requirements & Capabilities

TOSCA Requirements & Capabilities. Kevin Wilson & Travis Tripp Jun 12th, 2013. User Profiles. Developer / Arch of Software Company

peony
Download Presentation

TOSCA Requirements & Capabilities

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. TOSCA Requirements & Capabilities Kevin Wilson & Travis Tripp Jun 12th, 2013

  2. User Profiles Developer / Arch of Software Company As a developer / Architect of a software company, I want to be able to expose Tosca documents that show how my software is intended to be deployed (Supported Topologies). And support the ease of integration of my software into a consumers environment.

  3. User Profiles Integrator As a Integrator of a software company, I want to be able to consume a application(s) via its supported topologies and create a integrated composite topology representing the deployment choices that I need to make to successfully integrate the product into the existing environment.

  4. Developer/Architect – Use Cases As a Developer/Architect I want to produce a tosca model that shows how may application may be deployed independent of the underlying infrastructure. As a Developer/Architect, I want to provide tools and integration that helps my product be easily consumed. As a Developer/Architect, I want to leverage other existing software in my topologies. As a Developer/Architect, I need to communicate the support matrix of my application to the consumers.

  5. Integrator – Use Cases As a integrator I want to be able to consume a TOSCA document and make calls to the value added function of a software component. As a integrator I want to be able to consume a TOSCA document and leverage common interfaces for the application during my deployment. As a integrator I want to be able to choose a tool for the right scale based on the lifecycle of my deployment environment. As a integrator I want to leverage several different pieces of software in my environment.

  6. Capabilities & Requirements Common TOSCA xsd/xml Requirement - Constraint Capability - Property Application TOSCA Topology Application TOSCA Topology

  7. Capabilities & Requirements – Interface TOSCA-115 Common TOSCA xsd/xml Requirement - Constraint Capability - Property Application TOSCA Topology Application TOSCA Topology Contract

  8. Capabilities & Requirements – Interface Parameters Oracle ( Java ) JBoss Common TOSCA xsd/xml Requirement - Constraint Capability - Property Application TOSCA Topology Application TOSCA Topology JAVAHOME

  9. Capabilities & Requirements – Interface Methods Oracle ( Java ) JBoss Common TOSCA xsd/xml Requirement - Constraint Capability - Property Application TOSCA Topology Application TOSCA Topology AddCert RemoveCert

  10. Capabilities & Requirements – Interface Methods Common TOSCA xsd/xml Capability - Property Application TOSCA Topology Contract

  11. Capabilities & Requirements – Interface Methods Common TOSCA xsd/xml Requirement - Constraint Application TOSCA Topology AddCert RemoveCert

  12. Binding Choices Application Model Vendor A Versions Vendor B Versions +

  13. TOSCA Docs Runtime Inspect Runtime Parameter Values Engine Operational UI Running Software Instance Invoke Methods at Runtime

  14. Composite Requirements/Capability • Often times applications are managed in groups. • Sometimes because mergers and acquisitions have allowed a company to produce a composite application. • Sometimes industry demand causes the merging of two similar product streams. • To support the above we need to be able to manage and collect requirements and capabilities into groups.

  15. Capabilities & Requirements – Composite Requirements Common TOSCA xsd/xml Composite Capability Composite Requirement Application TOSCA Topology Application TOSCA Topology

  16. Capabilities & Requirements – Composite Requirements Common TOSCA xsd/xml LAMP Capability LAMP Requirement Application TOSCA Topology Application TOSCA Topology

  17. By Placing a requirement on a composite. All sub requirements must be met. PHP LAMP By Placing a requirement on a composite. All sub requirements must be met. By providing a capability all capabilities are either provided or required by a sub layer. MySQL Apache Linux

  18. Capabilities & Requirements – Composite Requirements Lamp Stack Common TOSCA xsd/xml Linux Linux Application TOSCA Topology Application TOSCA Topology Apache Apache PHP PHP

More Related