1 / 13

Paul Lipton, VP Industry Standards, CA Technologies OASIS TOSCA Technical Committee Co-Chair

TOSCA T opology and O rchestration S pecification for C loud A pplications International Cloud Symposium October 10-12, 2012. Paul Lipton, VP Industry Standards, CA Technologies OASIS TOSCA Technical Committee Co-Chair paul.lipton@ca.com. Background.

eden
Download Presentation

Paul Lipton, VP Industry Standards, CA Technologies OASIS TOSCA Technical Committee Co-Chair

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. TOSCATopology and Orchestration Specification for Cloud ApplicationsInternational Cloud SymposiumOctober 10-12, 2012 Paul Lipton, VP Industry Standards, CA Technologies OASIS TOSCA Technical Committee Co-Chair paul.lipton@ca.com

  2. 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)

  3. Members (Also Many Observers)

  4. Services Portability is Not Easy! Network • 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

  5. Services Portability is Not Easy! Network • 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!

  6. 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

  7. Introducing TOSCA Topology and Orchestration Specification for Cloud Applications • 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

  8. More Colorfully… Topology Model Orchestrated Behaviours (Plans) Node Operation Relationship Task TOSCA Service Templates – a model based approach!

  9. Script - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Deploy Web Farm Apache Webserver 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 ... … … …refers to… … …bound to…

  10. ServiceCatalog Vision: A Complete TOSCA Eco-System Service Instance 6. Use 3. Browseand Select 5. Deploy anywhere 4. Tools tooptimize, report, etc. Service Template 2. Publish 1. Model Once Service Template

  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

  13. Learn More, Ask Your Vendors, Join! 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 Geyer Senior Director, OASIS carol.geyer@oasis-open.org +1-941-284-0403

More Related