15
Portable, Interoperable Cloud Applications using TOSCA Topology and Orchestration Specification for Cloud Applications (TOSCA) Standard Demonstrated using: Vnomic’s Service Designer, IBM ISM Cloud Marketplace and IBM Workload Deployer (IWD)

Portable, Interoperable Cloud Applications using TOSCA · Portable, Interoperable Cloud Applications using TOSCA ... Business Value of TOSCA Open Ecosystem for ... Composing a TOSCA

  • Upload
    hakhue

  • View
    229

  • Download
    0

Embed Size (px)

Citation preview

Portable, Interoperable Cloud Applications using TOSCA

Topology and Orchestration Specification for

Cloud Applications (TOSCA) Standard

Demonstrated using:

Vnomic’s Service Designer, IBM ISM Cloud Marketplace and

IBM Workload Deployer (IWD)

Business Value of 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

1

Demo Messaging – TOSCA Enables…

Portability

– Specified package format: Cloud Service Archive (CSAR)

– Includes Topology of Application Components, Artifacts and their Relationships / Dependencies

– Encapsulates “Expert Knowledge” of the service designer / architect

Interoperability

– Complete Tool and Runtime Interoperability

Lifecycle Management

– Each Component Exports its own Granular Lifecycle Management Operations

2

Composing a TOSCA Service Template for a “SugarCRM” Application

3

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)

Vnomic’s Service Designer tool supports TOSCA“Deployment” directly to various Clouds

…including IBM’s SmartCloud Enterprise

4

for this demo, we choose to publish the “SugarCRM” Cloud Application

to IBM’s Integrated Service Mgmt. (ISM) Cloud Marketplace

which encapsulates the Application Architect’s “Expert Knowledge”

5

The Cloud Application is made “Portable” and packaged

using TOSCA’s Cloud Service Archive (CSAR) format

Showing “SugarCRM” as a newly published service by Vnomic into IBM’s “Cloud Marketplace”

Demonstrating the vision of an “Open Ecosystem” of cloud services based upon TOSCA standardized service templates

TOSCA service templates could be published and shared on

both public and private marketplaces

6

SugarCRM Overview / Description of Service

Customers can use such marketplaces to get information on published TOSCA cloud services to select those that best meet their needs

… as well as share fellow customer experiences, learn about

service licensing and support

7

SugarCRM Topology / Properties

The “Topology” of the application and each component’s properties can also be inspected as published within the TOSCA service template

8

Downloading / Exporting the “SugarCRM” Application’s CSAR

9

… another company wants to use “SugarCRM” in their cloud and decides to download the CSAR from the marketplace for their developers to work with.

“SugarCRM” Imported into IBM Workload Deployer (IWD)

10

… using the Cloud Service Archive (CSAR) for the “SugarCRM” app,

which was downloaded from the IBM Cloud Marketplace

Demonstrating Seamless TOSCA “Tool” Portability

The “SugarCRM” Application’s Topology Template Viewed in IWD

11

… developers can choose to edit the components’ properties or simply use the defaults settings packaged in the CSAR file prior to deployment

Web Server Tier (left), Database Tier (right)

The “SugarCRM” TOSCA Application is Fully Deployed and Running using IBM SmartCloud Foundation Services

12

… we can see that both the Web Server and Database Tiers are running

and assigned Public IP Addresses

Login to “SugarCRM” application running on an IBM Cloud

13

… 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

Demonstrating Seamless TOSCA “Run-time” Portability

Learn More! - TOSCA Resources

TOSCA Specification, Version 1.0

Committee Specification 01, 18 March November 2013,

http://docs.oasis-open.org/tosca/TOSCA/v1.0/cs01/TOSCA-v1.0-cs01.pdf

TOSCA Primer, Version 1.0

Committee Note Draft (CND) 01, Public Review Draft 01, 31 January 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

Interoperability Subcommittee, Working Draft 01, Rev. 02, 14 January 2013,

http://www.oasis-open.org/committees/document.php?document_id=47888&wg_abbrev=tosca-interop

TOSCA Interoperability Subcommittee, SugarCRM Scenario Sample CSAR

Preliminary Draft CSAR for Interop. Testing against TOSCA v1.0 Specification

http://www.oasis-open.org/committees/document.php?document_id=47585&wg_abbrev=tosca-interop

14