NFV Unbound from physical boxes to virtual, open infrastructures - - PowerPoint PPT Presentation

1

NFV Unbound

from physical boxes to virtual, open infrastructures

Christos Kolias

• Sr. Research Scientist

Network Architecture, Orange Silicon Valley

christos.kolias@orange.com

Open Daylight Summit February 4-5, 2014 – Santa Clara, CA

2

ETSI NFV

Agenda

• NFV: A Year Later
• Use Cases & PoCs
• Open NFV
• NFV+SDN
• Orange NFV PoCs
• Future of …

3

NFV: implementing network functions in software - that (today) run on proprietary hardware - leveraging (high volume) commodity servers and IT virtualization ETSI NFV ISG: a group for producing NFV specifications and a reference framework - not a standardization body

ETSI NFV

4

ETSI NFV

BRAS Firewall DPI CDN Tester/QoE monitor WAN Acceleration Message Router

Radio/Fixed Access Network Nodes

Carrier Grade NAT PE Router

SGSN/GGSN

The NFV Concept & Vision

Classical Network Model: Hardware Appliances

• Network Functions are based on specialized hardware
• One physical node per role. Physical install per site
• Static. Hard to scale up & out

Session Border Controller

standard servers, storage, switches The New Network Model: Virtual Appliances

Orchestration & Automation

• Network Functions are SW-based
• Multiple roles over same HW. Remote operation
• Dynamic. Extremely easy to scale

5

ETSI NFV

A Potted History of NFV

• Network operators had independently discovered that NFV

technology now has sufficient performance for real-world network work loads

• Informal discussions on cooperation to encourage industry

progress began at ONS in Santa Clara in April 2012

• At an operator meeting in Paris in June 2012 we coined the new

term “Network Functions Virtualisation (NFV)”.

• We decided to convene a new industry forum, and publish a joint

white paper to galvanise the industry

• At a meeting in San Francisco in September 2012 we decided to

parent the new forum under ETSI

• In October 2012 we published the first joint-operator NFV white

paper as a “call to action”.

• This paper is widely regarded as the seminal paper

heralding this new approach for networks.

• The first NFV ISG plenary session was held in January 2013
• In October 2013 the first NFV ISG documents were released

after only 10 months, and a second joint-carrier NFV white paper published to provide our perspectives on progress.

13 signatories to first NFV white paper

6

ETSI NFV

Fields of Application (examples)

• Mobile networks:
• HLR/HSS, MME, SGSN, GGSN/PDN-

GW, eNodeB, vEPC

• NGN signalling:
• SBCs, IMS
• Switching elements:
• BNG, CG-NAT, routers
• Home environment:
• home router, set top box, picocell
• Application-level
• ptimization:
• CDNs, Cache Servers, Load Balancers,

Application Accelerators

• Security functions
• Firewalls, virus scanners, intrusion

detection systems, spam protection

• Tunnelling gateway

elements:

• IPSec/SSL VPN gateways
• Converged and network-

wide functions:

• AAA servers, policy control and charging

platforms

• Traffic analysis/forensics:
• DPI, QoE measurement
• Traffic Monitoring:
• Service Assurance, SLA monitoring, Test

and Diagnostics

7

ETSI NFV Group

• Global operators-initiated Industry Specification Group (ISG) under the

auspices of ETSI

‒ >170 companies ‒ 28 Tier-1 carriers (and mobile operators) & service providers, cable industry

• Open membership

‒ ETSI members sign the “Member Agreement” ‒ Non-ETSI members sign the “Participant Agreement”

• Operates by consensus (formal voting only when required)
• Deliverables: requirements specifications, architectural framework, PoCs,

standards liaisons

• Face-to-face meetings quarterly. Currently four (4) WGs, two (2) expert

groups (EGs), 4 root-level work items (WIs)

‒

WG1: Infrastructure Architecture

‒

WG2: Management and Orchestration

‒

WG3: Software Architecture

‒

WG4: Reliability & Availability

