+ All Categories
Home > Documents > Paul Lipton, VP Industry Standards, CA Technologies OASIS TOSCA Technical Committee Co-Chair

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

Date post: 22-Feb-2016
Category:
Upload: eden
View: 53 times
Download: 0 times
Share this document with a friend
Description:
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 [email protected]. Background. - PowerPoint PPT Presentation
Popular Tags:
13
TOSCA Topology and Orchestration Specification for Cloud Applications International Cloud Symposium October 10-12, 2012 Lipton, VP Industry Standards, CA Technologies S TOSCA Technical Committee Co-Chair [email protected]
Transcript
Page 1: 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]

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

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)

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

Members (Also Many Observers)

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

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

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

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

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

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

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

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

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

More Colorfully…

8

Topology Model Orchestrated Behaviours (Plans)

Relationship

Node

Operation Task

TOSCA Service Templates – a model based approach!

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

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…

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

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

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

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

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

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

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

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!


Recommended