NETWORK FUNCTION VIRTUALIZATION - AN INSIGHT

(1)

NETWORK FUNCTION VIRTUALIZATION - AN INSIGHT

Presented by Deepanshu Gautam for

(2)

BACKGROUND

(3)

PROBLEM STATEMENT AND OBSERVATION

Problem Statement

• Complex carrier networks with a large variety of proprietary nodes and hardware

appliances.

• Launching new services is difficult and takes too long,

and requires just another variety of box, which needs to be integrated into the

existing network and IT environments.

• Operation is expensive, due to existing procure-design-integrate-deploy cycle.

Observation

• Commercial-off-the-shelf IT-platforms allow to host a large variety of applications.

• New virtualization technology allows to abstract underlying hardware,

and enables elasticity, scalability and automation.

• Network Technology suppliers already use such technologies, but in a proprietary

(4)

VISION

Efficient Resource

Utilization

Remote configuration

and install

Single design based

on commodity

hardware

Reduces OpEX and

VapEX.

Reduces system

complexities

Multivendor network

management

platform

Reduce power

consumption

Rapid Time to Market

Efficient test and

integration bcz of

common infrastructure

….

(5)

ETSI NFV INDUSTRY SPECIFICATION GROUP (ISG)

(6)

In the 2 months since NFV#10:

• 10 new ISG member companies,

• 71 conference calls and 1 F2F meeting week

In the 32 months since the creation of ISG NFV:

• 280 Member companies, (115 ETSI Members, 165 Participant

organisations)

• 1300 people subscribed to the principal NFV mailing list

• 34 Work Items under way, a further 2 NWIs proposed

• Plenary attendance: NFV#1 (165), NFV#2 (285), NFV#3 (242),

NFV#4 (355), NFV#5 (260), NFV#6 (258), NFV#7 (303),

NFV#8(220), NFV#9 (244), NFV#10 (171)

(7)

CURRENT MEMBERSHIP

(8)

NFV ISG LIFE SPAN

8 October 2012 NFV White Paper Released at SDN & OpenFlow summit in Germany February 2013 NFV#1 Kick-off ETSI headquarter, France

Structure decided April 2013 NFV#2 Santa Clara ISG WI created for • E2E architecture, • use cases • requirements • terminology NFV#3 Bonn ISG mainly work on the ISG level documents July 2013 NFV#4 Sunnyvale Phase 1 work continues NFV#5 Malaga •ISG decided to go for Phase 2 •OPNFV proposed NFV#6 Okinawa ISG leadership changes.

•AT&T took the chair position •NOC chair changed affiliation NFV#7 Santa Clara •Docomo took

the ISG vice-chair position

•ISG approves the Phase 2

mission statement •IT was decided

that Phase 2 will develop normative stage 2 (Architecture) work NFV#8 Scottsdale •ISG Phase 2 started •NFV Phase 1 officially ended. NFV#9 Prague •WG chairs and vice chair elected •Phase 2 progresses NFV#10 Sanya ISG decided to make all working drafts publically available NFV#11 San Jose •Phase 3 planning started •Beyond 2016 planning started NFV#12 Jersey City October 2013

ISG releases first set of specifications as a major milestone • E2E architecture, • use cases • requirements • terminology February 2014 MANO#1 MANO#2 May 2014 July 2014 November 2014 February 2015 May 2015 July 2015 October 2015 MANO#3 _{Election of 2} additional ISG vice-chair took place. HP and ALU took the positions

MANO#4 Phase 1 specifications

published

MANO, SWA, REL, INF etc. MANO#5

Chairm an Working Groups INF SWA MAN O REL Expert Group PER PoC SEC TSC NOC Chairm an Working Groups IFA EVE TST REL SEC TSC NOC Phase 3 features proposals starts flowing NFV#13

(9)

LEADERSHIP AND STRUCTURE

Chair

Vice Chair

Raquel Morera,

Verizon Mehmet Ersue, Nokia

(10)

(11)

NFV Architecture

11

Computing

Hardware

Storage

Hardware

Network

Hardware

Hardware resources

Virtualisation Layer

_{Infrastructure}

Virtualised

Manager(s)

VNF

Manager(s)

NFV

Orchestrato

r

OSS/BSS

NFVI

VNF 3

VNF 1

Execution reference points

Other reference points

Main NFV reference points

Virtual

Computing

Virtual

Storage

Virtual

Network

NFV Management and Orchestration

EM 2

EM 3

EM 1

Or-Vi

Or-Vnfm

Vi-Vnfm

Os-Ma

Ve-Vnfm

Nf-Vi

Vn-Nf

Vl-Ha

Service, VNF

and

Infrastructure

Description

VNF 2

VNF

Virtualised Infrastructure Manager (VIM) NF VI Execution reference points Main NFV reference points

EM

VNF Catalogu e Or-Vi Ve-Vnfm-vnf Ve-Vnfm-em Os-Ma-nfvo Nf-Vi Vn-Nf NFV Orchestrator (NFVO)

NFV-MANO

