Delivering Composable NFV Services for Business, Residential and Mobile Edge OpenStack Summit | Barcelona, Spain

Pere Monclus, CTO @ PLUMgrid Azhar Sayeed, Telco Chief Architect @ Introduction

Pere Monclus CTO, PLUMgrid

Azhar Sayeed Chief Architect, Telco. Red Hat Inc.

2 Agenda

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

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

Physical Virtual Container-based

• Optimized for each function to maximize performance • Standard high volume Hardware • Slow to deploy & update • Independent Software Vendors • Fragmented non-commodity • Open Ecosystem hardware, Vertical Design • Fast on-demand deployment & update • Physical install (per • Variable performance and support for optimization appliance, per site)

4 Realizing Value for Technology Providers Jumpstarting an NFV ecosystem

• Standardized Framework • Proper definition of VNF • Well understood Insertion approaches • Well defined management interfaces VIRTUAL NETWORK FUNCTIONS ECOSYSTEM MANAGEMENT • Scale Out model & ORCHESTRATION • Go to market • Flexible delivery NFVi

• Choose & deploy from portfolio of options SD-COMPUTE SD-NETWORK SD-STORAGE VIM • Shorter testing/deployment/upgrade cycles

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

5 Realizing Value for Operators Carrier Benefits • Service Creation • Introduction and monetization of new services • From concept to production in short timeframes

VIRTUAL NETWORK FUNCTIONS MANAGEMENT • Operational Benefits ECOSYSTEM & • Ease of automation and Increased deployment agility ORCHESTRATION • Scale Out architecture • Visibility with monitoring and alerting NFVi • Reliable (Self-healing, Highly Available, no SPOFs) SD-COMPUTE SD-NETWORK SD-STORAGE VIM

• Cost effective • Multi-tenant • Flexible • Shortened GTM cycle

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

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

vCPE/SDWAN vEPC, vIMS

GiLAN vPE

7 vCPE reference design

Customer Premise Equipment (CPE) Virtualizing the Customer Premise Equipment (vCPE) • Management intensive • Use software implementation on general purpose hardware to • Rigid to changes in operational models provide services to residential and business customers & • performance limited Moore’s law economies of scale • static and immune to demand changes • 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

Residential vCPE Enterprise vCPE Internet Residential VM VM

NFVO SDN Controller VNFM(s) Software Defined Central Office VIM NFVI - POP Enterprise

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

10 Agenda

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

11 Let’s size it.

12 Sizing the reference design Residential vCPE Infrastructure Sizing: Number of Servers

Households vCPE Adoption Servers Needed

10% vCPE penetration 2 VM per CPE 2.1 M Servers 100 VMs / server Residential Households: 30% vCPE penetration 6.3 M Servers 2 VM per CPE • China: 455.9 Million 100 VMs / server • India: 248.4 Million • Europe: 218.9 Million • USA: 133.9 Million 50% vCPE penetration 10.5 M Servers 2 VM per CPE 100 VMs / server

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

13 Sizing the reference design Residential vCPE Infrastructure Sizing: Bandwidth

vCPE Adoption / Households BW per Server Speed

10% vCPE penetration 500Mbps / Server 10 Mbps / CPE ( 2.1M Servers) Residential Households: 5Gbps / Server 30% vCPE penetration (6.3M Servers) • China: 455.9 Million 100 Mbps / CPE • India: 248.4 Million • Europe: 218.9 Million • USA: 133.9 Million 50Gbps / Server 50% vCPE penetration (10.5M Servers) 1 Gbps / CPE

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

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

3 to 10 Million Servers? 2 to 10 Million Servers? Cloud NFV Industry Industry

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

15 Really??? Agenda

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

17 We need more… Branch Apps Wireless LAN Controller Business vCPE + Other Branch site software FW DHCP Compute node(s) running the following functionality at the branch ● vRouter with the following services Branch Current Router Branch ● WAN connectivity with IPSec DNS, LDAP ● Firewall PBX ● Intrusion Protection ● DHCP services ● WAN optimization ● Branch Compute ● DNS ● AD/LDAP agents ● Physical Security applications – Video Monitoring, Security sensors etc Converged Branch ● PBX Virtualized Environment with ● Wireless LAN Controller vCPE with vRouter+ Compute, Storage and Apps