• Network Operators Council (NOC): technical advisory body
• Technical Steering Committee (TSC): WG Chairs + EG Leaders, TMs, PMs,

Rapporteurs

‒ EG1: Security ‒ EG2: Performance &

Portability, PoCs

ETSI NFV

8

ETSI NFV

Support from ETSI Secretariat

ISG Chair ISG V. Chair ISG Plenary

(Chaired by ISG Chair)

Network Operators Council

(Chaired by NOC Chair)

Technical Management

(TM and ATM)

Technical Steering Committee

(Chaired by Technical Manager) WG WG WG

Expert Group

. . . ETSI NVF Organization & Structure

9

Architectural Groups

• Related to functional requirements
• Have a clear location in the NFV architecture

‒ Keep consistency with both requirements and architecture

• INF

‒ The supporting infrastructure interfaces and elements

• MANO

‒ The external interfaces and behaviour of a VNF

• SWA

‒ The internals of a VNF

• Refining the architecture
• Addressing use cases
• Mostly oriented to produce reference documents

ETSI NFV

10

Transversal Groups

• Related to non-functional requirements
• Transversal to the architecture

‒ Influencing work in the architectural groups

• REL

‒ Specify resiliency requirements, mechanisms , and architectures

• PER

‒ Predictability in the data plane and function portability

• SEC

‒ Function by function and infrastructure

• Refining the requirements
• Assessing use cases
• Mostly concerned with recommendations and architecture models

ETSI NFV

11

ETSI NFV

ETSI NFV’s objectives

• Provide a common requirements and architectural framework

 Four specification documents ratified and published (Oct. ‘13)

• Architecture Framework, Use Cases, Requirements, Terminology

www.etsi.org/nfv

• Identify overall technical challenges and scope, e.g.:

‒ Achieving high performance with portability between different hardware vendors (and

hypervisors)

‒ Specify interfaces between functional blocks ‒ Achieving co-existence with bespoke hardware based network platforms whilst

enabling an efficient migration path to fully virtualised network platforms

‒ Managing and orchestrating many virtual network appliances while ensuring security

from attack and misconfiguration

‒ Achieving scale through automation ‒ Integrating multiple virtual appliances from different vendors (“mix & match”) without

incurring significant integration costs, and while avoiding lock-in

12

ETSI NFV

• Templates/patterns/config-schemes for instantiating the VNFs

‒ They could be network/operator specific ‒ Compile VNFs

• Encourage common approaches to solving these technical challenges

in an open ecosystem

• The NFV ISG provides a forum for the industry & operators to

collaborate, to converge requirements, agree common approaches, and to validate recommendations

• Develop and exhibit Proof-of-Concepts (PoCs). Benchmarking
• Perform a Gap Analysis

‒ Map WG tasks to relevant externals bodies

ETSI NFV

13

External Relationships

• Public documents, www.etsi.org/nfv
• Early access to stable drafts
• Participation in joint events
• Coordinated individual contributions
• Most relevant SDOs
• Open Source

projects

• Identifying concrete

areas of cooperation

• Need to avoid

fragmentation

ONF

MoU

14

• Network Functions

Virtualisation Infrastructure as a Service (NVFIaaS)

‒ Network functions go to the

cloud

• Virtual Network Function as a

Service (VNFaaS)

‒ Ubiquitous, delocalized

network functions

• Virtual Network Platform as a

Service (VNPaaS)

‒ Applying multi-tenancy at the

VNF level

• VNF Forwarding Graphs

‒ Building E2E services by

composition

An E2E View: Architectural Use Cases

NVFIaaS Example

ETSI NFV

15

ETSI NFV

XaaS for Network Services

NFVI Provider

IaaS NaaS NaaS SaaS

NFVIaaS Hosting Service Provider

VNF VNF VNF VNF VNF VNF VNF VNF VNF

VNF Tenants NSP VNF VNF VNF VNF VNF VNF Forwarding Graph Admin User Admin User VNFaaS User

PaaS PaaS

VNPaaS

