View
214
Download
0
Category
Tags:
Preview:
Citation preview
www.oasis-open.org
TOSCA*& The Government Sector
Tobias Kunze, Red Hat
* Topology and Orchestration Specification for Cloud Applications
Motivation
Why Standards?
Government Needs
Standards Provide
Outsourcing ⇦ Defined Contracts
Agility ⇦ Speed through Reuse
Cost Savings ⇦ Insurance against Failure
Quality ⇦ State-of-the-Art Services
Vendor Neutrality ⇦ Vendor Neutrality
Interoperability ⇦ Interoperability
Use Cases
Use Cases Addressed
‣ Deploy: Dependency resolution, Install, Configuration, Orchestration
‣ Operate: Start, Stop, Patch, Scale
‣ Migrate: Disaster Recovery, Geo-Redundancy, Cost Optimization, Promotion
6
ServiceCatalog
1. Create
2. Publish
3. Browseand Select
4. Provision
5. Use
Service Template
Service Instance
Other Scenarios: Creating a Market For Cloud Applications
Other Scenarios: Creating a Market For Cloud Applications
How it Works
8
What Is “(Cloud) Service Template” All About?What Is “(Cloud) Service Template” All About?
A new language (“metamodel”) to specify the building blocks of your application the management functions these
building blocks offer to be managed
the relations between these building blocks
Collection of node types and relationship types(for reuse purposes)
the procedures to follow in order to manage your application as a whole
NodeTypes
Rel.shipTypes
Plans
Topology(Template)
(Clo
ud)
Serv
ice T
em
pla
te
GroupTemplate
9
Graphical RepresentationGraphical Representation
Prop
ertie
s Interfaces
NodeTemplate
Topology Template
type for
Node Type
Relationship Template
Service TemplateNode Types
Plans
type for
Prop
ertie
s
Relationship TypeRelationship Types
GroupTemplate
10
How Plans and Nodes Fit TogetherHow Plans and Nodes Fit Together
Task of a plan refers to interface of a topology node
Topology node specifies all interfaces offered to manage it Interface is bound to a concrete implementation
Implementation already available at providers side, or Implementation is copied from somewhere, or A standardized Cloud Interface (Iaas, PaaS, SaaS) is used,
or ...
WebSphere Cell …
Create Cluster
… …
Script- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
…refers to…
…bound to…
11
More Colorful…More Colorful…
Topology Orchestration (Plans)
12
Refined ViewRefined View
How ...
----
----
----
----
----
----
----
----
----
OVFOVFOVF
With ...
Scripts WorkflowsEAR (EJBs,…)BPEL
The images of the middleware (DB2, Websphere,…) required to run the application
The business logic of the application, e.g. EJBs, JSPs, JPEG,…
The business processes of the application (BPEL, BPMN, Human Tasks,…)
(Existing) scripts used by task of plans to manage the cloud application
(Existing) workflows used by subprocess-tasks of plans
13
BaselineBaseline
TOSCA is modular and composable
It does not reinvent the wheel, i.e. it uses existing standards wherever possible E.g. WSDL, BPMN, OVF,…
14
The Service TemplateThe Service Template
<ServiceTemplate …> <Extensions/>? <Import />*
<Types/>?
( <TopologyTemplate/>
| <TopologyTemplateReference/>)?
<NodeTypes/>?
<RelationshipTypes/>?
<Plans/>? </ServiceTemplate>
<ServiceTemplate …> <Extensions/>? <Import />*
<Types/>?
( <TopologyTemplate/>
| <TopologyTemplateReference/>)?
<NodeTypes/>?
<RelationshipTypes/>?
<Plans/>? </ServiceTemplate>
YAML as well
Effort
History
May 2011 Sep 2011 Oct 2011 Nov 2011 Dec 2011
Industry consortium formed (IBM, SAP, Red Hat, CA, Citrix, WSO2)
Renamed TOSCA
Addt’l members: Capgemini, Cisco, Citrix, EMC, NetApp, PwC, Software AG, Virtunomic
Charter submitted to OASIS
Call for Participation
First TC meeting
Members
Public Review
Future
Mar 2012 Jul 2012 Oct 2012 Nov 2012 Dec 2012
Initial Draft
Public Draft
Sep 2012Aug 2012
Candidate Standard
Draft 2 … Draft n
Public Review
Candidate Standard
Q&A
Appendix: Examples
21
Example: High Level ViewExample: High Level View
WebSphereCell
DB2 Server
WebSphereProcessServer
BPEL Files
EJBs
WSDL Files
uses
implementedby
deployedOn
requires
requires
deployedOn
deployedOn…and this is a
bit more clomplex…
Node TemplateNode Template
Relationship TemplateRelationship Template
22
Example: WebSphere Cell Refined
Example: WebSphere Cell Refined
WebSphere Cell
IHSNode
WAS NDDeployMgr
Node
WAS NDManaged Node
Application Server Instance
Cluster
DB2 Server
DB2 Database Instance
"cluster""database"
1..*
1..*exists
Properties, e.g.:ports, servername, weight
Properties, e.g.:WAS install location, Profile name, Node name
WebSphereCell
DB2 Server
23
Example: Overall Topology TemplateExample: Overall Topology Template
WebSphere Cell
IHSNode
WAS NDDeployMgr
Node
WAS NDManaged Node
Application Server Instance
Cluster
DB2 Server
DB2 Database Instance
1..*
1..*
WebSphereProcessServer
BPEL Files
EJBs
WSDL Files
24
Example: AmazonExample: Amazon
WebSphereCell
DB2 Server
WebSphereProcessServer
BPEL Files
EJBs
WSDL Files
uses
implementedby
deployedOn
requires
requires
deployedOn
deployedOn
AmazonAmazon
25
…Which is the “Interoperable Service Templates” Scenario (see later)
…Which is the “Interoperable Service Templates” Scenario (see later)
WebSphereCell
DB2 Server
WebSphereProcessServer
BPEL Files
EJBs
WSDL Files
AmazonAmazon
26
Example: Amazon – Refined ScenarioExample: Amazon – Refined Scenario
WebSphereCell
DB2 Server(WAS Data)
WebSphereProcessServer
BPEL Files
EJBs
WSDL Filesuses
Implemented by deployedOn
requires
requires
AmazonAmazon
DB2 Server(ApplicationDat
a)
requires
WebSphereCell
deployedOn
On PremiseOn Premise
27
Example: Amazon – Refined Scenario(Details)
Example: Amazon – Refined Scenario(Details)
WebSphereCell
DB2 Server(WAS Data)
WebSphereProcessServer
BPEL Files
EJBs
WSDL Filesuses
Implemented by deployedOn
requires
requires
AmazonAmazon
DB2 Server(ApplicationData)
requires
WebSphereCell
deployedOn
On PremiseOn Premise
The Web Services required by the BPEL processes are hosted on premise
The EJBs (e.g.) implementing the Web Services are deployed on WebSphere hosted on premise
The application data of the WS/EJBs are stored in DB2 on premise
This ensures compliance with data privacy/confidentiality rules
Process Server etc is installed and managed at Amazon’s EC2
The corresponding middleware is provided as AMIs
The process models are deployed on Process Server
Process Server maintains state data in DB2 also running in EC2
28
Example: Reusing Existing ServicesExample: Reusing Existing Services
Only the processes and required middleware is managed on a “known” cloud
The Web Services needed by the BPEL processes are reused “wherever” they are
The existing Web Services are bound to the BPEL process by the established mechanisms
Specifying binding details can be part of the build plan of the application’s Service Template (.ste)WebSphere
Cell
DB2 Server
WebSphereProcessServer
BPEL Files
WSDL Files
uses
deployedOn
requires
requires
deployedOn
WS1WS1
WS2WS2
WSnWSn
…
„somewhere1“„somewhere1“
„somewhere2“„somewhere2“
„somewheren“„somewheren“
boun
d to
boun
d to
29
Example: SAPExample: SAP
Netweaver
Oracle
SAP Workflow
BPEL Files
EJB
WSDL Files
uses
implementedby
deployedOn
requires
requires
deployedOn
deployedOn
SAPSAP
30
Example: MicrosoftExample: Microsoft
.Net
SQL Server
BizTalk
BPEL Files
.NetAssemblies
WSDL Files
uses
implementedby
deployedOn
requires
requires
deployedOn
deployedOn
AzureAzure
31
Example: Different Hosters of a Particular ApplicationExample: Different Hosters of a Particular Application
Netweaver
Oracle
SAP Workflow
BPEL Files
EJB
WSDL Files
uses
implementedby
deployedOn
requires
requires
deployedOn
deployedOn
IBMIBM
AT&TAT&T
T-SystemsT-Systems
......
Recommended