How TOSCA Adds Value in NFV world Topology and Orchestration Specification for Cloud Applications (TOSCA) Standard How TOSCA Adds Value in NFV world

Agenda TOSCA Overview How TOSCA can be used in NFV Many problems can be solved with TOSCA Some Open Source Implementations Openstack, Tacker, Parser, Senlin, alien4cloud, getCloudify Main Features containers, policies，network modeling, Template Examples VNFD, NSD

TOSCA Overview

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 (Nov 2013) Government and Corporate Awareness: OASIS: 600+ participant organizations. 5000+ participants spanning 65+ countries TOSCA Committee: 170+ people 45+ companies/orgs International Standards & Research: ETSI NFV liaison, EU FP7, etc. Industry Analysts: Forrester names TOSCA as a top four cloud open standard (Mar 2014) Multi-company Interoperability Demonstrated: EuroCloud 2013 (Oct 2013): IBM, SAP, Fujitsu, Huawei, HP, Vnomic, Zenoss and others Open Data Center Alliance: TOSCA Application Portability in the Enterprise Cloud PoC (Jan 2014) Associated Companies

TOSCA reduces application complexity independently from cloud provider Capabilities… by expressing application requirements… TOSCA Portable Cloud Application TOSCA Service Template Storage Compute1 DB Compute2 App Network Scaling Policy Application Requirements TOSCA Orchestration & Optimization Automatic Matching Infrastructure Capabilities Ring Network KVM Cloud Provider C Cloud Provider B PowerVM SSD RDMA Network Cloud Provider A 10 Gb Network X86 VM HDD Enabling TOSCA applications to be portable to different infrastructures

How TOSCA can be used in NFV Main features TOSCA can be provided Topology Composition Lifecycle

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. Defining node templates to describe components in the topology structure Defining relationship templates to describe connecting, dependency, deployment ordering VNF, VL can be defined as node templates in TOSCA. A new virtualLinksTo relationship type can be defined to connect VNF and VL. TOSCA can be used to describe the topology of a Network service or VNF as defined by ETSI NFV.

Composition NSD NFV information model has the layered structure. VNFD VLD VNFD VDU VLD NSD are composed of VNFD, VLD and PNFD VNFD VNFD are composed of VDU and VLD VNFD Using the TOSCA substitution feature, NFV information model can be described by using multiple TOSCA service templates

Lifecycle(added soon)

Some Open Source Implementations

(compute, network, storage) TOSCA in OpenSource Requirements Senlin Policy & Scaling TOSCA Templates tosca parser NSD VNFD VNFFGD OPNFV Parser NFVO/VNFM Operators NFV Orchestrator Tacker OpenStack Heat tosca heat-translator NFV Architects OpenStack VIM (compute, network, storage)

Main features

TOSCA Model for Containers leveraging Repositories PaaS Modeling Template author chooses to expose or hide runtime topology & implementation Container Application Modeling Agnostic of PaaS Cloud Provider PaaS on OpenStack, Cloud Foundry, Azure, etc. PaaS Subsystem (hidden) docker_mysql my_PaaS_platform Docker Hub (Repository) Container.App.Docker Container.Runtime Artifacts - my_image: type: Image.Docker URI: mysql repository: docker Capabilities Container Docker Image for mysql Runtime.Docker Hosted On Requirements ... Runtime.Nodejs Container Runtime.Docker ... Runtime.J2EE PaaS Layer exposes “runtimes” as TOSCA Capabilities Docker, Nodejs, JSP, J2EE, etc. 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 14 14

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 my_scaling_group 1 Policy Type Rule Trigger my_app_1 Compute Capabilities Container ... Lifecycle create configure backend_app Compute 3 web-app Compute my_database Compute Policy Type Rule Trigger Policies modeled as Requirements using Capability Types that can be attached to Interfaces or specific Operations Nodes and Groups of Nodes Abstract A key feature of any Cloud infrastructure is to provide auditing capabilities for compliance with security, operational and business processes. In this talk we provide an overview of the recent enhancements made in OpenStack projects to support API and security auditing using the DMTF Cloud Auditing Data Federation (CADF) standard. We will describe how auditing is seamlessly enabled for Nova, Glance, Swift, Cinder, Neutron and Keystone and illustrate what is audited, where it is stored, what the records contain and how this supports compliance. We will finish by presenting some possible future directions such as extending the use of CADF beyond audit to facilitate event correlation and federation across multiple tiers. 15 15

TOSCA Model for Logical Public & Private Cloud Networks my_app_1 Compute Attributes private_address public_address networks ports Capabilities Container ... Bindable Connected via logical Ports nodes (via LinksTo and BindsTo) port_1 Port Capabilities Linkable Requirements Bindable BindsTo LinksTo private_net_1 Network Capabilities Linkable port_2 Port Capabilities Linkable Requirements Bindable Application Model separate from Network Model BindsTo LinksTo public_net_1 Network Capabilities Linkable Allows developers to model JUST the application bind to existing tenant networks 16 16

NFV use case example

VNFD example Page 18

NSD example Page 19

Using TOSCA group concept 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 Resources – Learn More TOSCA Technical Committee Public Page (latest documents, updates, and more) https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=tosca OASIS Channel (all standards) or TOSCA YouTube Playlist https://www.youtube.com/user/OASISopen or http://bit.ly/1BQGGHm TOSCA Simple Profile in YAML v1.0 (latest committee approved draft) http://docs.oasis-open.org/tosca/TOSCA-Simple-Profile-YAML/v1.0/TOSCA-Simple-Profile-YAML- v1.0.pdf TOSCA Simple Profile for NFV v1.0 (latest committee approved draft) http://docs.oasis-open.org/tosca/tosca-nfv/v1.0/csd02/tosca-nfv-v1.0-csd02.pdf Contact the Technical Committee Co-Chairs: Paul Lipton, paul.lipton@ca.com Simon Moser, smoser@de.ibm.com Today’s Presenters from the TOSCA TC: Shitao Li, lishitao@huawei.com Matt Rutkowski, mrutkows@us.ibm.com Chris Lauwers, lauwers@ubicity.com Sridhar Ramaswamy , sramasw@Brocade.com Sivan Barzily, sivan@gigaspaces.com Find out more about TOSCA through these links and contacts.

Start Blueprinting Your Cloud Apps in TOSCA now! An Open Standard for Business Application Agility and Portability in the Cloud Q&A Start Blueprinting Your Cloud Apps in TOSCA now!