16

• Mobile core network and IMS

‒ Elastic, scalable, more resilient EPC ‒ Specially suitable for a phased

approach

• Mobile base stations

‒ Evolved Cloud-RAN ‒ Enabler for SON

• Home environment

‒ L2 visibility to the home network ‒ Smooth introduction of residential

services

• CDNs

‒ Better adaptability to traffic surges ‒ New collaborative service models

• Fixed access network

‒ Offload computational intensive

• ptimization

‒ Enable on-demand access services

An E2E View: Service-Oriented Use Cases

ETSI NFV

17

• Focused on the differences introduced by NFV

‒ Not on aspects that are identical whether the implementation is physical or

virtual

• High level requirements on

‒ Portability ‒ Performance ‒ Elasticity ‒ Resiliency ‒ Security ‒ Service continuity

• Requirements for supporting

‒ Deployment ‒ Multi-tenant service models ‒ Maintenance

An E2E View: Requirements

‒

Service assurance

‒

Operation and management

‒

Energy Efficiency requirements

‒

Transition and coexistence with existing infrastructures

ETSI NFV

18

Computing Hardware Storage Hardware Network Hardware Hardware resources Virtualisation Layer

NFV Infrastructure (NFVI)

Virtual Computing Virtual Storage Virtual Network

NFV MANAGEMENT & ORCHESTRATION

VNF VNF VNF Virtual Network Functions (VNFs)

The NFV Framework

Apps Apps Apps Apps

• Decoupling NVFs from underlying hardware presents management challenges: services to

NFV mapping, instantiating VNFs, allocating and scaling resources to VNFs, monitoring VNFs, support of physical/software resources.

• M&O addresses these issues. Needs to work closely with OSS/BSS.

Cloud/Net Apps Store

ETSI NFV

19

Computing Hardware Storage Hardware Network Hardware Hardware resources Virtualisation Layer Virtualised Infrastructure Manager(s) VNF Manager(s) VNF OSS/BSS NFVI VNF VNF

Execution reference points Main NFV reference points Other reference points

Virtual Computing Virtual Storage Virtual Network EMS EMS EMS

Service, VNF and Infrastructure Description

Or-Vi Or-Vnfm Vi-Vnfm Os-Ma Se-Ma Ve-Vnfm Nf-Vi Vn-Nf Vl-Ha

Orchestrator

NFV MANAGEMENT & ORCHESTRATION

VNFs

The E2E Reference Architecture

ETSI NFV

20

Network Functions Forwarding Graph

• Provides logical description of interconnecting the VNFs and traffic

flow between them (aka Service Chaining)

• Nested FGs are a possibility
• Need for new visualization & monitoring tools

ETSI NFV

21

ETSI NFV

NFV @ Play

End Point End Point

E2E Network Service

HW Resources Virtualization SW Virtual Resources Logical Abstractions

VNF VNF VNF VNF VNF

Logical Links

SW Instances

Compute Storage Network

Virtualisation Layer NFVI

Virtual Computing Virtual Storage Virtual Network VNF

VNF Instances

VNF VNF VNF

22

• Objectives

‒ Demonstrate and disseminate NFV capabilities ‒ Explore technology options, identify & expose issues ‒ Facilitate gap analysis

• Lightweight process

‒ Few requirements for submitting a PoC proposal (www.etsi.org/nfv-poc)

• At least one network operator and two vendors
• Address at least one goal related to the E2E Use Cases, Requirements, or

Architecture

• Run PoC project

‒ Commercial or academic event, operator’s lab, experimental network…

• Openly report results to the community

‒ At least one contribution to the ISG: the PoC Report ‒ Community will assess PoC through the normal contribution process

PoCs

ETSI NFV

23

OSS/BSS

Billing

Product Catalog

CRM Ordering SLA Reporting Accounting Billing

Product Catalog

CRM Ordering SLA Reporting Accounting

BSS

Monitoring

Performance Management

NMS EMS Service Level Management Provisioning Security Activation

