nfv ecosystem enabler - a well-enabled vnf package catalyst

© 2016 TM Forum | 1

NFV Ecosystem Enabler:A well-enabled VNF package

master deck

© 2016 TM Forum | 2

Problem Statement

ProcurementWhen I buy a Network Service or VNF

What is in the box?

How do I determine it is fit for purpose?

How do I acceptance test it?

And when should I pay for it?

OperationsWhen a Network Service or VNF is delivered, how

do I manage and onboard into my organization?

What management tools does it support?

And how will I manage it automatically within my IT

and network operations?

Service providers are faced with some simple, but surprisingly hard

to answer business questions in NFV transformation:

© 2016 TM Forum | 3

Solution Approach & Project Scope

Develop

• Design

• Develop

• Test

Deliver

• Package

• Validate

• Accept and catalogue (onboard)

Deploy

• Combine

• Assemble

• Configure (software)

Use

• Service design

• Configure (service)

• Instantiate

Manage

• Monitor

• Update

• Upgrade

Retire

Migrate User

Template-based, well-enabled packages for automated onboarding1

Network DevOps principles & governance for service design & creation

Autonomic computing blueprint approach for deployment orchestration

& lifecycle management

2

3

VNF Supplier VNF Supplier/

Service provider

(procurement)

Service provider

(Service design)

Service provider

(Service Delivery)

Service provider

(Service Assurance)

© 2016 TM Forum | 4

Catalyst Participants

Champions:

Solution Providers:

Collaboration Communities:

© 2016 TM Forum | 5

User Stories - Smart City NFV Ecosystem

© 2016 TM Forum | 6

Technology Highlights

Service Design &

Creation

Environment

Marketplace, Catalogs

& Deployment

Blueprints

Deployment

Orchestration &

Lifecycle Management

VNF

VNF

VNF

VNF

VNF

Model Driven

Network DevOps Autonomic ComputingGaming Engine

Focus: Business layer abstraction & orchestration

© 2016 TM Forum | 7

Demo - Onboarding

Develop

• Design

• Develop

• Test

Deliver

• Package

• Validate


Deploy

• Combine

• Assemble


Use

• Service design


• Instantiate

Manage

• Monitor

• Update

• Upgrade

Retire

Migrate User





2

3


Service provider

(procurement)

Service provider

(Service design)

Service provider

(Service Delivery)

Service provider

(Service Assurance)

© 2016 TM Forum | 8

Introducing TOSCA

Topology and Orchestration Specification for Cloud Applications

Standardizes a language to describe

The structure of a service(aka its “topology”) consisting of Nodes and Relationships

The operational behavior of a service(aka “orchestration”)

By means of plans leveraging the BPMN standard

Declarative model spanning from applications to virtual and physical infrastructure

Leveraging and extending the reach of existing standards (e.g. OVF, CIM, SCA, …)

8

Topology Orchestration

© 2016 TM Forum | 9

A well-enabled package

= TOSCA template + additional metadata

Metadata:

Attributes to support procurement decisions, deployment

options & lifecycle management, examples:

• Procurement Model

• make, buy, rent

• Maturity Model

• softwarelized, virtualized,…

• Usage Model

• entitlement, capacity,…

• SLA Model

• KPI/KQI, metrics,…

© 2016 TM Forum | 10 10

Scope Governance Standards

Procurable VNF Package Service Providers To be defined by the TM

Forum

Supplier VNF Package Suppliers ETSI VNF Package/IFA011,

TOSCA, Docker, Other

standards

Supplier Run time Deployment

Module

Suppliers + Service Providers Standard for Containers

Packaging Layer of Abstraction & Scope

TM Forum IG1141 scope Catalyst scope

© 2016 TM Forum | 11 11

TOSCA enables holistic application lifecycle automation

11

TOSCA Templates Agnostic to Cloud Infrastructure Changes

Architects

Model services, policies &

requirements

Development Teams

Develop, unit test scripts, plans & artifacts for

planned releases, patches, fixes

QA Teams

Build & Test releases, updates &

configurations

Operations

Deploy, manage& monitor application

lifecycle

Cloud Provider A

Cloud Provider C

Cloud Provider B

TOSCATemplate

Cloud Application Lifecycle with TOSCA

TOSCATemplate

TOSCATemplate

TOSCATemplate

TOSCATemplate

