Paul Lipton, VP Industry Standards, CA Technologies OASIS TOSCA Technical Committee Co-Chair
description
Transcript of Paul Lipton, VP Industry Standards, CA Technologies OASIS TOSCA Technical Committee Co-Chair
TOSCATopology and Orchestration Specification for Cloud Applications
International Cloud SymposiumOctober 10-12, 2012
Paul Lipton, VP Industry Standards, CA TechnologiesOASIS TOSCA Technical Committee [email protected]
Background
—TOSCA Technical Committee formed in December 2011 −Initial technical contribution:
•CA Technologies, CapGemini, Cisco, Citrix, EMC, IBM, NetApp, PwC, Red Hat, SAP, Software AG, Virtunomic, WSO2
—Grown to be one of the largest TCs (> 100 members)
Members (Also Many Observers)
Services Portability is Not Easy!
—Portability (install, operate, regulate, market/exchange) —Many challenges with real-world services
−Complex software and hardware infratructure• Complicated requirements, Sequence-of-operation,
relationships, groupings, capacity, dependency, configuration, and much, much more!
Approach 1: Moving virtual images? −Uncoordinated, unsynchronized snapshots of virtual components
• Operation at the component level only• No “understanding” of the overall service
Netw
ork
Services Portability is Not Easy!
—Portability (install, operate, regulate, market/exchange) —Many challenges with real-world services
−Complex software and hardware infratructure• Complicated requirements, Sequence-of-operation, relationships,
groupings, capacity, dependency, configuration, and much, much more!
Approach 2: “Bundle” the service components in a “package” for a service provider? Not adequate!
−Another provider might not have a clue how install, operate, regulate, manage the service • Detailed skills and information needed!
Netw
ork
TOSCA Addresses Service Portability
—TOSCA Use Cases Across Service Lifecycle −Deploy Cloud Services: Install, Remove, Configure,
Integrate−Operate Cloud Services: Start, Stop, Patch, Scale−Regulation of Cloud Services: Disaster Recovery,
Geo-Redundancy, Optimization (cost, volume, etc.), Verification
−Markets and Exchanges for Cloud Services
Introducing TOSCA
—Standardized description language−Structure and nature of an IT Service (its topology
model) −Behavior and “best practices” (plans such as build,
deploy, patch, shutdown, etc.)−Packaging format
—Simple declarative model that spans applications, virtual and physical infrastructure
Topology and Orchestration Specification for Cloud Applications
More Colorfully…
8
Topology Model Orchestrated Behaviours (Plans)
Relationship
Node
Operation Task
TOSCA Service Templates – a model based approach!
9
How 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 ...
Apache Webserver
…
Deploy Web Farm
… …
Script- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
…refers to…
…bound to…
10
Vision: A Complete TOSCA Eco-System
ServiceCatalog
1. Model Once
2. Publish
3. Browseand Select
4. Tools tooptimize, report, etc.
6. Use
Service Template
Service Template
Service Instance
5. Deploy anywhere
11
TOSCA Status
—Goal: submit v1 of the language for public review by the end of 2012 −Additional language definitions and refinements will
be standardized in late 2013, as the industry and use cases continue to mature
−Interoperability testing subcommittee started in September 2012
12
Summary
—Model-driven, portability across the service lifecycle −Examples: scale-in, scale-out, patch, multi-cloud, regulate, burst,
markets−Enabled by service-centric topology models acted upon by TOSCA
plans
—Can work with other standards, e.g., OVF, CIMI, OCCI, BPMN, etc. Working with TM Forum.
— Immense TOSCA eco-system potential −Multi-cloud services to meet requirements, restrictions, regulations −Automation with faster deploy, test, update, existing app migration,
etc.−Simulation (like debugging) of deployment and changes−Cloud service marketplaces
OASIS TOSCA Technical Committee:http://www.oasis-open.org/committees/tosca
TOSCA TC Charter:http://www.oasis-open.org/committees/tosca/charter.php
More on OASIS or Joining TOSCA Technical Committee:Carol GeyerSenior Director, [email protected]+1-941-284-0403
Learn More, Ask Your Vendors, Join!