Asset Management

Monitoring

Performance Management

NMS EMS Service Level Management Provisioning Security Activation

Asset Management

OSS

• To exploit its maximum benefits, NFV requires new thinking around the

OSS/BSS and could offer opportunities to gain operational benefits

• NFV M&O components complement

functionality of current OSS

• Interfaces between M&O and OSS

need to be aligned and standardized

• Associated information models and

business processes (i.e., Fulfilment, Service Assurance, Accounting, Security) need also to be aligned and will require to be re-engineered

• Automation will be key
• Will require integration with existing, legacy systems
• As OSS/BSS evolves, implementation process could be operator-specific

ETSI NFV

24

Timeline for NFV ISG Work Program

ETSI NFV

25

ETSI NFV

Open Innovation

Creates competitive supply of innovative applications by third parties

Strategic Networking Paradigms: Open Source & SDN

• NFV and SDN are highly complementary, they are mutually beneficial (software is

common denominator) but not dependent on each other

• SDN can significantly enhance NFV

Creates abstractions to enable faster innovation

Software Defined Networking

Leads to agility, Reduces CAPEX, OPEX,

Network Functions Virtualisation

26

• Elements: Open Source and Open Design/Development
• What should be open?
• Could or should there be standards-based open development?
• Decomposition and modularization: favors best of breed (in a multi-

vendor and multi-carrier/SP environment); commoditization, customization

• Challenges:

‒ (harmonious) integration and consistency ‒ carrier-grade (HA & five 9s, DR/BC, SLAs, reliability) ‒ security, testing & interoperability, certification, regulation

• Wish list for an OpenNFV:

 Build upon existing, diverse open source efforts  Open Environment: allow plug-n-play of different implementations  A sandbox of open source tools would be ideal. Enable telco APIs.

• Create a dynamic, inclusive & synergetic environment to foster open

source NFV and accelerate implementation of NFV

An Open Ecosystem

ETSI NFV

27

Mapping to Open Source communities

NFVI

NFV M&O

Hardware Resources

Computing Hardware Storage Hardware Network Hardware

Virtualization Layer

Virtual Compute Virtual Storage Virtual Network VNF VNF VNF

EMS EMS EMS

OSS / BSS

Service, VNF & Infrastructure Description

Virtualized Infrastructure Manager Orchestrator VNF Managers

VNF OpenStack CloudStack KVM XEN, LXC new for generic VNFs Openstack Cloudstack ? Open Daylight ONOS DPDK ODP (Linaro) OCP

• Open Daylight provides an integrated platform

ETSI NFV

28

• SDN can play a key role in the orchestration of the infrastructure

(physical, virtual)

‒ Use SDN to apply security & other policy control to VNFI ‒ Allocate and manage resources (e.g., bandwidth) ‒ VM mobility ‒ Automation & programmability ‒ Unified control & management plane?

• Service chaining

‒ Traffic flow characterization very important (especially for mobile, E2E

scenarios)

‒ Directing traffic flows to VNFs

• Leverage SDN to create (dynamic) VNs (eg, multi-tenancy for NFVI)
• SDN can play role in aligning OSS/BSS
• SDN could enable and accelerate the virtualization of the network and

the “cloudification” of the carrier (COs/PoPs become DCs)

• Could NFV be a “killer app” for SDN?

NFV+SDN: end-user perspective

ETSI NFV

ETSI NFV

29

Cloud, Data Center & Net

Apps/Services/Functions/Utilities SDN (control, programmability,

management, network virtualization)

APIs

Interfaces, Protocols

Network, Storage

SDN

ETSI NFV

30

Apps Apps Apps

APIs

Computing Hardware Storage Hardware Network Hardware Hardware resources Virtualisation Layer (ODL, NSX, OVX, …) NFV Infrastructure (NFVI) Virtual Computing Virtual Storage Virtual Network

SDN-based MANAGEMENT & ORCHESTRATION

Virtual Network Functions (VNFs) VNF VNF VNF

Apps

