How Cloud Native VNFsDeployed On OpenStackWill Change The Telecom Industry

Arthur Berezin

Dir. Product Management, Cloudify

[arthur@cloudify] # whoami

▪ Active OpenStacker Since Essex (2012)

▪ Dir. of Product Management, Cloudify

▪ Apache ARIA-TOSCA Project Lead

▪ Project Open-O TSC > now ONAP

Introducing Cloudify

■ Pure-Play MANO based on TOSCA○ Technology agnostic○ Fits into any architecture

■ Full automation of service lifecycle

■ No vendor lock-in, enabling best of breed approach

Leveraging web-scale best practices to orchestrate network services in Telco environments

• NFV 1.0 Transformation

• NFV 2.0 Cloud Native

• OpenStack’s Role

Service Provider Traditional Networks

• Physical Appliance

• Vendor Driven

• 18+ months of on-boarding

• Static

• Costly

Physical to Virtual[Network Function Virtualization]

• Commodity Hardware

• Commodity or custom Operating system

• Minimal Software Change

Physical to Virtual[Network Function Virtualization]

• VM Appliance

• Virtualization Packaging

• Hours/Days to Deploy

• Same Management

• High HW Consumption

http://www.lightreading.com/nfv/nfv-mano/telcos-clamoring-for-cloud-native-vnfs/a/d-id/724093

Cloud Native Disruption

• Fully automatic

• Hardware Efficiency

• Commodity Costs

Cloud Native Disruption

● Hyper Scalable

● Architected to Expect Failure

● Operations Driven On-boarding

● Underlay and Overlay Networks

● Cloud Native Pricing Model

Cloud Native VNFs - Versa

Self Managed

Cloud Native VNFs - Ruckus Wireless

SaaS Managed

A Blueprint of Cloud Native VNF

Cloud Native VNF

● Software Defined

● Application, Management and Provisioning

● Design for DevOps

● Configuration as code

● Built-in automation of the provisioning and configuration

● Continuous deployment

● Monitoring

● Avoid proprietary monitoring

● Use best of breed open-source monitoring framework

● Containers

Cloud Native VNF

● Multi Tenancy

○ Share the same VNF between multiple users

○ Have separate VNF per (IaaS) tenant

● Multi Cloud (VIM) Support

○ Operators have different cloud flavour and preferences

○ Be ready to support the common platform to maximize your

market reach

The Cloud Native Journey with OpenStack

● De Facto standard VIM● Highly customizable Private Cloud

● Making OpenStack Cloud Native

● Rich Ecosystem of Vendors and Plugins

● Overlay and Underlay Integration

● Expand the native capabilities

Leverage OpenStack

Use OpenStack’s Native Services for Cloud Native VNFs

Neutron

Designate FWaaS

Magnum Kuryr Kolla

Virtrage

LBaaS

VNF Orchestration and Management

Provision

ConfigureMonitor

Manage

Orchestration Engine

VNFs Hybrid Cloud/Stack

Self-healing Auto-scaling Monitoring

Policy ManagementSecurity and Multi-Tenancy

Cloud Native High Performance Stack

Provision

ConfigureMonitor

Manage

Orchestration Engine

VNFs High Performance Stack

Self-healing Auto-scaling Monitoring

Policy ManagementSecurity and Multi-Tenancy

Bare Metal Cloud

Intel EPA

Enabled

Canonical Clear Containers

Embeddable Orchestration

Operator Service Orchestrator

Multi-Tenancy

Management

Service

Composition

Lifecycle

Management

Consistent

Infrastructure

/Tenant

ManagementVirtual Appliance

Physical Appliance

Micro Services

Cloud Native VNF

Embedded Orchestrator

Open Source Embeddable Orchestration

● OEMable

● White Labeling

● Lightweight

● Open Source

● Open Governance

● Extensible/Customizable

● Portable Between OSes & Clouds

Open Source Embeddable Orchestration

● TOSCA Deployment Orchestration ● Development Framework ● Lightweight● Support for major platforms:

○ OpenStack, VMWare, Kubernetes,Docker Swarm

● Full Lifecycle Management ● Uses ARIA as Orchestration Engine● Advanced Management:

○ Self-Healing, Self-Scaling○ Policy Management ○ Monitoring○ Multi-Tenancy○ Portal○ Security

Standardization Efforts

Standards Open Source

Model Driven Cloud Native Orchestration

Multi Cloud Infrastructure Orchestration● Automation of compute, storage, network

● Auto scale, Heal

● Consistent management and monitoring

Non

Containerised

Model Driven (TOSCA) Service Orchestration Orchestration of services across platform domains.

Modeling is done Independentof the Container platform. (“Where”) and Independent of how the service is Orchestrated. (“How”)

Infrastructure Portability

Provision containers platform

across clouds and manage their

resource availability and

capacity

Service

Orchestration

Infrastructure

Orchestration

Container

Platforms

Hybrid Containerized Cloud Native

https://github.com/dfilppi/posts/wiki/Hybrid-CME-Post

Are You Ready To Be Cloud Native?

● Can you package your VNF as an Image/Container?

● Can your VNF be driven by API or external script?

● Can you boot/configure your VNF using Cloud-Init

● Does the setup of your VNF assume manual operations during setup process?

The only constant is change

Where Do I Go From Here?

_Academy_

FREE NFV Labs ON DemandVia Cloudify Academy

Thank You

www.CLOUDIFY.co