OSS/BSS NFVI Resourc es Or-Vnfm Vi-Vnfm NFV Instanc es Other reference points NS Catalogu e VNF Manager (VNFM) • NS Lifecycle Management • NS Lifecycle Change Notifications • NS Descriptor Management • NS Performance Management • NS Fault Management

Network Service

• VNF Package Management • VNF Image Management • VNF Lifecycle Management • VNF Lifecycle Operation Granting • VNF Lifecycle Change Notifications • VNF Configuration Management • VNF Performance Management • VNF Fault Management

VNF

• vResource Catalog Management • vResource Capacity Management • vResource Performance Management • vResource Fault Management • vResource Management

Virtual Resource

• NFVI Compute Management • NFVI Networking Management • NFVI Storage Management • NFVI Hypervisor Management

(12)

NFV LAYERS VIEW

12

NFV Infrastructure (NFVI)

Compute

Storag

e

Network

HW Resources

Virtualization Layer

Virtualization SW

Virtual

Compute

Virtual

Storag

e

Virtual

Network

Virtual Resources

Network Service

VNF

VNF FG

VNF

PNF

Logical Links Logical Abstractions

End

Point

End

Point

E2E Network Service

VNF Forwarding Graph

(including Service

Chain)

VNF Instances

VNF

SW Instances

VNF

VNF : Virtualized Network Function PNF : Virtualized Network Function

(13)

MANO DESCRIPTORS

13 NSD Id Vendor Version vnfd Vnffgd Vld Lifecycle_event Vnf_depedency Monitoring_parameters Deployment_flavour Auto_scale_policy CP pnfd VNFD vendor descriptor_version version vdu virtual_link connection_point lifecycle_event dependency monitoring_parameter deployment_flavour auto_scale_policy manifest_file manifest_file_security VDU id vm_image computation_requirement virtual_memory_resource_element virtual_network_bandwidth_resource lifecycle_event constraint high_availability scale_in_out vnfc monitoring_parameter id vm_image vnfc id connection_point VNFFGD Id Vendor Descriptor_version Version Constituent_vnf Cp Nfp Depedent_virtual_link Number _of_endpoints number_of_virtual_lin k VLD Id Vendor Version Root_requirements Leaf_requirements Qos connection Connectivity_type Test_access NFP Id policy connection

(14)

VNF LCM OPTIONS

14

VNF LCM in direct Mode VNF LCM in in-direct Mode

• VNFM talk to VIM, for resource management,

directly after getting a permission (granting)

form NFVO for particular LCM operation.

• VNFM talk to VIM, for resource management, via

NFVO even after getting a permission (granting)

form NFVO for particular LCM operation.

Pending Issues:

• Is granting always needed?

• What bout cases where LCM request is received by NFVO in first place.

• Can granting be “delegated”

(15)

IFA008 (Ve-Vnfm)

15

Generic VNFM

Specific VNFM

Vendors Boundaries The most controversial Interface in NFV architecture

(16)

NFVO SPLIT

16

NFVO- DO acts as a proxy between NFV-SO and VNFM

for VNF LCM

NFVO(RO) acts as a proxy between NSO and VIM

hiding underlining multiple VIM form NSO.

(17)

IFA012 (app & services running on top)

17

Details of 'DGS/NFV-IFA012' Work Item

This work item will entail work to specify the interface(s) and the corresponding requirements that comprise

the Os-Ma-nfvo reference point as currently defined in the GS NFV-MAN 001 regarding applications/services

on

top

of Network Services (NS).

• Life cycle management of Services (applications/services on top of NS). • Monitoring/Tracing (e. g. concerning services).