Infrastructure Changes

Hot Packs

Strategic Requests

Operational Requests

External

Influences

Business

Conditions

TOSCA templates communicate and drive app-centric Dev-Ops and continuous delivery

© 2016 TM Forum | 12 12

Introducing Network DevOps

Accelerate

Network Service delivery –

for faster time to value

Balance speed, cost,

quality and risk –

for increased capacity to

innovate

Reduce time to customer

feedback – for improved

customer experience

Continuous Customer

Feedback &

Optimization Collaborative Network

Development

Continuous Network

Release and Deployment

Continuous

Monitoring

Continuous Network

Business Planning

Continuous Testing

through development and

deployment

Operate Develop/ Test

Deploy

Fulfillment

Design

End-to-End Service Delivery

Design

Develop

Test

Package

Validate

Accept and catalogue (onboard)

Combine

Assemble

Configure (software)

Service design

Configure (service)

Instantiate

Monitor

Update

Upgrade

Service provider

(Service Assurance)

Service provider

(Service Delivery)

Service provider

(Service Design)

VNF Supplier/

Service provider

(procurement)

VNF Supplier

© 2016 TM Forum | 13

Days

<10%

Quarters

35%

Months

40%

Weeks

15%

6-12 Month Delivery Cycles Are STILL Normal for most

Delivery cycle profile across 600 business enterprises

Feedback cycles

Source--The New Software Imperative: Fast Delivery With Quality: 8 DevOps Practices Hold The Key To Success

A Forrester Consulting Thought Leadership Paper Commissioned By IBM, August 2014

© 2016 TM Forum | 14

What is the WASTE we are trying to remove?

Manual Efforts

• Deployments require human intervention

• Reliance on scripts

• Environment configuration is done on an “as-needed” basis

Long Wait Times

• Teams waiting on manual handoffs

• Resources not available when needed

• Delayed time-to-test

• Insufficient notification

Unproductive Work

• Using static environments

• Deploying things that have not changed

• Managing infrastructure & apps separately

• Not leveraging virtualization & cloud correctly

Poor Visibility

• Reliance on spreadsheets, meetings, con calls to know status

• Limited understanding of deployment dependencies and status

• Long Outage windows

© 2016 TM Forum | 15

How those WASTE can be eliminated?

Remove Manual Efforts

• Push-button Deployments

• Graphical process designer

• Manage Environment configuration as part of deployment

Eliminate Long Wait Times

• Automated Notifications

• Include provisioning as part of deployment

• Add testing to deployment process

• Immediate feedback

Reduce Unproductive Work

• Leverage production-like environments

• Only deploy what has changed

• Managing infrastructure & apps together

• Get the most out of virtualization & cloud

Raise Visibility

• Known status of resources at-a-glance

• Immediate view of deployment compliance

• Status, feedback & understanding of all parts of deployment as it occurs

© 2016 TM Forum | 16 16

UrbanCode for Release and Deployment automation

Drive down costReduce amount of manual labor, resource wait-time,

and rework by eliminating errors & providing self-service

environments

Speed time to marketIncrease frequency of software delivery through

automated, repeatable deployment processes across

development, test and production

Reduce risk

Robust configuration management, coordinated release

processes, audits, and traceability

Enabling more rapidly deliver mobile, cloud, big data and traditional applications with high

quality and low risk

IBM UrbanCode Deploy with Patterns is a full-stack environment

management and deployment solution that enables users to design,

deploy and update full-stack environments to multiple clouds

IBM UrbanCode Deploy automates the deployment of applications,

databases and configurations into development, test and production

environments, helping to drive down cost, speed time to market with

reduced risk.

IBM UrbanCode Release is an intelligent collaboration release

management solution that replaces error-prone manual spreadsheets

and streamlines release activities for application and infrastructure

changes.

© 2016 TM Forum | 17

Demo – Deployment & LCM

Develop

• Design

• Develop

• Test

Deliver

• Package

• Validate


Deploy

• Combine

• Assemble


Use

• Service design


• Instantiate

Manage

• Monitor

• Update

• Upgrade

Retire

Migrate User





2

3


Service provider

(procurement)

Service provider

(Service design)

Service provider

(Service Delivery)

Service provider

(Service Assurance)

© 2016 TM Forum | 18

Leveraging Standards and Open Sources

OASIS/TOSCA

Deployment Templates

