tosca requirements & capabilities
DESCRIPTION
TOSCA Requirements & Capabilities. Kevin Wilson & Travis Tripp Jun 12th, 2013. User Profiles. Developer / Arch of Software Company - PowerPoint PPT PresentationTRANSCRIPT
© Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
TOSCA Requirements & CapabilitiesKevin Wilson & Travis TrippJun 12th, 2013
© Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.2
User ProfilesDeveloper / 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.
© Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.3
User ProfilesIntegrator
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.
© Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.4 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.
© Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.5 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.
© Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.6 6
Capabilities & Requirements
Common TOSCA xsd/xml
Application
TOSCATopology
Application
TOSCATopology
Requirement
- Constraint
Capability-
Property
© Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.7 7
Capabilities & Requirements – Interface TOSCA-115
Common TOSCA xsd/xml
Application
TOSCATopology
Application
TOSCATopology
Requirement
- Constraint
Capability-
PropertyContract
© Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.8 8Oracle ( Java ) JBoss
Capabilities & Requirements – Interface Parameters
Common TOSCA xsd/xml
Application
TOSCATopology
Application
TOSCATopology
Requirement
- Constraint
Capability-
PropertyJAVAHOME
© Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.9 9Oracle ( Java ) JBoss
Capabilities & Requirements – Interface Methods
Common TOSCA xsd/xml
Application
TOSCATopology
Application
TOSCATopology
Requirement
- Constraint
Capability-
Property AddCertRemoveCer
t
© Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.10
Capabilities & Requirements – Interface Methods
Common TOSCA xsd/xml
Application
TOSCATopology
Capability-
PropertyContract
© Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.11
Capabilities & Requirements – Interface Methods
11
Common TOSCA xsd/xml
Application
TOSCATopology
Requirement
- ConstraintAddCert
RemoveCert
© Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.12 12
Binding Choices
Vendor AVersions
Application
Model
Vendor B Versions +
© Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.13 13
Runtime
Engine
Operational UI
Inspect Runtime ParameterValues
Invoke Methods at Runtime
RunningSoftwar
e Instanc
e
TOSCADocs
© Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.14 HP Confidential
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.
14
© Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.15 15
Capabilities & Requirements – Composite Requirements
Common TOSCA xsd/xml
Application
TOSCATopology
Application
TOSCATopology
CompositeRequiremen
tCompositeCapability
© Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.16 16
Capabilities & Requirements – Composite Requirements
Common TOSCA xsd/xml
Application
TOSCATopology
Application
TOSCATopology
LAMPRequiremen
tLAMP
Capability
© Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.17 HP Confidential
By Placing a requirement on a composite. All sub requirements must be met.
17
Linux
Apache
MySQL
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.
© Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.18 18 Lamp Stack
Capabilities & Requirements – Composite Requirements
Common TOSCA xsd/xml
Application
TOSCATopology
Application
TOSCATopology
LinuxApachePHP
LinuxApachePHP