• Flexible/dynamic service orchestration including creation and modification (e. g. orchestration, launching of a service and adaptation of running services.

What is

on-top

??

On-top may imply:

• Grouping:

• Having an existing NS grouped with the

“application/service” on top.

• Full (entire NS) and partial (few VNF of

a NS) grouping is possible

• Grouping may imply dependencies

between NS and “application/service”

on-top.

(18)

(19)

STAKEHOLDERS

• Vendors: providing solutions/products

• VNF/Network Service Vendors

• Converting their existing NFs into VNF/NS

• NFV Hardware vendors (NFV COTS)

• Provide an efficient COTS which can meet integrated hardware in terms of efficiency.

• NFV MANO vendor

• Providing multivendor NFV network management system.

• Legacy NMS (EM, OSS/BSS) vendor

• Saving the current investments

• Network Operators: deploying provided solutions/products

• No-vendor lock-in

• Reducing OpEx

• Reducing CpEx

• Service Providers: consuming NFV service and providing further service to end-users

• VNFaaS, NFVIaaS

• End Users

(20)

STAGE 3 STANDARDIZATION LANDSCAPE

20

??

Standardized Open Source Public

?

(21)

RELATED SDO AND TECHNOLOGIES

21

NFV PHASED DEPLOYMENTS

22

NFV is considered to be a disruptive technology. Specially, it is expected to change the way

current networks is being managed.

The multi-vendor management and

orchestration objective of NFV need to

controlled. Smooth migration is

required.

Phase 1 Phase 2

Phase 3 Phase 4 Final Phase

(23)

(24)

Launched 30 Sep 2014

Speed up implementation of NFV

Create a carrier grade Open Source Ecosystem

OPNFV (OPEN PLATFORM FOR NFV)

Website:

https://www.opnfv.org/

Wiki:

https://wiki.opnfv.org/

OPNFV Arno:

https://www.opnfv.org/arn

o

(25)

OPNFV Project Pipeline

OPNFV CONTND…

For details: https://wiki.opnfv.org/

Next OPNFV release (in discussion) now is called

“OPNFV

Brahmaputra

release aka B release”

(26)

OPEN MANO

26

• Openmano (spelled without capitals), a reference

implementation of an NFV orchestrator

• Openvim, a reference implementation of a virtualized

infrastructure manager (VIM)

(27)

(28)

WHAT ARE THEY?

NFV enables executing existing network functions on virtual

machine where as, SDN separate control flow from data flow.

SDN

Applied

NFV

Applied

(29)

PLACEMENT IN ETSI NFV ARCHITECTURE

29 SDN Controller SDN vSwitch vSwirch SDN OpenFlow

The most obvious

NFV construct

related with SDN

would be NFPs

(network forwarding

path aka service

chain) included in

VNFFG.

SDN could be used

to configure vSwitch

to forward the

traffic as per a

particular NFP.

(30)

SOME USEFUL POINTERS

NFV Public page

• http://www.etsi.org/technologies-clusters/technologies/nfv

NFV published Specifications

• http://www.etsi.org/technologies-clusters/technologies/nfv

All NFV working drafts are publically accessible

• http://docbox.etsi.org/ISG/NFV/Open/Drafts/

NFV PoC updates

• http://www.etsi.org/technologies-clusters/technologies/nfv/nfv-poc

NFV Liaison Matrix

(31)

(32)

RELEASE 2016 TIMELINE

32

Feature

based

2016

Release

(33)

FEATURE PROPOSAL SUBMITTED

33

Total 24 feature proposal were submitted for 2016 release.

30%

18%

11%

7%

4%

4% 4%

4%

Contributions

_AT&T

Huawei

HP

DT

DoCoMo

PTP

(34)

FEATURE PROPOSAL RECOMMENDED BY TSC

Listed in TSC recommendation

NOT listed in TSC

recommendation

Withdrawn/Merged

“New Features”:

FTR002 (CHRG)

FTR003 (NFV_SECM)

FTR007 (POLICY)

FTR008 (SEC4SNC)

FTR013 (VEMOSS)

FTR016 (VNF_PHOTO)

FTR017 (NFV_M&Ms)

FTR019 (SWUP)

FTR030 (NFVWAN)

FTR031 (CONF&IOP)

FTR004 (REAL-TIME)

FTR011 (NFVI_PATH_TEST)

FTR018 (NFV_FM)

NFV039 (INTENT)

“Extensions“:

FTR001 (IM-NFV)

FTR010 (NFVO_ARCH)

FTR026 (HWENV)

FTR035 (FASTSWITCH)

FTR023 (VNFCON)

FTR005 (DM-NFV)

FTR012 (HWMET)

FTR027 (PLACEMENT)

FTR029 (MARKETPLACE)

FTR033 (G-VNFM)

FTR036 (PAAS)

FTR037 (BBF-MSBN)

FTR006 (IOT-5G)

FTR020 (NFVI-EndPoints)

FTR021 (NFVI-EndPoints)

FTR022 (NFVI-EndPoints)

FTR024 (WAN services)

FTR025 (WAN control services)

FTR028 (MAN-REL)

FTR032 (Lightweight Containers)

FTR009 (VNFM_ARCH)

Research Agenda:

FTR004 (REAL-TIME)

FTR014 (DEVOPS)

FTR015 (PNF2VNF)

FTR034 (VCONF)

(35)

FEATURE MAPPINGTO WGs

NFV-IM (FTR001) IFA CHRG (FTR002) IFA NFV_SECM (FTR003) SEC, IFA

Work Item set to

update published

GS(s)

POLICY (FTR007) IFA SEC4SNC (FTR008) SEC, IFA VEMOSS (FTR013) IFA NFV_M&M (FTR017) IFA, SEC, REL

VNF_PHOTO (FTR016) TST, IFA, SEC INTENT (FTR039) EVE, IFA PATH_TEST (FTR011) TST NFVO_ARCH (FTR010) IFA NFV_FM (FTR018) REL SWUP (FTR019) REL, TST, IFA, SEC CONF&IOP (FTR031) TST HWENV (FTR026) EVE, SEC, REL

NFVWAN (FTR030) IFA VNFCON (FTR023) EVE FASTSWITCH (FTR035) IFA

Features

Building Blocks

REAL-TIME (FTR004) EVE, IFA

Work Item set for

feature related

normative work

Work Item set to

cover Stage 3

Work Item set for

feature related

informative work

Work Item set to

update published

GS(s)

Work Item set for

feature related

normative work

Work Item set to

cover Stage 3

Work Item set for

feature related

informative work

EVE

IFA

REL

TST

SEC

To derive work items

Extensions

NFV Information Modelling Charging, Billing and Accounting Security Management Policy Management End-to-End Management Testing Continuous Integration Service and Network