NFV Infrastructure & VIM

OPNFV Brahmaputra Release

with associated tools.

Service chaining, Deployment

& Management

TM Forum APIs: Onboarding, Catalogue APIs

© 2016 TM Forum | 19

Autonomic Management (M-A-P-E)

19

*An autonomic manager can be a managed element

Monitor

Analyze Plan

ExecuteState

Sensors Effectors

Enrich

Delegate

Autonomic

Manager*

Sensors Effectors

Escalate

Managed

Element

© 2016 TM Forum | 20 20

Service Chaining & Deployment

20

NFV Package is chosen in

UrbanCode

Add to catalog -UrbanCode posts TOSCA blueprint

to AMP

AMP tests blueprint in OpenStack

NFV Package listed in AMP

catalog for use by blueprint

authors

Blueprint authors compose applications

• Use NFV Package as part of larger app;

• or Service Chaining of NFV packages

Deploy app to OpenStack multi-

region environment

Cloudsoft Automated Workflow

© 2016 TM Forum | 21 21

User Experience

Dynamic 3D Model of

Cloudsoft Managed

Cloud Application

Visualize the

NFV Ecosystem Enablers

Business Scenario

© 2016 TM Forum | 22

Example: Ambulance App

App composed of:

NFV Packages: load balancer,

firewall, IPS

Front-end load balancer + firewall +

IPS

HA app-server cluster

Riak multi-region

Sensor ingress to app-server

cluster

(via load balancer + firewall)

Elements shown as ”child” buildings

© 2016 TM Forum | 23

Project Contributions

ZOOM IG1141:

VNF Package Metadata

ZOOM IG1139:

Autonomic Computing

Pattern-based Orchestration & LCM

TM Forum APIs

Monitor

Analyze Plan

ExecuteState

Sensors Effectors

Enrich

Delegate

Autonomic

Manager*

Sensors Effectors

Escalate

Managed

Element

© 2016 TM Forum | 24

Future Plan - Smart City NFV Ecosystem

Smart Cities Local Government

VNF SuppliersService Providers

Innovation

.

Agility

.

Experience

• Refined procurement & onboard requirements, metadata to support smart city/IoT

• e.g. maturity model, software/device & license management

• Refined package LCM, run time configuration, toolchain and standards

recommendations

• Additional collaborations with other SDOs and open source implementations.

© 2016 TM Forum | 25

Backup Slides

© 2016 TM Forum | 26

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…

What is TOSCA?

Associated Companies• TOSCA Version 1.0 Specification approved as an OASIS Standard (published Nov 2013)

• TOSCA Simple Profile v1.0 Specification (YAML) final public review draft, Aug 2014)

• 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:

– OSCON 2015, Open Data Center Alliance 2014, EuroCloud 2013

26

© 2016 TM Forum | 27

Topology

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 virtualLinksTo relationship type can be

defined to connect VNF and VL.

Primarily, 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 connections, dependencies, deployment

ordering

27

© 2016 TM Forum | 28

Topology & Composition

NSDVNFD

VNFD

VLD

VDU

VDU

VLD

Using the TOSCA substitution feature, NFV information model can be

described by using multiple TOSCA service templates

VNFD

VNFD

Any node in a TOSCA topology can be an abstraction of another layer or sub-topology

NFV information model has such a layered

structure:

NSDs are composed of VNFDs, VLDs, PNFDs, etc.

VNFDs are composed of VDUs, VLDs, etc.

28

© 2016 TM Forum | 29

LifecycleTOSCA 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

my_resource_name

My_Resource_Type

Lifecycle.Standard

create

configure

start

stop

delete

Standardize Resource Lifecycle Standardize Relationship Lifecycle Lifecycle Customization

source_resource

Type_A

A

target_resource

Type_B

B

my_relationship

ConnectsTo

Op

era

tio

ns Lifecycle.Configure

pre_config_target

post_config_target

add_target

remove_target

pre_config_source

post_config_source

add_source

remove_source

Operations

Lifecycle.Configure.NFV

Op

era

tio

ns

Lifecycle.Standard

create

configure

start

stop

delete

Create new NFV Lifecycles or

Augment existing (via subclassing)

nfv_pre_config

nfv_pre_delete

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 29

© 2016 TM Forum | 30

Portability from Standardization

TOSCAPortableCloudApplication

