Limitations of Optimization for Multi-site NFV Network Service - - PowerPoint PPT Presentation

Limitations of Optimization for Multi-site NFV Network Service Delivery

Use Cases and Early Analysis Andy Veitch

Premise

• Orchestration with integrated planning algorithms for

SDN/NFV is necessary to deliver optimal utilization of compute and networking infrastructure and the successful delivery of services (over multiple locations)

• To date, the definitions and development of these in

SDOs and open source projects have been independent

• This is a reasonable time for the IETF (IRTF) to engage in

identifying requirements, architecture options, and possible implications for current (legacy) functions and protocols

Motivation

• SDN / NFV is expected to reduce OPEX and CAPEX
• Orchestration solutions expected to

– Maximize the utilization of infrastructure – compute, storage, network – Keep costs low – Deliver network services that meet SLAs – Follow policies – Minimize migrations

• Tradeoffs – Utilization vs. SLAs
• NFV and SDN orchestration solutions are separate and

independent

– Orchestration for NFV / SFC (MANO) – Orchestration for networks (SDN, PCE) – Deployment planning computations must be unified or cooperative

2016/07/22 3

Activities

• Review use cases
• Review current SDO and open source projects and

current research literature

• Review (some) options for unification / cooperation

– LCM (activation) – Roles – Information passing – Possible requirements

• Review possible impact on IETF definitions
• Develop informational drafts describing use cases and

requirements

PNF

VNF VNF VNF

Simple Network Service

Service defini6on, from network service descriptor Low latency and jiEer required between VNF R and VNF G.

Datacenter 1

PNF

Enterprise

VNFB VNFR

Datacenter 2 Datacenter 3

VNF VNF

WAN

Access

NFV orchestra6on algorithm computes VNF loca6ons based on policies, NFVI resources, costs, etc Solu6on does not account for network conges6on Solu6on considers network service condi6ons. Low latency and jiEer requirement between VNF R and VNF G is met. Lower cost with VNF B in DC 1.

Datacenter 1

PNF

Enterprise

VNFB VNFR

Datacenter 2 Datacenter 3

VNFR VNF VNF

WAN

Access

VNFG

Network Service Descriptor / SFC to instan6ate

VNF VNF

Solu6on 1 – independent planning Solu6on 2 – Unified or Collabora6ve planning

vCDN and virtual IoT (Sensors) Gateways High Volume Rapid Deployment

• Need to support a rapid rise in

source and access to information

– Emergency, e.g. Nice – Rock concerts – shared videos – Natural disasters – sensor data

• NFV enables makes possible the

dynamic, elastic, and scalable deployments

– Sensor gateways – vCDNs, cache servers – Real-time data

• Must consider network, compute

and storage, etc. all together

Service Deployment Adjustments - Migrations

• Monitoring and analytics indicate it is

time to re-configure the deployment of some services

• Examples

– Consolidate services to fewer datacenters, reduce energy usage and costs – Reduce network delays due to congestion – Reduce chance of service interruptions / SLA violations – move paths from OTN circuit showing increased errors

• Migrations are to be avoided

– Impact on service performance – SLA – Each service deployment must consider broader optimization implications

2016/07/22 7

V N F G

Datacenter 1

PN F

Enterpr ise

V N F B V N F R

Datacenter 2 Datacenter 3

V N F V N F G V N F

WAN

Access

PN F

V N F B V N F R V N F B V N F R

PN F

V N F G V N F G V N F G V N F G

Consolida6on raises usage of WAN connec6on between DC 1 and DC

• 2. Even aWer path re-computa6on, the conges6on, latency and loss

may be increased to an unacceptable level. A beEer overall solu6on would be possible if the op6miza6on algorithms were integrated or coopera6ve.

V N F G

Datacenter 1

PN F

Enterpr ise

V N F B V N F R

Datacenter 2

V N F G V N F

WAN

Access

PN F

V N F B V N F R V N F B V N F R

PN F

V N F G V N F G V N F G V N F G

Opportunity to consolidate to Datacenter 2 and reduce opera6ng costs of DC 3.

Openstack with OpenDaylight – Split Optimization

• OpenStack

– Receives a network service request via Tacker – Chooses how and where to implement with Nova, Swift – Communicates SFC connectivity graph via Neutron (networking-sfc)

• OpenDaylight

– Processes connectivity needs and computes connections to meet requirements – Establishes connectivity using underlying networking technology – No feedback possible to OpenStack for smarter VNF placement

2016/07/22 8

OpenStack OpenDaylight Datacenters/WAN

VNF 1 VNF 2 VNF 3

Tacker Nova SwiW Neutron SFC Networking-sfc Loca6ons and connec6vity requirements Network SBI Computes connec6vity Path compute

ETSI Architecture

• Introduces WIM as integration point from NFVO to WAN Controller

E2E Orchestrator Controls NFV and Network

NFVO

WIM / WAN Controller

Topology

E2E Orchestra6on

NFVI-PoP X1

network

VNF

VIM

NFVI-PoP X2

VNF Ms

network

VNF VNF Netw

• rk

Contr

• l

Gateway Gateway VNF VNF VNF

VIM VNF Ms

Netw

• rk

Contr

• l

WAN J Network Controller WAN K Network Controller

Op6cal Network Packet Network

• Used in a number of open source
• E.g. Open O, MEF LSO, TMForum

NFVO Collaborates with WAN Controller

NFVO

WIM / WAN Controller

Topology

OSS

NFVI-PoP X1

network

VNF

VIM

NFVI-PoP X2

VNFMs

network

VNF VNF Network Control Gateway Gateway VNF VNF VNF

VIM VNFMs

Network Control

WAN J Network Controller

WAN J

WAN K Network Controller

WAN K

Gateway

• Used in some open source
• SONATA

Admin Domain X Admin Domain X Admin Domain Y

Hierarchical and Multiple NFVOs

WAN Network Controller

Topology

NFVI-PoP X1

network

VNF

VIM

NFVI-PoP Y1

VNF Ms

network

VNF VNF Netw

• rk

Contr

• l

Gatew ay Gateway VNF VNF VNF

VIM NFVI-PoP X2 VNFM s network VNF Netwo rk Contr

• l

VNF VNF

Gateway

VIM VNF Ms

Netw

• rk

Contr

• l

NFVO NFVO NFVO OSS Op6cal Network WAN

WIM / WAN Controller

Common Agents Across Architectures

NFV Agent NFVO Network Agent SDN Controller / PCE Integrated Op6miza6on / Orchestra6on NFV Agent NFVO Network Agent SDN Controller / PCE

NFV Agent NFVO Network Agent SDN Controller / PCE Integrated Op6miza6on / Orchestra6on NFV Agent NFVO Network Agent SDN Controller / PCE NFV Agent NFVO Network Agent SDN Controller / PCE Integrated Op6miza6on / Orchestra6on NFV Agent NFVO Network Agent SDN Controller / PCE

• Identify

– Possible roles of agents

• Where are functions located
• Multiple options

– Knowledge representation options

• What is necessary to enable the rapid

computation

• Information distillation or summarization

– KPI, policies, etc

– Implications on functional blocks and communications

• Controllers, PCE, etc
• What information is exchanged and

when

– Develop requirements

Catalogue Topology Instances Resources Policies

Next Steps

• Continue use case definitions and analysis an document
• Develop requirements and document
• Evolve (update) and validate, repeat

– Coordinate in open source, etc.

Relevant IETF Work

• PCE

– PCEP

• TEAS

– Controller based TE / Hybrid

• ALTO

– NFV/SDN

• SFC

– H-SFC

• YANG modeling