TOSCA Value for CxOs

1. TOSCA Value for CxOs Draft outline for feedback by TOSCA TC members Editors: Karsten Beins (Fujitsu), Peter Gibbels (HP), Paul Lipton (CA Technologies), Derek Palma (Vnomic), Matt Rutkowski (IBM) Date: 2014-03-18

2. TOSCA Introduction (to CIOs) • TOSCA is an important new open cloud technology, supported by a large and growing number of international industry leaders • It addresses critical cloud application challenges: • Speed and accuracy moving apps to Cloud • TOSCA captures knowledge to automate rapid implementation and deployment • TOSCA spans the entire technology stack and multiple Clouds • Agility adapting to change (Business and IT) • TOSCA enables holistic lifecycle automation ensuring Integrity, Security and Compliance • TOSCA reduces complexity by expressing application requirements independently from infrastructure capabilities • Choice of Cloud vendor and technology • TOSCA enables flexible deployment and migration on different Clouds while maintaining needed functionality, quality and manageability • TOSCA is a recognized OASIS industry standard, aligned with key open source projects (e.g., OpenStack, Cloudify, Eclipse) • Members: ASG Software, Axway, CA Technologies, China Internet Network Information Center, Cisco, Citrix, CloudSoft, EMC, FastConnect SAS, Fujitsu, GigaSpaces, Google, HP, Huawei, IBM, NetApp, Nokia, Primeton, Red Hat, SAP, Software AG, VCE, Vnomic , WSO2, Yaana, Zenoss

3. Call to action for the CIO • Business demands greater speed and agility while application complexity increases • If you intend to use the Cloud to address these challenges then TOSCA impacts your Technology Strategy! • Determine how leveraging TOSCA can benefit YOU • Talk to your vendors and platform providers • Charter your CTO office to investigate – we can deliver deep dive material

4. Topics for the office of the CTO and Enterprise Architects org

5. Potential TOSCA Storyline Context: enterprise IT struggles with many aspects when using cloud to host applications, e.g. assure time-to-value and agility, managing complexity, choosing technology / vendor (lock-in), speeding innovation, etc. (tell the story with “app” as main character) TOSCA always considers the application’s needs • Breadth of TOSCA: (“apps” view of TOSCA just from the app-layer perspective) • Application-centric: application-centric modeling (why is app abstraction important?) (app requirements are always projected on infrastructures, existing methods bind the app to an provider or platform, without knowing it… downside… TOSCA does not). • Initial AND post-deployment: holistic lifecycle / operational management automation for agile adaption to change without jeopardizing Integrity, Security and Compliance (operations are abstracted) (application operations are abstracted, benefit? More than deployment). • Composable / “snap-able” models and automation (dynamically add, remove, replace application services or dependencies) • Quickly and efficiently adapt application to address compliance, monitoring, backup, scaling, etc. • Depth of TOSCA (“apps” sees the “vertical view” with a rich infra. below it to utilize, TOSCA provides a better way) • Hybrid cloud enabling: simplifying integration with multiple Cloud (provider) infrastructures, platforms and external / hybrid services. (allowing granular outsourcing) (applications need to work with other apps and services, these dynamically change over its lifecycle to address scale/growth, cost, failover). • Entire topology covered (when the app needs to interact “deeply” with infrastructure services TOSCA provides a better way. Without coupling) • Independent modeling and automated orchestration for Infrastructure and application (app and Infra. Lifecycle can be managed independently… change management, provider upgrades) • As an open standard TOSCA reduces complexity • Cloud portability and interoperability of complex applications • Automatic & flexible (adaptive?) matchinginfrastructure capabilities with application requirements • not simply restricting to the least common denominator (like many other standards) • Capturing advanced expert knowledge to automate application deployment & management of complex applications independent of particular platforms/infrastructures

6. TOSCA Storyline (as a theatre play) • Prelude: application centricity as main role in TOSCA • Act I: from the application perspective • Act II: view to the underlying infrastructure • Act III: Open standard • Finale:

7. Prelude – Application Centricity • The TOSCA standard is application-centric because in IT, applications are the key to support business processes • For compelling benefits applications are moved to Cloud • Automation of key operations needed by Apps to deliver expected services • Operations including deployment, update, transformation, migration • With agility, accuracy and control • Without jeopardizing integrity, security and compliance • Abstractions are needed for these operations to • Decouple applications from specific infrastructures details • Articulate application requirements in a platform neutral way • Enable infrastructure environments to understand such application requirements and offer their best matching capabilities

8. Act I: TOSCA enables one-click deployment of complex applications anywhere in the Cloud • Scene 1: TOSCA’s abstract operations allow deployment, update, etc. to different clouds • How: complete expression of applicationrequirements. TOSCA is the first standardized approach • Scene 2: Snap-able, re-usable, composablecomponents, … (like DBs, monitoring services) • How: application component requirements and inter-dependencies, component-level abstractions • Scene 3: Hybrid cloud (extending cross-cloud) • How: deploy application components into different infrastructures, resolving their requirements to actual available infrastructure capabilities in a way that required functionality, quality-of-service and manageability are guaranteed no matter where <Still to be inserted – where? In act I or II?> • InitialAND post-deployment: holistic lifecycle / operational management automation for agile adaption to change without jeopardizing Integrity, Security and Compliance

9. Act II: view to the underlying infrastructure • Scene 1: … • Scene 2: … • Scene 3: …

10. Act III: Open standard • Scene 1: … • Scene 2: … • Scene 3: …

11. Finale - TOSCA • Vision: describe all of IT declaratively • In a single document • All aspects visible • Completely under your control

12. Overview of Challenges (to CTOs) • How do I optimize time-to-value for moving apps to Cloud? • How do I leverage domain expert knowledge and best practices as cloud applications become more complex? • How can I support business dynamics and IT change agility while keeping IT costs balanced? • How do I scale to support growing business? • How do I keep Development & Operations aligned while optimizing time-to-value and continuous delivery of cloud applications? • How do I preserve choice of Cloud vendor, platform and technology?

13. <meta slide: template for following “challenge” slides>“Challenge xyz” • Very concrete problem statement • How does TOSCA solve xyz? • Why is TOSCA unique?

14. How do I optimize time-to-value for creating and moving apps to Cloud? • Accelerate IT learning curve while migrating existing enterprise applications to the Cloud • Leverage best internal & external expertise to prevent costly trial and error • Rapidly unleash the business benefit potential of Cloud • Use of existing TOSCA models • Bundling of application products with TOSCA model ready-to-use • Best practices composed by communities, consultants, cloud service providersleveraging application lifecycle management expertise of recognized industry experts • OASIS TOSCA guidelines standardize a high quality • Allows rapid deployment of applications

15. How do I leverage domain expert knowledge and best practices as cloud apps become more complex? • Powerful new mechanism to capture and leverage expert knowledge • ISV, System Integrators, infrastructure vendors, universities, open contributors (e.g. OpenStack, Eclipse, Dev communities) • Marketplaces / libraries for cloud application models structured as TOSCA content • Preserve and leverage existing investments in scripts, workflows, etc. • TOSCA enforces reusability by a structured development and delivery approach • Start today to leverage TOSCA principles and methodologies in your enterprise architect community

16. How can I support business dynamics and IT change agility while keeping IT costs balanced? • TOSCA contributes to reduced IT costs by supporting transformation to the Cloud • Dynamically adapt to changing business conditions TOSCA enables choice of cloud service providers incl. private/managed/public clouds • TOSCA supports necessary governance of IT supply chain while providing needed IT agility to Lines-of-Business