TOSCA Service Template

Storage

Compute1

DB

Compute2

App

Network

ScalingPolicy

TOSCAOrchestration

TOSCA enables NFV applications flexible movement

between different cloud infrastructures.

By expressing application Requirements

independently from cloud Capabilities and

implementation, TOSCA provides:

Robust set of Normative Types for different domains

(including NFV)

NFV Profile and Types applied to TOSCA enable our

Way Forward.

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 to the TOSCA

Orchestrator)

30

© 2016 TM Forum | 31

TOSCA Model for Containers leveraging Repositories

Hosted

On

PaaS Subsystem (hidden)

PaaS Modeling

• Provider chooses to expose or hide underlying

runtime topology & implementation

Container Application Modeling

• Agnostic of PaaS Cloud Provider

– PaaS on OpenStack, Cloud Foundry, Azure, etc.

Docker Hub(Repository)

Docker image

for mysql

docker_mysql

Container.App.Docker

artifacts:- my_docker_image:

type: Image.DockerURI: mysqlrepository: docker

Requirements

...Runtime.Docker

Container

my_PaaS_platform

Container.Runtime

Capabilities

Runtime.Docker

Container

Runtime.Nodejs

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

Layer

Separation

31

© 2016 TM Forum | 33

Parser Project Overview – Architecture

TOSCA-

>HOT

YANG-

>TOSCA

OpenStack

Upstream

Parser

Repo

Heat-

Translator

Document

Use Case

OPNFV

Doc

33

© 2016 TM Forum | 34

TOSCA Parser and Heat Translator

TOSCA

TypesTOSCA

Template

TOSCA

Nodes

Validation Tests

Map Generate

Validation Tests

tosca-parser heat-translator

HOT - Heat

Orchestration

Template

TOSCA-to-Heat-Translator is part of OpenStack Heat (from Kilo) The tosca-parser is an OpenStack project and licensed under Apache 2. It is developed

to parse TOSCA Simple Profile in YAML. It reads the TOSCA templates and creates an

in-memory graph of TOSCA nodes and their relationship.

Heat-Translator is an Openstack project and licensed under Apache 2. It is a command

line tool which takes non-Heat templates as an input and produces a Heat Orchestration

Template (HOT) which can be deployed by Heat. Currently it supports TOSCA to HOT

translation.

TOSCA-parser & Heat-Translator are available as independent Python library. https://pypi.python.org/pypi/heat-translator ; https://pypi.python.org/pypi/tosca-parser

Heat-Translator available to use in python-openstackclient (OSC) via plugin

Latest TOSCA features integrated: Networking, Block & Object Storage...

34

https://pypi.python.org/pypi/heat-translator

https://pypi.python.org/pypi/tosca-parser

© 2016 TM Forum | 35

YANG-TO-TOSCA

• Provide a mechanism for a VNF provider to describe (VNF descriptor) the

deployment requirements (such as basic VM requirements – vCPU,

memory, storage, as well as advanced HW enhancement requirements

such as Huge Pages support, SR-IOV, NUMA, DPDK support etc.) of a

VNF

• Python based script to convert VNF descriptor from YAML/XML based on

YANG to TOSCA

• VNFD based on the YANG schema defined in ETSI specification

• Enhancements planned to YANG definition for additional NFV requirements

– DPDK, SRIOV, HUGE Page support, CPU Pinning etc.

35

© 2016 TM Forum | 36

Accelerate Delivery with IBM UrbanCode Deploy

• Faster integration (Performance improvement)

• More efficient integration with the new Release plug-in

© 2016 TM Forum | 38

Cloudsoft AMP

© 2015 Cloudsoft

Corporation

15/05/2016 38

> MODEL

Capture

best

practices

Maintain

SLAs

> MANAGE

Dynamic

live model

> DEPLOY > SENSE > EFFECT

>MONITOR

© 2016 TM Forum | 39

Model, Deploy & Manage Any App on Any Cloud

Cloudsoft AMP

Hybrid Cloud Application Management Platform

Portable Model avoids lock-in to today’s tech choices

Supports Agile, IT DevOps model

Policy-based, autonomic management platform

Open-source software & open-standards foundation

© 2016 TM Forum | 40 40

Business Models

Visualization to Provide Context and Understanding

Process Frameworks Large Datasets

DynamicIntuitiveInteractive

..…make better business decisions