Topology and Orchestration Specification for Cloud Applications (TOSCA) Standard

1. Topology and Orchestration Specification for Cloud Applications (TOSCA) Standard TOSCA Interoperability Demonstration Participating Companies: Join the TOSCA Technical Committee www.oasis-open.org, join@oasis-open.org

2. Complete cloud application modeling and orchestration TOSCA Enable portabilityand semi-automatic management of cloud applications across clouds regardless of provider platform or infrastructure thus expanding customer choice, improving reliability, and reducing cost and time-to-value. The TOSCA standard… Contributing Members • provides the Interoperable Description of: • Applications, their component Services and Artifacts • Platform and Infrastructure services, • Relationships between these services, and the • Management and Operational behavior of these services • facilitates higher levels of Solution Portability: • Portable deployment to any cloud that can orchestrate TOSCA service templates • Simplify Migration of existing customer apps. to cloud • Dynamic, Flexible Scaling and bursting of multi-cloud applications • Enables Software Defined Environments (SDEs) • Template contents provide the means to optimizethe underlying cloud infrastructure

3. Business Value TOSCA Open Ecosystem for Cloud Services • Vendor-independent definitions of complex Cloud services provide new marketing channel for solutions in the Cloud • Decoupling of Cloud infrastructure and Cloud content helps focus on key aspects: Cloud Provider or Cloud Service Provider • Ability to deploy services in any standards-compliant environment avoids vendor lock-in and eases migration • Interoperability and Composition • Goes beyond VMs in describing the cloud application‘s components and their dependencies • Composition of services defined independently by their domain experts into a higher-value service • Key enabler for open hybrid Clouds • Easy Adoption of new Cloud Services • Model-driven creation of Cloud Services • Standardized deployment into various kinds of environments • from test to production, from cloud A to cloud B • Process-driven Cloud Service Lifecycle Management Cloud A Cloud B Cloud C

4. TOSCA Conceptual Open Ecosystem Enabling choice for cloud customers… Orchestration ofTOSCA Apps in any TOSCA enabled cloud Wide Range of Open Source & Commercial Tooling • Customers can seamless deploy, run and manage any TOSCA applications in any TOSCA enabled cloud. • Architects and Developers can choose from many open source and commercial tools to create, compose, update and manage TOSCA Cloud Applications. Cloud Customers Design Deploy Service Template Marketplaces Reuse Manage Develop Application Modeling & Management Tools Publish Reusable, Composable TOSCA Service Templates Cloud Providers • Companies & Software Providerscan share TOSCA service templates which have encapsulated theirexpert knowledgeusing “marketplaces” for others to reuse and extend. Cloud A Cloud B Cloud C

5. Interoperability Demonstration Overview Demonstrating: different cloud orchestration tools from different vendors all interpreting and seamlessly running the same TOSCA service templates in the same way. Manage TOSCA Cloud Application Marketplaces Customize Orchestrate Cloud Management and Automation Design Benefits: Using TOSCA service templates, enterprise customers can easily move their applications from one cloud to another and orchestrate them using the expert knowledge the application developers have built into them. Telco Cloud Solution Suite Publish SmartCloud and Workload Deployer FlexFrame Orchestrator Cloud Monitoring

6. Specific Demonstration Elements Cloud Customers Service Template Marketplaces Application Modeling & Management Tools Cloud Management and Automation Suite Cloud Providers Telco Cloud Solution SmartCloud And Workload Deployer FlexFrame Orchestrator Cloud Monitoring

7. Composing a TOSCA Service Template for a “SugarCRM” Application using Vnomic’s Service Designer, www.vnomic.com • The SugarCRM application include 2 “Tiers”: • Web Application Tier (Linux, Apache, PHP, SugarCRM) • Database Tier (Linux, MySQL)

8. The Cloud Application is made “Portable” and packagedusing TOSCA’s Cloud Service Archive (CSAR) format which encapsulates the Application Architect’s “Expert Knowledge” for this demo, we choose to publish the “SugarCRM” Cloud Application to IBM’s Integrated Service Mgmt. (ISM) Cloud Marketplace

9. Showing “SugarCRM” as a newly published service by Vnomic into IBM’s “Cloud Marketplace” TOSCA service templates could be published and shared on both public and private marketplaces Demonstrating the vision of an “Open Ecosystem” of cloud services based upon TOSCA standardized service templates