17. How do I scale to support growing business? • Agile business needs to adapt to changing conditions rapidly • Seasonal changes • Special / unforeseeable events • Business growth / shrink • Merger & Acquisition, divestiture • TOSCA is revolutionizing change management • Enable & support full automation of planned & unplanned changes • Adopt, harmonize and modernize the common IT standards, governance, compliance regulations after M&A • Automate the b2b integrationfor new business partner onboarding • Accelerate agile lifecycle iterations along the Dev-Test-QA-Production chain • Leverage other experts’ documentation, automated solutions and tools for modeling & orchestration • Decoupling application requirements from infrastructure capabilities

18. How do I keep Development & Operations aligned while optimizing time-to-value and continuous delivery of cloud applications? • OASIS TOSCA is the most comprehensive cloud application-centric open standard • TOSCA model unified view minimizes the impact of change and maximizes productivity while simplifying DevOps across all environments • TOSCA enables transparency and understanding of applications and their dependencies across multiple clouds and throughout their lifecycle • TOSCA-based comparison and automation of actual/target configurations supports governance, risk and compliance management

19. How do I preserve choice of Cloud vendor, platform and technology? TOSCA as an Open Standard offers • Portable service description • Encapsulation of best practices in a provider neutral fashion • Modular and composable approach Benefits • Choices of cloud service providers • Flexibility to change cloud service providers over time • Interoperability across multiple cloud service providers • High quality of service through re-use and adaptability • Choice of service quality and price

20. TOSCA Conceptual Open Ecosystem Enabling choice for cloud customers … aligning with all involved roles / processes Cloud Customers Cloud Providers aspart of IT Supply Chain Architects and Developers Design Deploy TOSCA Marketplaces / Libraries Reuse Manage Develop Application Modeling & Testing Tools Publish CloudOrchestrators Cloud A Cloud B Cloud C ISV, System Integrators, Infrastructure Vendors, Enterprises, Universities, Open Contributors

21. Backup

22. Placeholder slide for examples • Needed to back up our statements • Example slides still TBD

23. Act I: TOSCA enables one-click deployment of complex applications anywhere in the Cloud • Scene 1: TOSCA’s abstract operations allow deployment, update, etc. to different clouds • How: complete expression of application requirements. TOSCA is the first standardized approach • Scene 2: Snap-able, re-usable, composablecomponents, … (DBs, monitoring svcs) (within one cloud) • How: application component requirements and inter-dependencies, component-level abstractions • Scene 3: Hybrid cloud (extending cross-cloud) • How: deploy such components into different infrastructures, resolving requirements to infrastructure capabilities still maintaining the reuiredfunc, qos and manageability, functionality is guaranteed no matter where it’s put • Breadth of TOSCA: (“apps” view of TOSCA just from the app-layer perspective) • InitialAND post-deployment: holistic lifecycle / operational management automation for agile adaption to change without jeopardizing Integrity, Security and Compliance (operations are abstracted) (application operations are abstracted, benefit? More than deployment).

24. Act I: TOSCA enables one-click deployment of complex applications anywhere in the Cloud • Scene 1: TOSCA’s abstract operations allow deployment, update, etc. to different clouds • How: complete expression of application requirements. TOSCA is the first standardized approach • Scene 2: Snap-able, re-usable, composable components, … (DBs, monitoring svcs) (within one cloud) • How: application component requirements and inter-dependencies, component-level abstractions • Scene 3: Hybrid cloud (extending cross-cloud) • How: deploy such components into different infrastructures, resolving requirements to infrastructure capabilities still maintaining the reuiredfunc, qos and manageability, functionality is guaranteed no matter where it’s put • Generality of operation • Breadth of TOSCA: (“apps” view of TOSCA just from the app-layer perspective) • Application-centric: application-centric modeling (why is app abstraction important?) (app requirements are always projected on infrastructures, existing methods bind the app to an provider or platform, without knowing it… downside… TOSCA does not). • Initial AND post-deployment: holistic lifecycle / operational management automation for agile adaption to change without jeopardizing Integrity, Security and Compliance (operations are abstracted) (application operations are abstracted, benefit? More than deployment). • Composable / “snap-able” models and automation (dynamically add, remove, replace application services or dependencies)