OpenStack Summit | Barcelona, Spain

Delivering Composable NFV Services for Business, Residential and Mobile Edge

Pere Monclus, CTO @ PLUMgrid Azhar Sayeed, Telco Chief Architect @ Red Hat

Introduction

2

CTO, PLUMgrid Monclus Pere

Chief Architect, Telco. Red Hat Inc. Sayeed Azhar

• NFV, What, Why, How? • What is the Problem? • Composable NFV Services • Help! Ideas • Summary

Agenda

3

NFV, what, why, how? Virtual Network Functions Evolution

4

•  Optimized for each function to maximize performance

•  Slow to deploy & update •  Fragmented non-commodity

hardware, Vertical Design •  Physical install (per

appliance, per site)

Physical

•  Standard high volume Hardware •  Independent Software Vendors •  Open Ecosystem •  Fast on-demand deployment & update •  Variable performance and support for optimization

Virtual Container-based

Realizing Value for Technology Providers Jumpstarting an NFV ecosystem

5

MANAGEMENT&

ORCHESTRATION

VIM

NFViSD-COMPUTE SD-NETWORK SD-STORAGE

VIRTUAL NETWORK FUNCTIONS ECOSYSTEM

•  Standardized Framework •  Proper definition of VNF •  Well understood Insertion approaches •  Well defined management interfaces •  Scale Out model

•  Go to market •  Flexible delivery •  Choose & deploy from portfolio of options •  Shorter testing/deployment/upgrade

cycles

Towards a “Market place” of VNFs for the new wave of SW Network Technology Providers

Realizing Value for Operators Carrier Benefits

6

•  Service Creation •  Introduction and monetization of new services •  From concept to production in short timeframes

•  Operational Benefits

•  Ease of automation and Increased deployment agility •  Scale Out architecture •  Visibility with monitoring and alerting •  Reliable (Self-healing, Highly Available, no SPOFs)

•  Cost effective

•  Multi-tenant •  Flexible •  Shortened GTM cycle

MANAGEMENT&

ORCHESTRATION

VIM

NFVi

SD-COMPUTE SD-NETWORK SD-STORAGE

VIRTUAL NETWORK FUNCTIONS ECOSYSTEM

Provide customers a richer set of services. Enable a “Marketplace”

NFV most common use cases Flexibility and openness enables innovation in many markets

vCPE/SDWAN

vPE

vEPC, vIMS

GiLAN

7

vCPE reference design

Customer Premise Equipment (CPE) •  Management intensive •  Rigid to changes in operational models •  performance limited •  static and immune to demand changes

Virtualizing the Customer Premise Equipment (vCPE) •  Use software implementation on general purpose hardware to

provide services to residential and business customers & Moore’s law economies of scale

•  Low overhead - centralized control and management - No truck roll

•  Performance can scale with the cloud •  Dynamic and flexible with ability to add and drop services

easily

Internet

NFV Cloud 8

vCPE reference design Thin / Thick vCPE Model

9

Enterprise

Software Defined Central Office NFVI - POP

Internet

Residential vCPE Enterprise vCPE

NFVO SDN Controller VNFM(s) VIM

Residential VM VM

Life is good vCPE and NFV as the answer to many problems

10

• NFV, What, Why, How? • What is the Problem? • Composable NFV Services • Help! Ideas • Summary

Agenda

11

12

Let’s size it.

Sizing the reference design

https://en.wikipedia.org/wiki/List_of_countries_by_number_of_households

Residential vCPE Infrastructure Sizing: Number of Servers

Residential Households:

•  China: 455.9 Million •  India: 248.4 Million •  Europe: 218.9 Million •  USA: 133.9 Million

10% vCPE penetration 2 VM per CPE

100 VMs / server

30% vCPE penetration 2 VM per CPE

100 VMs / server

50% vCPE penetration 2 VM per CPE

100 VMs / server

2.1 M Servers

6.3 M Servers

10.5 M Servers

Households vCPE Adoption Servers Needed

13

Sizing the reference design

https://en.wikipedia.org/wiki/List_of_countries_by_number_of_households

Residential vCPE Infrastructure Sizing: Bandwidth

Residential Households:

•  China: 455.9 Million •  India: 248.4 Million •  Europe: 218.9 Million •  USA: 133.9 Million

10% vCPE penetration 10 Mbps / CPE

30% vCPE penetration 100 Mbps / CPE

50% vCPE penetration 1 Gbps / CPE

500Mbps / Server ( 2.1M Servers)

5Gbps / Server (6.3M Servers)

50Gbps / Server (10.5M Servers)

Households vCPE Adoption / Speed BW per Server

14

How big is the pie? In terms of number of servers

15

10M servers at USD 5,000 per server = USD 50B investment…

NFV Industry

Cloud Industry

2 to 10 Million Servers? 3 to 10 Million Servers?

Really???

• NFV, What, Why, How? • What is the Problem? • Composable NFV Services • Help! Ideas • Summary

Agenda

17

We need more…

18

Business vCPE + Other Branch site software

Compute node(s) running the following functionality at the branch ●  vRouter with the following services

●  WAN connectivity with IPSec ●  Firewall ●  Intrusion Protection ●  DHCP services ●  WAN optimization

●  Branch Compute ●  DNS ●  AD/LDAP agents ●  Physical Security applications – Video Monitoring,

Security sensors etc ●  PBX ●  Wireless LAN Controller

PBX

BranchRouter

DNS,LDAP

BranchAppsWirelessLANController

FW

