1. 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

2. 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, alien4cloud, Cloudify
Main Features
containers, policies，network modeling,
Template Examples
VNFD, NSD

3. TOSCA Overview

4. 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: participant organizations 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

5. Way forward-How TOSCA can be used in NFV
Many problems can be solved with TOSCA
Topology
Composition
Lifecycle
Portability

6. 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.

7. Composition
Any node in a TOSCA topology can be an abstraction of another layer or subtopology
NSD
VNFD
NFV information model has the layered structure.
NSD are composed of VNFD, VLD, PNFD and etc.
VNFD are composed of VDU, VLD and etc.
VNFD
VLD
VNFD
VDU
VLD
VNFD
Using the TOSCA substitution feature, NFV information model can be described by using multiple TOSCA service templates

8. 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 Relationship Lifecycle
Lifecycle Customization
Standardize Resource Lifecycle
source_resource
Type_A
my_relationship
ConnectsTo
target_resource
Type_B B
Lifecycle.Configure.NFV
my_resource_name
My_Resource_Type
Lifecycle.Standard A
create
Lifecycle.Standard
nfv_pre_config
create
configure
start
stop
delete
Lifecycle.Configure
Operations
configure
start
pre_config_source
post_config_source
add_source
remove_source
pre_config_target
post_config_target
add_target
remove_target
Operations
stop
nfv_pre_delete
delete
Operations
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

9. Portability TOSCA TOSCA Orchestration
By expressing application requirements independently from cloud capabilities and implementation,
TOSCA provides:
- Multi VIM Support
- Portability of services across clouds
- Declarative model spanning infrastructure and service
- Manipulate the orchestration declaratively instead of dealing with disparate cloud APIs (leave that to the TOSCA Orchestrator)
TOSCA
Portable
Cloud
Application
TOSCA Service Template
Storage
Compute1 DB
Compute2
App
Network
Scaling
Policy
TOSCA
Orchestration
TOSCA enables NFV applications flexible movement between different cloud infrastructures.

10. Some Open Source Implementations
Senlin
Tacker
Parser
Alien4cloud
Cloudify

11. TOSCA in OpenSource Openstack Deployment TemplateTranslation
Heat-translator
Senlin
Tacker
Opensource MANO
Policy (Placement&scaling)
Cloudify
OPNFV
Parser
Service Orchestration & Management
Deployment TemplateTranslation
alien4cloud
seaclouds
Topology & LCM Design

12. Automated TOSCA-based Orchestration Now Part of OpenStack
Template
HOT - Heat Orchestration Template
TOSCA Types
TOSCA Nodes
Map
Generate
Validation
Tests
Validation
Tests
TOSCA Parser
HOT Generator
Deploy
TOSCA-to-Heat-Translator now part of OpenStack Heat
Latest TOSCA features integrated: Networking, Block & Object Storage...
Implemented TOSCA relationship templates, custom types
Availability to use on command line & user input param support
New features in Liberty release and plans for Mitaka
Murano (Application catalog integration) with OpenStack client
TOSCA parser available as independent Python library
TOSCA Policy schema and Group schema
HOT Generator now supports additional plug-ins to allow translation to other DSLs besides HOT, such as Kubernetes
Heat
Orch
OpenStack Services

13. OpenSource related to ETSI NFV and OASIS TOSCA
Openstack
Senlin
OPNFV
Parser
NFV
Architects
Requirements
Policy
NSD
VNFD
VNFFGD
ETSI NFV Descriptor
Operators
ETSI NFV NFVO/VNFM
Data modeling
Openstack
tosca-heat-translator
reference
OASIS
TOSCA
Openstack Tacker
reference
OPNFV
parser
OpenStack VIM
(compute, network, storage)

14. Main features
Container
Policies
Network modeling

15. 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 15 15

16. 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.
TOSCA defines policies using an Event-Condition-Action model 16 16

17. 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 17 17

18. Backup slides sample template Lifecycle Sequencing

19. VNFD example
Page 19

20. NSD example
Page 20

21. Using TOSCA group concept
VNFFG
Using TOSCA group concept
Source: xxx

22. 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.

23. Source-Target Sequencing
TOSCA Orchestrators - Standardized Lifecycle Sequencing
Lifecycle.Standard
Deploy Sequencing
Lifecycle.Configure
Source-Target Sequencing
Undeploy Sequencing
Combined Sequencing

24. TOSCA Resources – Learn More
TOSCA Technical Committee Public Page (latest documents, updates, and more)
OASIS Channel (all standards) or TOSCA YouTube Playlist or
TOSCA Simple Profile in YAML v1.0 (latest committee approved draft)
v1.0.pdf
TOSCA Simple Profile for NFV v1.0 (latest committee approved draft)
Contact the Technical Committee Co-Chairs:
Paul Lipton,
Simon Moser,
Today’s Presenters from the TOSCA TC:
Shitao Li,
Matt Rutkowski,
Chris Lauwers,
Sridhar Ramaswamy ,
Sivan Barzily,
Find out more about TOSCA through these links and contacts.

25. 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!