10. The “SugarCRM” Application’s Topology Template Viewed in IWD Web Server Tier (left), Database Tier (right) … developers can choose to edit the components’ properties or simply use the defaults settings packaged in the CSAR file prior to deployment

11. The “SugarCRM” TOSCA Application is Fully Deployed and Running using IBM SmartCloud Foundation Services … we can see that both the Web Server and Database Tiers are running and assigned Public IP Addresses

12. Demo: deployment of SugarCRM to a private cloud based on a TOSCA Service Template Show a FUJITSU prototype of a TOSCA-compliant orchestrator that automatically: • interprets a TOSCA Service Template for SugarCRM applications, • orchestrates the environment for a SugarCRM application instance and • deploys it into a private Cloud using FUJITSU FlexFrame Orchestrator “The Fujitsu FlexFrame Orchestrator provides a comprehensive cloud framework to orchestrate and manage key applications like ERP, CRM and BI. By adopting TOSCA in FlexFrame Orchestrator we can now achieve cross-cloud interoperability and portability up to the application level. This is a great opportunity for Fujitsu to meet the customer challenge of using and combining cloud services from different clouds of different vendors.” Jens-Peter Seick, SVP Product Development, Fujitsu Technology Solutions

13. Login to “SugarCRM” application running on an IBM Cloud Demonstrating Seamless TOSCA “Run-time” Portability … using the IP Address allocated by IBM’s Cloud for the Apache Web Server which was part of the Web Server Tier of the TOSCA “SugarCRM” application

14. TOSCA Resources - Learn More & Participate! • TOSCA Technical Committee – Public Website • https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=tosca • TOSCA Specification, Version 1.0, Committee Spec. 01, March 18, 2013 • http://docs.oasis-open.org/tosca/TOSCA/v1.0/cs01/TOSCA-v1.0-cs01.pdf • TOSCA Primer, Version 1.0 , Committee Note Draft 01, 31 January 31, 2013 • http://docs.oasis-open.org/tosca/tosca-primer/v1.0/cnd01/tosca-primer-v1.0-cnd01.pdf • TOSCA Implementer's Recommendations for Interoperable TOSCA Implementations, Version 1.0, Working Draft 01, Revision 5, May 20, 2013 • http://www.oasis-open.org/committees/download.php/49245/tosca-implement-v1.0-wd01-rev05.docx • TOSCA Interop. Demo, SugarCRM Scenario Sample CSAR, August, 2013 • https://www.oasis-open.org/committees/download.php/50158/SugarCRM-Interop-20130803.zip

15. More on TOSCA Modeling…

16. Modeling Topologies with TOSCA Service Topologies are described using the TOSCA “Meta-model”: • Relationships • Represent the logical Relationshipsbetween nodes • e.g. “hostedOn”, “connectsTo”, etc. • Describes the validSourceandTargetnodes they are designed to couple • e.g. source “web application” node is designed to “connectTo” a target “database” node • Have their own Properties and Constraints • Nodes • Represent Componentsof an application or service and their Properties. Example nodes include: • Infrastructure: Compute, Network, Storage, etc. • Platform: OS, VM, DB, Web Server, etc. • Granular: functional Libraries, Modules, etc. • Include Operationswhich are the management functions for the node • e.g. deploy(), start(), stop(), connect(), etc. • Export their dependencies on other nodes • as Requirementand Capabilities • Service Templates • Groupthe nodes and relationships that make up a service’s topology • Allowing modeling of sub-topologies • Service Templates “look like nodes”enabling: • Composition of applications from one or more service templates • Substitution of abstract Node types with available service templates of the same type • Artifacts • Describe Installablesand Executablesrequired to instantiate and manage a service. Currently, they include: • Implementation Artifacts: • Executables or Plansthat implement a Node’s or Relationship’s Operations (e.g. a Bash script) • Deployment Artifacts: • Installables of the components(e.g. a TAR file) A service’s Topology Model is included in a TOSCA Service Template which is packaged and shared, along with all dependent artifacts, as a TOSCA Cloud Service Archive (CSAR)

17. TOSCA service templates can model any cloud application or infrastructure pattern TOSCA Service Templates Business Application Layer • Application Patterns • on either PaaS, IaaS platforms Service Oriented Applications Composition Layer compute Compute1, single Compute2, scalable app db Network1 Storage Network2 InfrastructurePatterns App. Resource Relationships Software Defined Environments compute • Generalized, Normative Types • OpenStack is one example PaaS Layer network storage IaaS Layer Platform and Infrastructure Resources Hardware • Derived, Custom Types Optimized Workloads Value: enables rapid and continuous delivery of diverse set of workloads with agility and optimization on programmable heterogeneous infrastructure leveraging reusable building blocks