Converged Branch Virtualized Environment with vCPE with vRouter+ Compute, Storage and Apps FW, DHCP, WLAN Controller

CurrentBranch

DHCP

Service Function Chaining Models Service Insertion / Service Function Chaining

19

Topology Based Service Insertion

Virtual Domain

Dis

tribu

ted

Pol

icy

Edge Policy Enforcement Point

Policy Based Service Insertion

Virtual Domain

Dis

tribu

ted

Pol

icy

Service Chain

We need more … Composable NFV Services More means… many more!!!

Security Services ●  vFW - Firewall ●  vALF - Application Level Firewall ●  vIPS - Intrusion Protection

WAN Access Services ●  WAN Optimization ●  SDWAN

Virtual VPN concentrator Residential Services

●  vRouting ●  vEmail Scrubber ●  vIDS - Intrusion Detection - Perimeter Services ●  vQuota Management ●  vPersonal Firewall

Managed/Business Services IPAM - IP Address Management

●  vDNS - ●  vDHCP ●  vNAT

Data Services ●  vLB - Load Balancer ●  vDPI - Deep Packet Inspection

Virtual Content Cache Node ●  Video Cache ●  Video Optimization

20

Redrawing vCPE design

Internet

HFC/GPON

Demarc Point

L2 NID

Ethernet

VM DC Switch

vFW

vFW

Traffic-O

vRouter

QoS

VxLAN

VxLAN

VxLAN

Sub Configuration Policy AAA

VM NAT VM

Quota Management

Parental Control

VM NAT

vIPS/ Malware

vLB

VM

VM

VM

App or Content Cache

uCPE nCPE

21

22

Let’s size it.

Sizing the reference design

https://en.wikipedia.org/wiki/List_of_countries_by_number_of_households

Residential vCPE Infrastructure Sizing: Number of Servers

Residential Households:

•  China: 455.9 Million •  India: 248.4 Million •  Europe: 218.9 Million •  USA: 133.9 Million

10% vCPE penetration 6 VM per CPE

100 VMs / server

30% vCPE penetration 6 VM per CPE

100 VMs / server

50% vCPE penetration 6 VM per CPE

100 VMs / server

6.3 M Servers

13.2 M Servers

31.5 M Servers

Households vCPE Adoption Servers Needed

23

How big is the pie? In terms of number of servers

24

NFV Industry

6 to 30 Million Servers?

Cloud Industry

3 to 10 Million Servers?

30M servers at USD 5,000 per server = USD 150B investment… !!!

Really???

• NFV, What, Why, How? • What is the Problem? • Composable NFV Services • Help! Ideas • Summary

Agenda

26

27

Back to the drawing board…

This time with the ruler!!

Exploring Solutions We need to look for efficiencies in multiple dimensions

Density Bandwitdh Architectural

FD.IO/VPP

XDP/IOVisor

DPDK/OVS

Smart NICs

SR-IOV

Multi tenant VNFs

Containers

Serverless Computing

New VNF models

(distributed Data Path)

Thin/Thick CPE

Policy based Networking

Service based Networking

Tethered CPE

Needed Goals: 40-100Gbps / server 100x to 1000x density improvement

Simplify operations, visibility and management. Extensibility/new services.

28

About Bandwidth

29

Bandwitdh

FD.IO/VPP

XDP/IOVisor

DPDK/OVS

Smart NICs

SR-IOV

40-100Gbps / server

Things to consider: •  Raw PPS/BW •  Current feature set / Future feature set •  Programmability & Ecosystem of developers •  Solution for VM, Containers or VM & Containers •  Beyond Networking: Security/Policy at all dimensions of

infrastructure •  Part of Linux Kernel / External to Linux Kernel •  Isolation of environments •  HW assist

About Architecture

30

Architectural

Thin/Thick CPE

Policy based Networking

Service based Networking

Tethered CPE

Simplify operations, visibility and management. Extensibility/new services.

Things to consider: •  Thin/Thick CPE transition steps •  Alternative models? Tethered CPE or uCPE •  Do we need to change our thinking towards

networking (from topology to policy/services)?

About Density

31

Things to consider: •  HW to VNF VM as first transition (1-1) •  Complex Multitenant VMs to Single Tenant VMs (1-N) •  VM to Containers next logical transition (1-1)

•  What about other models? Equivalent to AWS Lambda for networking? (N-0)

•  Control Plane – Data Plane Separation (N-1) •  Vendor Ecosystem and Marketplace around the different

technologies

Density

Multi tenant VNFs

Containers

Serverless Computing

New VNF models

(distributed Data Path)

100x to 1000x density improvement

Red Hat and PLUMgrid Solutions

Overlay ServiceChain VNF

PLUMgrid Open Networking Suite

SpecificVNFm(e.g.Tacker)ManageIQ/Cloudforms

RHOSP

Openstack

VMandVirtualInfra(RHEL)

TenantNetworks

Or-Vi HOT, API

Ansible&Tower

API, Or-Vnfm, VNFD

Vi-Vnfm

Vi-Vnfm, HOT

Nf-Vi

REST API

REST Nf-Vi

IOVisor

32

•  NFV market is happening, 5G as a potential main driver in the coming years

•  Still some unresolved problems around the overall solution, but well understood and with active development on those areas

•  No ‘universal solution’ that fits all the NFV use cases yet. But specific solutions for certain use cases already in Production

•  VNF vendors slow to play nice with the NFV ecosystem / marketplace. Need for new generation of start ups that will deliver VNFs in new form factors

•  Try it!

Conclusions

33

Visit Us @Booth B37 & D1

THANK YOU!