OPNFV: Open Source Software to Enable NFV

Ashiq Khan, PhD

DOCOMO R&D TSC Member NTT DOCOMO, INC. Open Platform for NFV

CLOUDOPEN Japan June 3, 2015

 Telco virtualization and NFV

 Why open source

 Open Platform for NFV

Massive number of call attempts (roughly 60-fold increase) were made. Call restriction control were in place.

Earthquake 14:46 Mar.11 Call Restriction Call Restriction

15:00, Mar. 11 – 2:00, Mar. 12 6:00, Mar.12 – 1:00, Mar. 13

12.6-fold The number of call attempts were increased roughly 60-fold in outgoing and 40-fold in incoming.

The number of calls out in 7.9-fold out in After the A week disaster ago

Friday, Mar.11 Saturday, Mar.12 source: http://www.soumu.go.jp/menu_news/s-news/01kiban02_02000043.html Deploying resources to process such load is practically impossible © 2015, NTT DOCOMO. INC. All Rights Reserved. 3 Enter virtualization

 We need a mean to do resource sharing

Normal At disaster More on highly demanded More on voice calls etc. to Internet access (Rich media confirm safety of relatives Contents) than voice calls and friends

Voice

Mail

Rich Media (Video etc.)

This is a joint research work supported by "Experimental challenges for dynamic virtualized networking resource control over an evolved mobile core network - a new approach to reduce massive traffic congestion after a devastating disaster" of the Ministry of Internal Affairs and Communications, Japan.

 Resource sharing among services Virtualized Facilities Standard Facilities Tohoku University Yokosuka Center Tohoku

IMS EPC Video Site B Site A Server

IMS EPC EPC EPC IMS EPC EPC EPC Mail VM VM VM VM VMVM VMVM VMVM VMVM 96 Blade Servers 96 Blade Servers Legacy HW Legacy HW Server 8 OpenFlow 8 OpenFlow Switches L2/L3 Networks Switches Access Access 5 OpenFlow Access 5 OpenFlow Switches Switches JGN-X L2/L3 Networks Load Generator (Terminals) Load Generator (Terminals)

Site C Site D Access Access 4 OpenFlow 4 OpenFlow Switches Switches IMS: IP Multi-media Subsystem, EPC: Evolved Packet Core This is a joint research work supported by "Experimental challenges for dynamic virtualized networking resource control over an evolved mobile core network - a new approach to reduce massive traffic congestion after a devastating disaster“ and “Research and development of network conversion of communication processing functions in large-scale communication congestion” of the Ministry of Internal Affairs and Communications, Japan.

 Virtualization can enable us to do resource sharing Call completion rate Call completion rate Estimated peak demand during the disaster 5% 25%

Voice Voice 5% accepted 112.5K <50-fold increase> （2.25M/h） 25% accepted E-mail 25% accepted 135K

（0.54M/h） Reallocation 562.5K

Packet <4-fold increase> Rich Media 25% accepted （） 2.34M/h 25% accepted 585K 135K

6% accepted 135K

This is a joint research work supported by "Experimental Normal After reallocation challenges for dynamic virtualized networking resource （） control over an evolved mobile core network - a new （Total Capacity: 832.5K） Total Capacity: 832.5K approach to reduce massive traffic congestion after a devastating disaster" of the Ministry of Internal Affairs and Communications, Japan.

 Feasibility of resource sharing over geographically dispersed area Before sharing After sharing Congested region

Voice: Voice: 170000 300000 Packet: Packet: 450000 840000 Sendai 400 km

DOCOMO R&D virtual Inter-site network Distant site e reallocat

This is a joint research work supported by “Research and development of network conversion of communication processing functions in large-scale communication congestion” of the Ministry of Internal Affairs and Communications, Japan. Virtualization can give a good amount of resource flexibility to mobile telecom operators

https://www.nttdocomo.co.jp/english/info/media_center/pr/2015/0302_00.html

 Its different than everything you see in the clouds now …

External networks

SGW deployment PGW

PGW SGW MME SGW Size: 377944 sq. km Population: 126 mil Penetration rate: 112%

eNB eNB

Each EPC node supports few hundred thousands subscribers

 Standardization won’t be completed before deployment – Risk of ‘standalone’ specification  Lack of commercial virtualization-based solution – gaps exist between standards and what is available  Don’t have a reference platform – Can’t compare if an offered platform is good enough

We need a way for fast implementation, start with what is common to everyone. We have heard that ‘opensource’ is pretty fast ….

 Open Platform for NFV started in Oct. 2014

requirements

