Post on 18-Jan-2018
description
transcript
TOSCA Interoperability Demonstration
Topology and Orchestration Specificationfor Cloud Applications
(TOSCA) Standard TOSCA Interoperability Demonstration Participating
Companies: Join the TOSCA Technical Committee Complete cloud
application modeling and orchestration
TOSCA Complete cloud application modeling and orchestration Enable
portability and 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 Management and
Operationalbehavior of these services facilitates higher levels of
Solution Portability: Portable deployment to any cloud that can
orchestrateTOSCA service templates Simplify migration of existing
customer apps. to cloud Dynamic, flexible scaling and bursting of
multi-cloudapplications Enables Software Defined Environments
(SDEs) Template contents provide the means to optimize
theunderlying cloud infrastructure Business Value TOSCA
Interoperability and Composition
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 Cloud A Cloud
C Cloud B Interoperability and Composition Goes beyond VMs in
describing the cloud applications components and their dependencies
Composition of services defined independently by their domain
expertsinto 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 FlexFrame
Orchestrator Service Delivery and Governance
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. FlexFrame Orchestrator Service Delivery and Governance Manage
Design Orchestrate Cloud Management and Automation Service Model
Monitoring Publish TOSCA Cloud ApplicationMarketplaces Telco Cloud
Solution SmartCloud and Workload Deployer Customize 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. TOSCA Conceptual Open Ecosystem
Enabling choice for cloud customers Wide Range of Open Source &
Commercial Tooling Orchestration ofTOSCA Apps in any TOSCA enabled
cloud Cloud Customers Architects and Developers can choose from
many open source and commercial tools to create, compose, update
and manage TOSCA Cloud Applications. Customers can seamlessly
deploy, run and manage any TOSCA applications in any TOSCA enabled
cloud. Design Deploy Manage Application Modeling & Management
Tools Cloud Providers Develop Cloud C Publish Cloud A Reuse Cloud B
Service Template Marketplaces Reusable, Composable TOSCA Service
Templates Companies & Software Providers can share TOSCA
service templates which have encapsulated their expert knowledge
using marketplacesfor others to reuse and extend. Scenario
Demonstration Elements
Demo participants demonstrating different parts of the TOSCA
Ecosystem * 1 TOSCA Application Modeling Tooling Interop.
Standardized modeling of cloud application services and
relationships Optionally, tools can directly deploy to clouds for
testing or production 1 Suite 1a Modeling 1a Cloud X 2 Publish
TOSCA Service Template to a sample cloud marketplace Using the
TOSCA Cloud Service Archive (CSAR) file format 2 3 Service Model
Monitoring 5 3 Share / Reuse TOSCA Templates Customers can rapidly
discover and compose cloud solutions from ready made templates
Marketplaces Monitoring 4 Deployment to Cloud Provider of Choice
Runtime Interop. seamless deployment to TOSCA-enabled clouds 4 4 4
4 5 Monitor TOSCA Cloud Applications Tooling Interop. granular
monitoring of application services described by TOSCA Cloud
Management and Automation Telco Cloud Solution FlexFrame
Orchestrator SmartCloud and Workload Deployer Cloud Providers *
Many of the participating companies have products that apply to all
parts of the ecosystem TOSCA Ecosystem: Modeling Tools
Architects and Developers can choose from many open source and
commercial tools to create, compose, update and manage TOSCA Cloud
Applications. 1 Demonstration shows a representative modeling tool
able to quickly compose and publish the TOSCA SugarCRM sample
application The 2-Tiers of the sampleTOSCA SugarCRM app: 1. Web
Applicatoin Tier Linux, Apache, PHP, SugarCRM 2. Database Tier
Linux, MySQL 2 Demonstration shows an export of the TOSCA SugarCRM
sample application to a representative cloud marketplace within a
TOSCA CSAR package TOSCA Ecosystem: Cloud Marketplaces
Companies & Software Providers can share TOSCA service
templates which have encapsulated their expert knowledge using
public or private marketplacesfor others to reuse and extend.
Demonstration shows a representative public cloud marketplace
showing the newly published TOSCA SugarCRM sample application (i.e.
a TOSCA Service Template, CSAR file) 3 TBD for Matt Change picture
FlexFrame Orchestrator SmartCloud and Workload Deployer
Share, Reuse & Deploy TOSCA Service Templates Demo participants
are demonstrating different parts of the TOSCA Ecosystem * 4
Demonstration shows choice of Cloud Providers, each able to
seamlessly Import (from the marketplace), deploy and run the same
TOSCA Service Template. Marketplace Choose which participating
companys cloud you wish to see a TOSCA service template imported
and deployed in. TOSCA Service Template Cloud Management and
Automation Telco Cloud Solution FlexFrame Orchestrator SmartCloud
and Workload Deployer Cloud Providers Customers can choose to
deploy and manage their TOSCA apps with many cloud providers that
support the TOSCA standard. Customers benefit from seamless TOSCA
Run-time portability
TOSCA Ecosystem: Cloud Provider Runtime Portability 4a
Demonstration shows successful login to the SugarCRM application
running at the chosen Cloud Provider using the address, user IDand
password provided withinthe TOSCA SugarCRMapplication Customers
benefit from seamless TOSCA Run-time portability 5 Monitoring of
TOSCA Service Instances
Demonstration shows the granular monitoring of application services
described by TOSCA Service Templates SugarCRM WebApp SugarCRM
Database Apache Web Server MySQL DBMS TOSCA-aware toolingcan enable
monitoring ofTOSCA service instancesrunning in the cloud. Apache
Linux OS MySql Linux OS Server Compute Server Compute Customers can
manage lifecycle and make adjustments to TOSCA defined services The
following slides provide details interoperability
demonstrations
on each participants interoperability demonstrations FUJITSU
FlexFrame Orchestrator
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 Import and deploy a TOSCA
SugarCRM model as well show how to deploy a TOSCA SAP model
HPs comprehensive management solution for heterogeneous clouds
provides you with all the management and governance capabilities
you need to automate service delivery for a successful hybrid
cloud. Deploy the SugarCRM Based on Tosca CSAR Package
ForTosca Demo Login portal Upload the CSAR package Step 1: Login
Step 2: Upload Ready Wait for implement installing configuring
Topology of the Application based on the CSAR Packageand the
Deploying Flow Status of each nodes descript in the CSAR Package
Step 3: Deploying Step 4: Deployment Successful 15 SugarCRM or SAP
CRM services offered in a service catalog
Demo TOSCA Service Templates import and deployment using IBM
SmartCloud Orchestrator Integrated tooling for TOSCA template
creation and editing Import and export of TOSCA v1.0 compliant
service templates Deploy-time composition of service templates
based on policies Integrated monitoring and scaling of deployed
services Import of the SugarCRM or SAP TOSCA applications into
ourintegrated application builder tool. SugarCRM or SAP CRM
services offered in a service catalog Deployed instances of
SugarCRM or SAP services with public IP addresses Demo designing,
publishing and deployingSugarCRM and SAP CRM TOSCA Service
Templates with Vnomic Suite Vnomic Service Designer Vnomic Suite:
Declarative Desired State Service Delivery and Governance for the
most complex applications and infrastructures Create TOSCA Service
Templates using modeled Components and Artifacts Compose Services
from existing deployments and component libraries Publish to
Marketplaces Import and Compose new Services Orchestrate TOSCA
Service Templates across diverse clouds and infrastructures Cloud X
Marketplaces Deploy from Marketplaces Model existing deployments
Vnomic Desired State Controller 17 Service Model Monitoring via
TOSCA
SAP service deployed with TOSCA orchestration Realized deployment
is instrumented for monitoring using TOSCA template along with
deployment information Results in deployment and operational
support of services based on IT policies Copyright Zenoss, Inc. 18
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
TOSCA Primer, Version 1.0 , Committee Note Draft 01, 31 January 31,
2013 TOSCA Implementer's Recommendations for Interoperable
TOSCAImplementations, Version 1.0, Working Draft 01,Revision 5,May
20, 2013 TOSCA Interop. Demo, SugarCRM Scenario Sample CSAR,
August, 2013
https://www.oasis-open.org/committees/download.php/50158/SugarCRM-Interop
zip More on TOSCA Modeling Modeling Topologies with TOSCA
Service Topologies are described using the TOSCA Meta-model: Nodes
Represent Components of an application or service andtheir
Properties. Example nodes include: Infrastructure: Compute,
Network, Storage, etc. Platform: OS,VM, DB, Web Server, etc.
Granular: functional Libraries, Modules, etc. Include Operations
which are the management functionsfor the node e.g. deploy(),
start(), stop(), connect(), etc. Export their dependencies on other
nodes as Requirement and Capabilities Relationships Represent the
logical Relationships between nodes e.g. hostedOn, connectsTo, etc.
Describes the valid Source and Target nodes they aredesigned to
couple e.g. source web application node is designed toconnect toa
target database node Have their own Properties and Constraints
Service Templates Group the nodes and relationships that make up
aservices topology Allowing modeling of sub-topologies Service
Templates look like nodes enabling: Composition of applications
from one or moreservice templates Substitution of abstract Node
types with availableservice templates of the same type Artifacts
Describe Installables and Executables required toinstantiate and
manage a service.Currently, theyinclude: Implementation Artifacts:
Executables or Plans that implement a Nodes orRelationships
Operations (e.g. a Bash script) Deployment Artifacts: Installables
of the components (e.g. a TAR file) A services 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) TOSCA service templates can model any cloud
application or infrastructure pattern
Business Application Layer TOSCA Service Templates Application
Patterns on either PaaS, IaaS platforms Composition Layer Service
Oriented Applications app db Software Defined Environments
Infrastructure Patterns App. Resource Relationships PaaS Layer
compute network storage OSS BSS DBaaS Generalized, Normative Types
OpenStack is one example IaaS Layer Compute Network Storage
Platform andInfrastructure Resources Hardware SLAs describe
attributes for operations, billing, availability, serviceability,
performance and penalties for violations Measures include (NIST):
Response Time,Automation, Agility, Linearity, Elasticity,
Durability, Load Balancing, Reliability, Throughput,Availability
compute Compute1, single Compute2, scalable Network2 Network1
Storage Derived, CustomTypes Optimized Workloads tmForum SLA
Standard: Service Level Agreement (SLA) The Service Level Agreement
serves as a means of formally documenting the service(s),
performance expectations, responsibilities and limits between cloud
service providers and their users. A typical SLA describes levels
of service using various attributes such as: availability,
serviceability, performance, operations, billing, and penalties
associated with violations of such attributes. Service Level
Agreements:are referenced by the master service level agreement.
They can contain: Business level objectives (BLO): Business Level
Objectives (often in form of a Business Policy) relate to the
measurements that are not service specific but impacting Cloud
Buyers business objectives such as disaster recovery, data privacy
etc. Service level objectives (SLO): SLOs are specific measurable
characteristics of the service being monitored.They are usually
specified in a Service Level Specifications (SLS) template. SLOs
are composed of one or more quality of service (QoS) objects or
Service Metrics Service Design Phase: Software factory tools and
processes can help govern and facilitate the Cloud service design
phase. These tools will be implemented according to standards of
Standardized Service Templates that contain information that will
contribute to the SLA calculation at the design phase, for example
a typical Response Time of 3-5 seconds. Service Deploy Phase:
System or policy engineer may provide additional information for
the specific deployment, such as response time must less than 4
seconds and using high-security encryption mechanism Service
Operation Phase: Monitoring and data retrieval activities happen.
The management applications need to have a consistent method to
access and/or retrieve and report from each instance of the
service.This can be achieved via SMI and the management and
monitoring threshold based on the information that is provided in a
catalogue/repository from various stakeholders. Value: enables
rapid and continuous delivery of diverse set of workloads with
agility and optimization onprogrammable heterogeneous
infrastructure leveraging reusable building blocks TOSCA Service
Templates support
Allow developers to describe the topology of their applications and
encapsulate their expert knowledge, including service
configurations, policies and dependencies. Complete Topology
Modeling Full Lifecycle Orchestration Go beyond simple deployment;
services can provide instructions for any lifecycle operations
enabling precise orchestration and control of application
management tasks. Supports the ability to substitute logical parts
of applications through composable service templates providing
choice in both service vendor and implementation. Service
Composability TOSCA supports Containment via the HostedOn
relationship
MySQLDatabase Database Nodes can host or contain other Nodes of
specified types Nodes can export the types of nodes theyare capable
of hosting, These are matched to other nodes thatexport their
specific host containerrequirements In this example: A MySQL
Database node is hostedOn aMySQL Database Management System(DMBS)
node The MySQL DBMS node, in turn, ishostedOn a Linux Operating
System, andso on hostedOn MySQL DBMS Component Containment
Relationship Type is called hostedOn 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 This service template
contains a reusable MySQL database tier. It includes the entire set
of dependent service component layers necessary for deploying a
standalone MySQL Database on a MySQL Database Management System
(DBMS). The DBMSrequired hosting environment is also described
which includes a Linux Operating System (OS), a Virtual Machine
(VM) container and Tier container which is used to logically group
them for overall management. hostedOn DBTier Tier TOSCA expresses
Connectivity relationships between service nodes
DBTier Service Template Connectivity SugarCRMApp Web Application
DependsOn Nodes can connect to other specified node types Nodes
export the types of nodesthey require connectivity to These are
matched to nodes thatexport they are capable ofaccepting specific
connections In this example: The SugarCRM Application
nodeconnectsToa database node inanother tier Note that the DB Tier
components are packaged into aseparate service templatepermitting
substitution SugarCRM Database connectsTo hostedOn hostedOn
PHPModule Apache Module Apache WebServer MySQL DBMS hostedOn
ApacheLinuxOS Operating System MySqlLinuxOS Operating System
hostedOn MySqlVM Server ApacheVM Server This service template
contains a typical, two-tier Apache Web Application customized to
host an open source Customer Relationship Mgmt. (CRM) application
called SugarCRM. The Web Tier includes the entire set of dependent
service components necessary for deploying the SugarCRM web
application on an Apache web server, with PHP Module support. Its
required hosting environment also includes a Linux Operating System
(OS), a Virtual Machine (VM) container and a Tier container to
logically group all related components. It also contains a
similarly composed MySQL Database Tier which the Web Tier connects
to during the SugarCRM Application's lifecycle. Network
Connectivity Relationship Type is named connectsTo hostedOn DBTier
Tier WebTier Tier Components grouped into composable service
templates. TOSCA Supports Scalability via the Tier Grouping
Node
ApacheLB LoadBalancer WebTier Service Template DBTier Service
Template Tier Node Types convey scalability The Web Application
Tier isdeclared scalable with upperbounds n instances Note: the
database tier remains asingle instance A Load Balancer node is
added tothe previous template to routerequests among WebApplication
Tier instances Both tiers are packaged into theirown service
templates permittingsubstitution of either SugarCRMApp Web
Application SugarCRM Database Apache WebServer MySQL DBMS
ApacheLinuxOS Operating System MySqlLinuxOS Operating System
ApacheVM Server MySqlVM Server This service template contains a
typical, two-tier Apache Web Application customized to host an open
source Customer Relationship Mgmt. (CRM) application called
SugarCRM. The components of both the Web Tier and Database Tier are
packaged into their own Service Templates to support
Substitutability.In this manner, the service template can be
treated as a pseudo-node exporting its aggregated requirements and
capabilities.In addition, the Web Tier is declared Scalable and the
composite applications template includes a Load Balancer node that
understands how to connect to and scale it. 1..n WebTier
ScalableTier 1 DBTier Tier The range of instances would be a
property of the Tier Node Type Components grouped into composable
service templates.