SD SDN-ba based NFV

Interfaces, Protocols

SDN Controller OpenStack Neutron

31 Load Balancer WAN Acceleration DPI Switch Firewall Load Balancer WAN Acceleration DPI Switch Firewall Load Balancer WAN Acceleration DPI Switch Firewall

Infrastructure today

Collection of heterogeneous networks

(with lots of duplication)

ETSI NFV

32

FW LB DPI

OSV

SDN CTR

FW LB DPI

OSV

SDN CTR

FW LB DPI

OSV

SDN CTR

VM VM VM VM VM VM VM VM VM VM M&O NV

SDN CTR

EMS OVS

NFV removes the boundaries and constraints in your

• infrastructure. It breaks the barriers and opens up

unlimited opportunities.

ETSI NFV

33

• EVA principle: elasticity, velocity, agility

‒ Flexibility to easily, rapidly, dynamically provision and instantiate new services in

various locations (i.e. no need for new equipment install)

‒ Increased speed of time-to-market by minimising the typical network operator

cycle of innovation. More service differentiation & customization. Great for BC/DR situations

‒ Improved operational efficiency by taking advantage of a homogeneous (physical)

network platform

• Reduced equipment costs through equipment consolidation on high

volume industry standard servers leveraging the economies of scale of the IT industry

• Reduced operational costs: reduced power, reduced space, improved

network monitoring

• Software-oriented innovation (including Open Source) to rapidly

prototype and test new services and generate new revenue streams

• IT-oriented skillset and talent (readily available in global geography,

flexible)

NFV: a Value Proposition (for many)

ETSI NFV

34

Orange, a worldwide presence

• Orange Silicon Valley (OSV), a wholly
• wned subsidiary of Orange, is its

Silicon Valley presence

• Orange is one of the major telcos, in 5

continents, 32 countries, 232 million customers, 6 million business customers

• Internet, Fixed, Mobile, IP TV provider
• 180,000 employees and ~ $ 55 b

revenues in 2013

• Other assets: Dailymotion, Orange

Business Services (OBS)

• Orange Fab: a startup accelarator

Orange Silicon Valley

35 Orange Silicon Valley

• vEPC testbed (@ San Francisco)
• vCDN (@ Orange Labs, France)
• IMS, SBC, NaaS (OBS)

Orange PoCs

36 Orange Silicon Valley

• Virtualizing the EPC goes beyond virtualizing a single function
• Virtualize nodes (MME, SGW, PGW, SecGW), functions

(attach/registration, bearer, PCRF, ANDSF, HSS)

• Benefits:

‒ Elasticity, agility, scalability: launch VMs to handle traffic spikes ‒ Remote operations. Eliminates physical distances between nodes ‒ Portability: “EPC in a briefcase”, e.g, deploy next to eNodeB ‒ Easier to integrate other functions such as IMS, vDPI, caching

• Complete decoupling of control & data planes
• Flexible allocation & deployment of resources
• Challenge: delivering carrier-grade performance

vEPC

37

EPC Virtualization - verticalized

S1

eNB

MME VM HSS VM PCR F VM S- GW VM P- GW VM

Attach Auth. Bearer Contex t

Mobility

Data Policy Attach Auth. Policy Bearer Contex t

Mobility

Policy Data Bearer

Mobility

Contex t

SGi

Internet

• A physical box is mapped to a VM
• Inefficient: still uses many processes and requires encoding/decoding

across interfaces

• Inflexible: high-availability requires duplication

Orange Silicon Valley

38

S1

eNB

Cloud EPC

• Consolidation of multiple physical network infrastructures into one
• Node disaggregation:

‒

• bscures boundaries between functional boxes

‒

can lead to less complexity

• Achieves better service scalability, flexibility. Multi-tenancy (eg, MVNOs)

Attach Auth. Bearer Context Auth. Data Policy Policy

Mobility Mobility

Policy Attach Bearer Bearer Context Context Data

Management & Orchestration

Orange Silicon Valley

39