18. TOSCAService Templates support … Full Lifecycle Orchestration • Go beyond simple deployment; services can provide instructions for any lifecycle operations enabling precise orchestration and control of application management tasks. Complete Topology Modeling • Allow developers to describe the topology of their applications and encapsulate their expert knowledge, including service configurations, policies and dependencies. Service Composability • Supports the ability to substitute logical parts of applications through composable service templates providing choice in both service vendor and implementation.

19. Primer Scenarios: Developing a “Single-Tier MySQL Database” Containment MySQLDatabase Database • Nodes can “Host” or contain other Nodes of specified types • Nodes can export the types of nodes they are “capable” of hosting, • These are matched to other nodes that export their specific host container “requirements” • In this example: • A MySQL Database node is “hostedOn” a “MySQL Database Management System (DMBS) node • The MySQL DBMS node, in turn, is “hostedOn” a “LinuxOS”, and so on… hostedOn MySQL DBMS Component “Containment” Relationship Type hostedOn MySqlLinuxOS Operating System hostedOn “Tier” is a topological concept used to describe sets of nodes (or sub-topologies) that can be deployed and managed as a single group MySqlVM Server hostedOn DBTier Tier

20. Primer Scenarios: “Two-Tier SugarCRM Web Application” DBTier Service Template Connectivity SugarCRMApp Web Application DependsOn • Nodes can “Connect” to other specified node types • Nodes export the types of nodes they require “require” connectivity to, • These are matched to nodes that export they are “capable” of accepting specific connections • In this example: • The SugarCRM Application node “connectsTo” a database node in another “tier” • The “DB Tier” components are packaged into a separate service template permitting Substitution SugarCRM Database Database ConnectsTo hostedOn hostedOn Apache WebServer PHPModule Apache Module MySQL DBMS hostedOn ApacheLinuxOS Operating System MySqlLinuxOS Operating System hostedOn MySqlVM Server ApacheVM Server Network “Connectivity” Relationship Type hostedOn DBTier Tier WebTier Tier Components grouped into composable service templates.

21. Advanced Scenarios: “ScalableSugarCRM Web Application” Scalability WebTier Service Template DBTier Service Template ApacheLB LoadBalancer • “Tier” Node Types convey scalability • The “Web Application Tier” is declared Scalablewith upper bounds “n” instances • Note: the “Database Tier” remains a single instance • A Load Balancer node is added to the previous template to route requests among “Web Application Tier” instances • Both tiers are packaged into their own service templates permitting Substitution SugarCRMApp Web Application SugarCRM Database Database Apache WebServer MySQL DBMS ApacheLinuxOS Operating System MySqlLinuxOS Operating System ApacheVM Server MySqlVM Server 1 1..n DBTier Tier WebTier ScalableTier The range of instances would be a property of the “Tier” Node Type Components grouped into composable service templates.

22. Overview – “Public TOSCA Interop. Demo” Widget.com Compliance Tools Hybrid Application Temporary 1 • Vnomic’s Service Designer Tool • Models the TOSCA Interop. Demo App: • 2-Tier SugarCRM App, MySQL Database 1 2 • Export of SugarCRM Application as TOSCA CSAR file • Format: Cloud Service Archive (CSAR) file • Export to a Cloud Marketplace or “AppStore” of TOSCA Modeled Applications and Services Service Designer 2 3 • TOSCA “Cloud Marketplace” • Customers can rapidly discover and implement cloud solutions from TOSCA Service Templates 3 Cloud Marketplace 4 • Download / Import of SugarCRM to choice of: • Runtime Interop. - TOSCA-enabled clouds for seamless deployment <or> • Tooling Interop. - TOSCA-enabled tools that can alter TOSCA Service Template models 4 4 4 4 5 • View SugarCRM in Cloud of Choice • Companies provide 3 minute video of SugarCRM in their tools or deployed to clouds • Companies can opt to show more if they desire and if asked to by press or analysts. IBM Workload Deployer (IWD) + IBM SmartCloud Huawei Cloud Fujitsu FlexFrame Note: Companies can choose to work with SAP (in advance) to demonstrate a SAP CRM model for private interop. events.