FW, DHCP, WLAN Controller 18 Service Function Chaining Models Service Insertion / Service Function Chaining

Virtual Domain Virtual Domain Policy Policy Edge Policy Distributed Distributed Enforcement Point

Service Chain

Topology Based Service Insertion Policy Based Service Insertion

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

Security Services Managed/Business Services ● vFW - Firewall IPAM - IP Address Management ● vALF - Application Level Firewall ● vDNS - ● vIPS - Intrusion Protection ● vDHCP WAN Access Services ● vNAT ● WAN Optimization Data Services ● SDWAN ● vLB - Load Balancer Virtual VPN concentrator ● vDPI - Deep Packet Inspection Residential Services Virtual Content Cache Node ● vRouting ● Video Cache ● vEmail Scrubber ● Video Optimization ● vIDS - Intrusion Detection - Perimeter Services ● vQuota Management ● vPersonal Firewall

20 Redrawing vCPE design

Sub AAA Configuration Policy

vIPS/ QoS Traffic-O Malware

DC Switch VM NAT VxLAN VM vRouter L2 NID HFC/GPON vFW

VM VM NAT VxLAN Ethernet Quota Parental VxLAN vFW Management Control

vLB Demarc Point

nCPE uCPE VM VM VM Internet

App or Content Cache

21 Let’s size it.

22 Sizing the reference design Residential vCPE Infrastructure Sizing: Number of Servers

Households vCPE Adoption Servers Needed

10% vCPE penetration 6 VM per CPE 6.3 M Servers 100 VMs / server Residential Households: 30% vCPE penetration 6 VM per CPE 13.2 M Servers • China: 455.9 Million 100 VMs / server • India: 248.4 Million • Europe: 218.9 Million • USA: 133.9 Million 50% vCPE penetration 31.5 M Servers 6 VM per CPE 100 VMs / server

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

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

3 to 10 Million Servers? Cloud Industry 6 to 30 Million Servers? NFV Industry

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

24 Really??? Agenda

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

26 Back to the drawing board…

This time with the ruler!!

27 Exploring Solutions We need to look for efficiencies in multiple dimensions

Bandwitdh Architectural Density

FD.IO/VPP Thin/Thick CPE Containers

XDP/IOVisor Tethered CPE Serverless Computing DPDK/OVS Policy based Networking Multi tenant Smart NICs VNFs New VNF Service based models SR-IOV Networking (distributed Data Path)

Needed Goals: 40-100Gbps / server Simplify operations, visibility 100x to 1000x density and management. improvement Extensibility/new services.

28 About Bandwidth

Bandwitdh Things to consider:

• Raw PPS/BW FD.IO/VPP • Current feature set / Future feature set • Programmability & Ecosystem of developers XDP/IOVisor • Solution for VM, Containers or VM & Containers DPDK/OVS • Beyond Networking: Security/Policy at all dimensions of infrastructure Smart NICs • Part of Kernel / External to Linux Kernel • Isolation of environments SR-IOV • HW assist

40-100Gbps / server

29 About Architecture

Architectural Things to consider:

• Thin/Thick CPE transition steps • Alternative models? Tethered CPE or uCPE Thin/Thick CPE

• Do we need to change our thinking towards Tethered CPE networking (from topology to policy/services)?

Policy based Networking

Service based Networking

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

30 About Density

Density Things to consider:

• HW to VNF VM as first transition (1-1) Containers • Complex Multitenant VMs to Single Tenant VMs (1-N) • VM to Containers next logical transition (1-1) Serverless Computing • What about other models? Equivalent to AWS Lambda for networking? (N-0) Multi tenant • Control Plane – Data Plane Separation (N-1) VNFs • Vendor Ecosystem and Marketplace around the different New VNF technologies models (distributed Data Path)

100x to 1000x density improvement

31 Red Hat and PLUMgrid Solutions

API, Or-Vnfm, VNFD Specific VNFm ManageIQ/Cloudforms (e.g. Tacker) Or-Vi HOT, API Vi-Vnfm, HOT

REST API RHOSP & Tower Openstack

Vi-Vnfm

REST Nf-Vi PLUMgrid Open Networking Suite

Service Tenant Nf-Vi Overlay VNF Chain Networks

IOVisor VM and Virtual Infra (RHEL)

32 Conclusions

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

33 THANK YOU! Visit Us @Booth B37 & D1