Orange Silicon Valley

MVNOs

• Cloud-based MVNOs

40

SmartEPC: NFV+SDN PoC

Orange Silicon Valley

ANDSF

Evolved Packet Core

SDN CTRL

• Easier to integrate SDN-based solutions, such as “smart traffic
• ffloading”

‒ Offload traffic based on various & different criteria (e.g., per customer, traffic) ‒ Embed OF agents in VNFs (running on VMs)

• Better management of EPC. Mobile flow characterization
• Does not require vendor to make drastic changes

41 Orange Silicon Valley

• Important NFV use case

‒ Motivation: growth of video IP traffic (live and on-demand) ‒ Objective: cheaper, better, easier delivery of content ‒ In current deployments, CDN cache nodes are designed for peak capacity,

cannot handle unpredictable load needs

‒ Content delivery is very volatile market (changing formats, protocols, etc) ‒ Benefits: higher elasticity, better QoE

• Allows to move content closer to the customer

‒ Support of multiple Hypervisors, improve exchanges between Cache Nodes VMs,

mutualize Storage between VMs, interfaces between Orchestrator and CDN Manager

• Virtualizable CDN components: cache node, CDN controller

vCDN

42

Orange vCDN Testbed

Raw server / no hypervisor HP DL 380 G8

VM Cache node6 VM Cache node7

Cache Node 1

management traffic Switch 1G

SPIRENT Avalanche

client delivery traffic

• rigin server traffic

management traffic HP DL 380 G7 HP DL 380 G8 E5 2670 KIT

10 Gbps link 1 Gbps link

Cache Node 7

Analytics

HP DL 380 G8

Manager

HP DL 380 G8

Request router

HP DL 380 G8

Cache Node 6

• vCDN for scale delivery: trade-off between performances and flexibility
• Architecture: specific distributed architecture mapped onto network physical topology,

explicit redirection of end users to CDN nodes

• Orchestration of delivery for flexible solutions: automation of new nodes’ deployment,

scaling of the service, management of different technologies in different locations

• Results are encouraging

Orange Silicon Valley

virtual Cache Node

43 Orange Silicon Valley

virtual Cache Node

44

• Programmability, ease of integration, deployment velocity, automation.

Brings intelligence into the network!

• Impact on silicon innovation
• Beware of hackers and bugs!!!

Softwarization of networking

45

Takeaways, so far

• NFV will precipitate the move to the telco cloud (collapse of the CO/POP)
• Need to build business cases to quantify claims on CapEx/OpEx savings.

Achieving high performance may require specialized processors.

• All NFV use cases are potential “killer apps”
• Could lead to the invention of new services, architectures & business

models, spawning a new wave of industry-wide innovation

• Open Infrastructure: open source software and hardware
• NFV can dramatically transform the SP landscape and industry over the

next 2-5 years and it is happening right now !

• Next NFV meeting: Malaga, Spain, Feb. 18-21, 2014. portal.etsi.org/nfv
• Make sure you go to the conference receptions !!!

46

• Data Centers are growing (very) fast, ~ 15% every year (they double in 5 yrs)
• Facebook spent $210 m on its Prineville, 28MW Data Center, 330k sq. ft, 150-

200k servers (this is a lot of servers)

The Future (of the) Data Center

• Huge TCO and upfront investment. Quite

centralized architectures. Imagine if telcos had one CO per 100m subs.

• Big data need bigger data centers!

Source: C. BeladyMSFT

• However, this cannot be sustainable (we had the mainframes, aka ‘big iron’, in

the last century, and dinosaurs a bit earlier – they both disappeared)

47

• Fully distributed model: move intelligence, processing, storage to the

edge

• Fact: # mobile devices will surpass world population this year
• May be the “cloud is us”

(uberization of the data center !!)

• Who will prevail? Whoever owns the “network”…
• We need an “out-of-the-data center” thinking!
• Reality check: in 2025!

REXComputing/OCP Summit V

48

49

virtualization (sharing) is the new economy