- Количество слайдов: 25
TOSCA Topology and Orchestration Specification for Cloud Applications (TOSCA) Standard OASIS TOSCA presentation to ETSI NFV Information Modelling Workshop Proposal for way forward-How TOSCA Adds Value in NFV world
Agenda ▪ TOSCA Overview ▪ Way forward-How TOSCA can be used in NFV ‒ Many problems can be solved with TOSCA ▪ Some Open Source Implementations ‒ Openstack, Tacker, Parser, Senlin, alien 4 cloud, Cloudify ▪ Main Features ‒ containers, policies，network modeling, ▪ Template Examples ‒ VNFD, NSD 2 2
TOSCA Overview 3
What is TOSCA? • TOSCA is an important new open cloud standard, that is enabling a unique eco-system, supported by a large and growing number of international industry leaders… • TOSCA Version 1. 0 Specification approved as an OASIS Standard • Government and Corporate Awareness: (Nov 2013) Associated Companies – OASIS: 600+ participant organizations. 5000+ participants spanning 65+ countries – TOSCA Committee: 170+ people 45+ companies/orgs – International Standards & Research: ETSI NFV liaison, EU FP 7, etc. • – Industry Analysts: Forrester names TOSCA as a top four cloud open standard (Mar 2014) Multi-company Interoperability Demonstrated: – Euro. Cloud 2013 (Oct 2013): IBM, SAP, Fujitsu, Huawei, HP, Vnomic, Zenoss and others – Open Data Center Alliance: TOSCA Application Portability in the Enterprise Cloud Po. C (Jan 2014) 4
Way forward-How TOSCA can be used in NFV Many problems can be solved with TOSCA Topology Composition Lifecycle Portability • •
Topology As the Topology and Orchestration Specification for Cloud Applications, TOSCA is mainly used to describe the topology of the deployment view for cloud applications. l l Defining node templates to describe components in the topology structure Defining relationship templates to describe connecting, dependency, deployment ordering TOSCA can be used to describe the topology of a Network service or VNF as defined by ETSI NFV. VNF, VL can be defined as node templates in TOSCA. A new virtual. Links. To relationship type can be defined to connect VNF and VL.
Composition Any node in a TOSCA topology can be an abstraction of another layer or subtopology NFV information model has the layered structure. • NSD are composed of VNFD, VLD, PNFD and etc. • VNFD are composed of VDU, VLD and etc. NSD VNFD VLD VNFD VDU VLD VDU Using the TOSCA substitution feature, NFV information model can be described by using multiple TOSCA service templates
Lifecycle TOSCA models have a consistent view of state-based lifecycle ü have Operations (implementations) that can be sequenced against state of any dependent resources ü fits into any Management Framework or Access Control System Standardize Resource Lifecycle Standardize Relationship Lifecycle source_resource my_relationship target_resource my_resource_name Type_A Connects. To Type_B My_Resource_Type A configure start stop delete Lifecycle. Standard Lifecycle. Configure pre_config_source pre_config_target create Operations create Lifecycle. Configure. NFV B Lifecycle. Standard add_source configure start nfv_pre_delete add_target remove_source nfv_pre_config stop post_config_source post_config_target remove_target Operations ü ü Lifecycle Customization delete Create new NFV Lifecycles or Augment existing (via subclassing) Parameters and Policies can be supplied to operations to affect resource behavior (state) Workflow - TOSCA is developing workflow to allow handling complex state changes, configurations, etc. TOSCA Lifecycle can be customized for NFV Resources and Relationships
Portability TOSCA Portable Cloud Application TOSCA Service Template App DB Compute 1 Compute 2 Network Scaling Policy By expressing application requirements independently from cloud capabilities and implementation, TOSCA provides: - Multi VIM Support Storage - Portability of services across clouds - Declarative model spanning infrastructure and service TOSCA Orchestration - Manipulate the orchestration declaratively instead of dealing with disparate cloud APIs (leave that to the TOSCA Orchestrator) TOSCA enables NFV applications flexible movement between different cloud infrastructures.
Some Open Source Implementations • • • Senlin Tacker Parser Alien 4 cloud Cloudify
TOSCA in Open. Source Openstack Heat-translator Deployment Template. Translation Senlin Policy (Placement&scaling) Cloudify Service Orchestration & Management seaclouds www. seaclouds-project. eu/media. html Tacker Opensource MANO OPNFV Parser Deployment Template. Translation alien 4 cloud Topology & LCM Design http: //alien 4 cloud. github. io/ 11
Automated TOSCA-based Orchestration Now Part of Open. Stack TOSCA Template TOSCA Types TOSCA Nodes Map Generate Validation Tests TOSCA Parser • HOT Generator TOSCA-to-Heat-Translator now part of Open. Stack Heat l Latest TOSCA features integrated: Networking, Block & Object Storage. . . HOT - Heat Orchestration Template Deploy Heat l Implemented TOSCA relationship templates, custom types l Availability to use on command line & user input param support • Orch New features in Liberty release and plans for Mitaka l Murano (Application catalog integration) with Open. Stack client l TOSCA parser available as independent Python library l TOSCA Policy schema and Group schema l HOT Generator now supports additional plug-ins to allow translation to other DSLs besides HOT, such as Kubernetes Open. Stack Services 12
Open. Source related to ETSI NFV and OASIS TOSCA Openstack Senlin Policy ETSI NFV Descriptor Data modeling OASIS TOSCA OPNFV Parser NSD VNFFGD Requirements NFV Architects Operators ETSI NFVO/VNFM reference Openstack Tacker Openstack tosca-heat-translator reference OPNFV parser Open. Stack VIM (compute, network, storage) 13
Main features • • • Container Policies Network modeling
TOSCA Model for Containers leveraging Repositories Paa. S Modeling Container Application Modeling • Template author chooses to expose or hide runtime topology & implementation • Agnostic of Paa. S Cloud Provider – Paa. S on Open. Stack, Cloud Foundry, Azure, etc. Paa. S Subsystem (hidden) docker_mysql my_Paa. S_platform Container. App. Docker Artifacts Container. Runtime - my_image: Capabilities Container Runtime. Docker Runtime. Nodejs . . . Runtime. J 2 EE Paa. S Layer exposes “runtimes” as TOSCA Capabilities • Docker, Nodejs, JSP, J 2 EE, etc. Hosted On type: Image. Docker URI: mysql repository: docker Requirements Container Docker Hub (Repository) Docker Image for mysql Runtime. Docker . . . Orchestrators could automatically retrieve and deploy a Docker image from a declared Repository • TOSCA Templates can model repositories • Orchestrators could dynamically “pull” from multiple repositories 15
TOSCA Direction to model Policies Supported areas: Placement (Affinity), Scaling and Performance ‒ with Rules that are evaluated to execute Automatic and Imperative Triggers 2 Policy • Type • Rule • Trigger 1 Policy • Type • Rule • Trigger my_app_1 my_scaling_group backend_app Compute Capabilities Container Lifecycle create configure . . . 3 Policy • Type • Rule • Trigger web-app Compute my_database Compute Policies modeled as Requirements using Capability Types that can be attached to ‒ Interfaces or specific Operations ‒ Nodes and ‒ Groups of Nodes TOSCA defines policies using an Event-Condition-Action model 16
TOSCA Model for Logical Public & Private Cloud Networks my_app_1 Compute Attributes • private_address • public_address • networks • ports port_1 Capabilities Container . . . Port Binds. To • Connected via logical Ports nodes (via Links. To and Binds. To) Requirements Bindable Capabilities Linkable Links. To private_net_1 Network Capabilities Linkable port_2 Port • Application Model separate from Network Model Binds. To Requirements Bindable Capabilities Linkable Links. To public_net_1 Network Capabilities Linkable Allows developers to model JUST the application bind to existing tenant networks 17
Backup slides sample template Lifecycle Sequencing 18
VNFFG – Using TOSCA group concept Source: xxx
NFP Network forwarding path as defined by ETSI NFV is an order list of connection points forming a chain of network functions (VNFs or PNFs). A new “Forwarder” requirement is defined in this specification to model the network forwarding path by using ordered list of multiple “Forwarder” requirements. Each “Forwarder” requirement points to a single connection point.
TOSCA Orchestrators - Standardized Lifecycle Sequencing Source-Target Sequencing Lifecycle. Configure Lifecycle. Standard Deploy Sequencing Undeploy Sequencing Combined Sequencing
TOSCA Resources – Learn More • TOSCA Technical Committee Public Page (latest documents, updates, and more) • OASIS Channel (all standards) or TOSCA You. Tube Playlist • TOSCA Simple Profile in YAML v 1. 0 (latest committee approved draft) • TOSCA Simple Profile for NFV v 1. 0 (latest committee approved draft) • Contact the Technical Committee Co-Chairs: – Paul Lipton, paul. [email protected] com – Simon Moser, [email protected] ibm. com • Today’s Presenters from the TOSCA TC: – Shitao Li, [email protected] com – Matt Rutkowski, [email protected] ibm. com – Chris Lauwers, ubicity. com – Sridhar Ramaswamy , [email protected] com – Sivan Barzily, [email protected] com – https: //www. oasis-open. org/committees/tc_home. php? wg_abbrev=tosca • https: //www. youtube. com/user/OASISopen or http: //bit. ly/1 BQGGHm • http: //docs. oasis-open. org/tosca/TOSCA-Simple-Profile-YAML/v 1. 0/TOSCA-Simple-Profile-YAMLv 1. 0. pdf – http: //docs. oasis-open. org/tosca-nfv/v 1. 0/csd 02/tosca-nfv-v 1. 0 -csd 02. pdf 24
TOSCA An Open Standard for Business Application Agility and Portability in the Cloud Q&A Start Blueprinting Your Cloud Apps in TOSCA now! 25 25