Network Functions Virtualisation (NFV) Open Platform for NFV Industry Specification Group (ISG) A Linux Foundation Collaborative Project

 Use cases and requirements  Reference implementation  Architecture  Interoperability tests  High-level specifications  Validating specifications

What we want and the We quickly know what interoperability requirements is missing, what is right

solutions

 De-facto implementation – Opensource projects can provide fast solutions becoming de-facto/standards later

 Validity and compliance – detects issues in standards through implementation, provide common codebase to test compliance to the standards

 Reduce development burden – vendors can build on existing code base rather than creating it from scratch

Os-Ma NFV OSS/BSS Orchestrator

Or-Vnfm

EM 1 EM 2 EM 3 Ve-Vnfm Service, VNF and VNF Infrastructure Manager(s) Description VNF 1 virtualizedVNF telecom 2 nodes VNF 3

Vn-Nf Vi-Vnfm NFVI Virtual Virtual Virtual OpenDaylight Computing Storage Network Nf-Vi VirtualisedCloud Or-Vi VirtualisationHypervisor Layer Management InfrastructureSystem Vl-Ha Manager(s)(OpenStack) Hardware resources Computing Storage Network Hardware Hardware Hardware

Execution reference points Other reference points Main NFV reference points See https://www.opnfv.org/developers/technical-project-governance/tsc-policy

 A reference implementation of the platform (NFVI+VIM)

 Filling out the gaps in between standards and what’s available

 A Linux Foundation collaborative project

Platinum Platinum Strategic End Silver Silver (continued) Silver Strategic End Users Users Brocade AT&T 6WIND Dialogic CableLabs Cisco China Mobile ADVA Dorado Software CenturyLink Dell DOCOMO Alcatel-Lucent ENEA Software KT EMC Telecom Italia Altera H3C Ooredoo Ericsson Vodafone ARM Ixia Orange HP Array Networks Metaswitch SK Telecom Huawei Brain4Net Midokura Sprint IBM Broadcom Mirantis Intel Canonical Overture Networks Juniper Cavium Networks Qosmos NEC Ciena Sandvine Nokia Citrix Sonus Networks Red Hat ClearPath Networks Spirent ZTE ConteXtream Stratus Coriant VMWare Cyan Wind River Xilinx

as of May 2015 A strong presence of Operators/Service providers. What do they do in an Opensource community???

 Target is to reach upstream

Upstream communities ………

Requirements Project Collaborative Development Project Testing & Integration Project Documentation Project

OPNFV accommodates a variety of telecom and IT industry players

 DOCTOR: requirement project on fault management – Don’t hide everything

Node manager/VNFM

switch over  Hardware is not completely decoupled from software VM VM  telco-nodes have five 9s ACT node SBY node availability requirement  Don’t take unilateral recovery action Hypervisor Hypervisor Hypervisor  OpenStack inform the manager first Hardware Hardware Hardware X detect

see https://wiki.opnfv.org/doctor

Three blueprints accepted in the last OpenStack summit on Liberty release

 Promise: requirement project on resource reservation – Reservation feature not available in OpenStack

Promise plug-in

OpenStack

see https://wiki.opnfv.org/promise

6 contributions were made to ETSI NFV. Prototyping underway.

 Pharos: building global federated testbed

Source: Pharos project, OPNFV 11 testbeds (8 operational, 3 planned) see https://wiki.opnfv.org/pharos

Sufficient amount of resources for large scale testing and verification

 A diverse range of projects, proof of speedy, open innovation

Policy enforcement Build, Integration and Deployment Application Deployment and Testing New Requirements & Features

Foreman FuncTest Prediction IPv6 support for OPNFV platform

Fuel Qtip Copper MOVIE IPv6

OSCAR DPACC Doctor Fastpath

JOID VSPERF Availability Escalator SFC

Resource Conductor Parser VNFFG Scheduler

ONOS Yardstick Promise Multisite Moon FW

Inspector High Availability of Multi-site Open ONOS OPNFV Platform Stack support integration visit https://wiki.opnfv.org

 Telco nodes need ‘some’ attention in virtualization.  reliability, high availability required, but not from the hardware per-say.

 Opensource can play a significant role in NFV-based telco network deployment and the consequent operation.  complementing the lack of commercial solutions.

 OPNFV is a fast-growing opensource community driving speedy development of a reference NFV platform.  heavy presence of telco players. Seeing success already.

 Early engagement from Operators/service providers in opensource development saves lots of rework later.  collect end-customers view ASAP.

 Follow standards. Standard is necessary in communication.  opensource can accelerate the adoption of telecom standards.

2015