7th sdn expert group seminar - session4

© Copyright 2014 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.

HP Open NFV Communications & Media Solutions, Enterprise Services Cho, Woo Chan April, 2014

© Copyright 2014 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. 2

Agenda

NFV Vision Overview What are the NFV/SDN? NFV Standard Management challenges of NFV HP Solution for NFV Management & Orchestration Pan-HP Launch Overview Why HP for NFV/SDN? Q&A


NFV Vision Overview


NFV – the new business of the network Improves OPEX •  Move from Telco opex model, to lower cost IT

opex model

Lowers CAPEX •  Move from dedicated appliances to

virtualization model based on IT technology Accelerates time to market •  Deploy new software and new services quickly

and easily (from months to minutes)

Accelerates innovation via an open platform •  Broaden access to partners who can innovate

not just NEPs but also start ups, ISV’s…

Delivers business agility •  Rapidly scale up or scale down applications

modify QoS, deliver new services faster

Why now? Change is not optional

•  Revenue/value shift to OTT •  IP network cost outweighs

revenues generated


2013-2015

Single-purpose element

Control plane

Application plane

Data plane

2014-2016 2015-2020

NFV-SDN Projects Cloud ready Agile Next Generation

Enable evolving operating / business models

SP#1fixed

SP#5DSP

SP#4IaaS

SP#3 SDN ASP

SP#2mobile

Control plane

Applications plane

Infrastructure plane

XaaS Services

SP#n Control plane

Applications plane

Infrastructure plane

SaaS Services

A dynamic future for CSPs


What are the NFV/SDN?


Ability to provide network functions on industry standard platforms

What is NFV?

Classic network appliance approach: •  Cumbersome • Proprietary • Manual

Router

CDN

Session border controller HSS DPI

Firewall

EPC HLR SGSN/ GGSN

CPE

BRAS PCRF

Network virtualization approach: • Agile • Standard • Automated

Standard high-volume Ethernet switches

Standard high-volume storage

Standard high-volume servers

Software vendors

Virtual applications

Transition


NFV business benefits

Cost / ROI

•  Reduced physical equipment costs •  Optimized power consumption by adapting to real-time

demand •  Shared physical infrastructure for production, test and

reference facilities •  Simplified operations of uniform, homogenous physical

platform

Business agility

•  Increase velocity of time to market – short maturation cycle, economy of scale

•  Phased and per-geography service introduction without physical presence

Scalability / flexibility

•  Rapid scale up and down of service infrastructure •  On-the-fly optimization of networks and topologies to

meet real-time demands • Multi-tenancy support of tailored services for enterprise

customers and partners

Innovation

•  Enable new services and new revenue streams •  Open ecosystem reducing risks of and agility for smaller

player participation and innovation

From Proprietary Platforms to Genera Purpose Platform


The move to NFV standardization

Discussion about NFV started among thirteen tier-1 operators Met at the 2012 SDN and OpenFlow World Congress Published an NFV White Paper Decided to pursue the NFV work through the European Telecommunications Standards Institute (ETSI) ETSI Industry Specification Group (ISG) on NFV Define requirements, architecture specifications, identify applicable standards (and their gaps), and guidelines for developing network functions Goal of completing work by January 2015

Over 100 companies participating Direction set by Network Operators Council Work groups: •  Infrastructure Architecture •  Management and Orchestration •  Software Architecture •  Reliability and Availability Expert groups: •  Security •  Performance and Portability

HP is a full member of ETSI and actively participates in and contributes to the NFV work


An emerging software based network architecture

Applications Layer

Control Plane

Data Plane Network Device

Network Device

Network Device

Network Device

SDN Controller Network Services

Network Services

Applications

Applications

Applications

Control Data Plane Interface ( Openflow)

API

SDN and NFV are not dependent on each other but highly complementary

Abstraction of control plane from forwarding hardware •  Network control plane as a centralized software program •  Centralized intelligence of network topology •  Dynamic and programmable network, interaction with

applications •  Implemented via variety of methods including OpenFlow

protocol

Key Benefits •  Provides opportunity for rapid innovation in networking •  Use cases for all types of networks including Enterprise

Campus, Service Provider, Cloud, Data Center •  Can enable simplified management through network

virtualization

What is SDN? Intelligent SERVICE Orchestration


Innovation of Software-Defined Networking

OpenFlow

Innovation!

Standard interfaces and programming languages

UC &C application

OpenStack virtual cloud

3rd party application …SDN Business

Applications

Standard Network Operating System

Proprietary Apps (MC, Routing, QoS)

Proprietary OS (IOS, JUNOS, …)

Proprietary Hardware


Virtualization coming together for the CSP


NFV Standard


HP solutions are based on CSP-defined needs

Leadership in Standards Bodies

Open Network Foundation HP is a founding member and chairs the Extensibility working group

European Telecommunications Standards Institute HP co-chairs and contributes to multiple groups in the NFV ISG

Alliance for Telecommunications Industry Solutions HP participates in the ATIS SDN Landscape Team


ETSI end-to-end architecture

Independence of functions provides flexibility Virtualized network function (VNF) separated from logical environment •  Core NFV proposition

NFV management and orchestration separated from logical environment (virtualization layer) •  Allows different virtualization technologies to be

employed

NFV orchestration is separated from VNF •  Allows orchestration to make decisions based on

complete environment, not just a single VNF

ETSI GS NFV 002 V1.1.1 (2013-10) NFV M

anagement and Orchestration

Virtual Network Functions (VNFs)

VNF 1

EMS 1

VNF 2 VNF 3

NFV Infrastructure (NFVI)

Hardware resources

Virtualization layer

Virtual compute

Virtual storage

Virtual network

Compute Storage Network

OSS/BSS

Orchestrator

Virtualised Infrastructure

Manager(s)

VNF Manager(s)

Execution reference points Main reference points Other reference points

Service, VNF and Infrastructure Description

EMS 2 EMS 3

Or-Vi

Or-Vnfm

Vi-Vnfm

Os-Ma

Se-Ma

Ve-Vnfm

Nf-Vi

Vi-Ha

Vn-Nf


Early use cases (ETSI NFV ISG)

Virtual EPC (Evolved Packet Core)

Virtual Appliance

Virtual CPE consumer (Customer Premise Equipment)

Virtual IMS (IP Multimedia Subsystem)

Virtual Base Station and Cloud RAN

NFV

Reduce Capex Opex

Agility

Multi Tenancy

Increase Revenue Reduce

Power & Space

Innovation Virtual CPE Enterprise

(Customer Premise Equipment)


Four different levels of capability

HP view of the NFV adoption

NFV Level 4: autonomous • Dynamic rule-based provisioning and management with fully automated operational tasks (e.g., automatic scale-in, scale-out, or migration based on threshold crossing)

NFV Level 3: elastic • The ability of a network function to define and automate elastic operations. Examples including startup shutdown, scale out, scale in, migration, etc.

NFV Level 2: virtualized • The ability of a network function to run in a virtual machine or some other abstraction mechanism between the logical environment seen by the network function and the actual physical infrastructure

NFV Level 1: COTS-capable • The separation of the network function from the physical infrastructure, allowing the network function to be run on any appropriate physical infrastructure


NFV Level 1: COTS-capable

OSS considerations Many existing OSS will easily adapt •  Operational aspects of network function are similar

to existing equipment being replaced •  Hardware and OS are introduced as new components

previously not visible –  IT components become directly visible to OSS and

require management •  OSS systems may have visibility of all three

components instead of just one

NFV Orchestrator Adds minimal value

Network function delivered as software running on COTS infrastructure

Operating System

Hardware

Network function

OSS


NFV Level 2: virtualized

OSS considerations Existing OSS systems may require some adaptation •  Operational aspects of network function are similar to

level 1 NFV (and existing equipment) •  Requires capabilities needed to manage NFV maturity 1 •  Layer of indirection between virtualized network

function and hardware •  OSS components may need to understand mapping from

virtualized network function to hardware

NFV Orchestrator Only very basic NFVO functionality is required •  Create/delete VM •  Start/stop VM

Network functions virtualized onto logical servers

NF


Hardware

NF

Network function

VM + OS VM + OS VM + OS

Network function

Network function

Note: other virtualization approaches are possible

OSS


NFV Level 3: elastic

OSS considerations Modern OSS systems should be able to adapt •  Requires capabilities needed to manage NFV maturity 2 •  Virtualized network functions may dynamically add,

delete, or move virtual instances •  Other OSS systems need to be aware of dynamic nature

of a VNF NFV Orchestrator Requires NFV orchestrator that can support requests about NFV instances •  Create, delete, resize, admin, etc. •  Support simple VM and static networking scenarios •  Templates for each of the different virtualized functions

contain minimal topology information •  Handle requests from VNF, EMS, or OSS

Elastic operations on virtualized network functions


Hardware

NF

VM + OS

VM + OS

VM + OS


Hardware

NF

VM + OS

VM + OS

VM + OS

NF NF NF Stop

Scale out, scale in, migrate, etc.

NFV Orchestrator

OSS

Monitoring Fulfillment


NFV Level 4: autonomous

OSS considerations Only well-architected OSS will be able to adapt •  Requires capabilities needed to manage NFV

maturity 3 •  Other OSS systems need to support the dynamic

nature of a VNF

NFV Orchestrator Requires a full-featured NFV Orchestrator •  Full understanding of NFV Descriptors •  Complex and dynamic network provisioning as part

of creating or deleting an NFV instance •  Policy engine that can monitor and react to

performance changes

Full dynamic policy-based control of virtualized network functions


Hardware

NF

VM + OS

VM + OS

VM + OS


Hardware

NF

VM + OS

VM + OS

VM + OS

NF NF NF Stop

Dynamic policy-driven

NFV Orchestrator

OSS

Policy Monitoring Fulfillment


Management challenges of NFV


NFV adoption is not an option, yet it is deeply transformational and risky for CSPs

NFV Challenges for the CSP

Ø  Cost of transformation Ø  Need Telco grade availability, performance and SLAs Ø  Future proof architecture to cope with NFV uncertainty

Ø  Integration within existing OSS/BSS environment Ø  How to maintain Customer and Services view correlated to underlying infrastructure Ø  Need Automation to enable NFV agility Ø  How to ensure reduced Operations costs while deploying NFV

Ø  CIO vs CTO Power fight Ø  Automation will create redundancies and have social impact Ø  Purchase chain and interfacing will drastically change

Infrastructural

Organizational

Operational


CSPs demand vendors to focus also on operational challenges

NFV Operational Challenges for the CSP

•  Seamless integration with existing OSS/BSS systems, processes and practices •  Correlation across Network Service, VNF, Infrastructure and Network to provide

end to end view of services to guarantee customer experience •  Management Automation to enable NFV agility •  Affordable and flexible solution with multi-vendor capabilities that removes

vendor dependency

NFV Transformation Requires Orchestration Capability


CSCF

MSE

Slide includes animations which helps illustrate the

concepts. Operational complexities introduced by virtualization

Virtualization layer introduced Requires management Complicates mapping New network functions can be quickly introduced Services may be hybrid Including virtual and physical network functions Components inside VNF are exposed The NFV Components can have a very dynamic lifecycle A single VNF can be distributed across multiple sites A VNF (or VNFC) can move A VNF component can scale out… …or in

…expanding one VNF

IP layer

Optical transmission

IMS AS

MGCF BGCF

Virtual network

functions

MRF-1 MRB-1

MRF Strg-1

MRF-2 MRB-2

MRF Strg-2

MRF

MRF-1a

CSCF


NFV physical realization Challenges Applications split across racks and/or across data centers •  Service components may need to move across data centers Service will encompass resources at multiple sites across WAN Support of geo-redundancy Service view needs to encompass all resources and dependencies Management layer needs to address •  Both compute and network aspects of the service •  Agility in fulfillment across sites •  End to end service assurance NFVO needs to be aware of geographic distribution Maintaining a consistent view across network and compute Providing a simplified abstract view to the VNFs

Applications replicated across multiple data centers

Radio/Access Network

WAN domain

Data center domain

Servers and Storage

Data center domain

Servers and Storage

VNF VNF

VNF VNF

Customer site

vCPE


NFV projects proliferate

Why an “NFV orchestrator”?

Virtual Infrastructure Manager

VNF

Native hypervisor and

networking calls

Physical infrastructure

Legacy NW

VNF Manager/EMS


NFV projects proliferate… simple approach causes operational difficulties

Why an “NFV orchestrator”?

Virtual Infrastructure Manager Virtual Infrastructure Manager VIM

VNF VNF/EMS VNF VNF

Native hypervisor and

networking calls


Legacy NW

VNF Manager/EMS VNF Manager/EMS VNF Manager/EMS

SDN controller


NFV orchestrator manages abstraction layer

Successful NFV deployment

Virtual Infrastructure Manager Virtual Infrastructure Manager VIM

VNF VNF/EMS VNF VNF


Legacy NW

VNF Manager/EMS VNF Manager/EMS VNF Manager/EMS

SDN controller

NFV orchestrator

Open Standard

API


HP Solution for NFV Management & Orchestration


Introducing HP NFV Director

Introduce and manage network services (NS) Even if they consist of mixed virtual and physical network functions Automatically manages the end-to-end service across VNF, VNF-FGs, and NSs Allow NS and VNF to easily span sites Consistently manage virtual network functions (VNF) Enforce consistent policy across all VNF In coordination with external VNF Manager or using embedded VNFM capabilities Provide visibility across all NS, VNF and resource pools Understand what virtual and physical resources each is using Support different infrastructure technologies Different virtualization technologies SDN, traditional, and legacy networking

Delivering NFV orchestration to operationalize NFV NFV M

anagement and Orchestration

NFV Director Policy management

Service fulfillment

Service monitoring

Global resource

fulfillment

Global resource

monitoring

Virtualized Infrastructure Manager

Catalog

Global resource inventory

Instance inventory

VNF fulfillment

VNF monitoring

External VNF Managers Embedded VNF Manager

VNF fulfillment

VNF monitoring


CSCF

MSE

Slide includes animations which helps illustrate the

concepts. Addressing the operational complexities

Network service lifecycle Provided by NFV orchestrator (NFVO) Ø  NFV Director VNF lifecycle Provided by VNF manager (VNFM) Ø  NFV Director embedded VNF Manager Ø  NFV Director working with external VNF Manager Global resource management Provided by NFV orchestrator Ø  NFV Director

Managing virtual infrastructure Provided by virtualized infrastructure manager (VIM) Ø  NFV Director works with HP or 3rd party VIM Ø  NFV Director directly handles resources not under VIM control Mapping virtual to physical End-to-end view provided by NFV orchestrator Ø  NFV Director

IP layer

Optical transmission

IMS AS

MGCF BGCF

Virtual network

functions

MRF-1 MRB-1

MRF Strg-1

MRF-2 MRB-2

MRF Strg-2

MRF

MRF-1a

CSCF


HP NFV Director network-focused features

Supports the end-to-end network Manage multi-domain, multi-technology and multi-vendor network infrastructure Manage SDN, traditional (non-SDN), and hybrid networks Model-driven approach Models can be extended to address ne domains or technologies Full tear-down on VNF scale-in or decommissioning Desired State Engine dynamically determines steps to go from current state to desired state Uses proven Telco-grade activation engine Transactional capabilities Automated error handling Fault tolerant configuration

Supporting the network needs of NFV

Radio/Access Network

WAN domain

Data center domain

Servers and Storage

Data center domain

Servers and Storage

App App

App App

Customer site

vCPE

HP NFV Director


Example: Flow-chaining for Gi-LAN

NFV and SDN Orchestration

F1 F2

Primary flow

F1_secondary F1_secondary

Secondary flow (load-balanced)

HP TSA (Traffic Steering Application)

HP SDN Controller Logical, abstract SDN OpenFlow

switching domain

REST API

OpenFlow protocol

What is missing in this picture? •  Protection by redundancy •  Automated elasticity … •  Geographical distribution … •  End-to-end orchestration … F1_primary F2_primary


Example: Flow-chaining for Gi-LAN

NFV and SDN Orchestration

F1_primary

WAN domain

Location A

Location B

F2_primary


HP NFV Director

Physical, concrete multi-technology

domains

Other virtualized network functions

F1 F2

Primary flow


Secondary flow (load-balanced)

HP TSA (Traffic Steering Application)

HP SDN Controller Logical, abstract SDN OpenFlow

switching domain

REST API

OpenFlow protocol

F1_primary F2_primary


HP NFV Director example use cases

…


Load Balancing

Serving Gateway eNodeB HP NFV Director

HP Virtualized Infrastructure Manager (MOE or CloudSystem 8)

Monitor performance

Create/delete VM

Create/delete Net Threshold

MME VM MME VM MME VM …

HP Blades and Network (with SR-IOV and Intel DPDK)

vEPC Use case


vCPE Use case

Physical CPE deployment Initial deployment and replacement Bare metal provisioning (or pre-loaded) OS/Hypervisor and application upgrades Access services Internet, telephony, TV, VPN, … Virtual appliance services Router, IDS, firewall, WAN acceleration, … Campus/site LAN Optional management of switch, port, access point, etc.

Virtual CPE applications

Customer site LAN/access points

(optional)

Physical CPE server

Backend functions (physical or virtual)

(PE, AAA, VPN, ACL, etc)

Firewall

WAN acceleration

Router

Internet

VPN

HP NFV Director

Resource Management

Service Management

Zero-touch configuration

Network access (when required)


vCDN Use case (1/2)

CDN is composed of several components Control Plane •  TLDDNS, CDNLOGGER , CDN MANAGER,

Control Service Nodes •  TOPOLOGY , ORIGIN TRACKER PLUBISHER

Delivery Regions •  ENDPOINTS

HP NFV Director provides NFV orchestrator and VNF manager Fulfillment and assurance planes

Endpoints can scale out and in to accommodate increases and decreases in load. NFV Director

INTERNET

ISP DNS

CDN Plyaer

DELIVERY REGION

CONTROL PLANE

CONTROL SERVICE NODES

TLD DNS

CDN LOGGER

CDN MANAGER

TOPOLOGY

ORIGIN

PUBLISHER

TRACKER

ENDPOINT01


vCDN Use case (2/2)

NFV Director Orchestrates the deployment of virtual CDN VNF 1. Provides visibility into the running components Automatically scales Endpoint based on load 2. Monitor CDN endpoints for congestion

3. Upon congestion

4. Scale out CDN endpoint

5. When congestion is cleared

6. Scale in CDN endpoint

How NFV Director leverages CDN virtualization

Virtualized Physical or Virtualized Virtualized scalable

Endpoint 1 TLDDNS

CDN Manager

CDNLOGGER Origin

Publisher

Tracker

Topology

NFV Director

VNF fulfillment

Policy management

VNF monitoring

Resource fulfillment

Resource monitoring

Endpoint 2

1

2

3 4

5

6


Pan-HP Launch Overview OpenNFV program “The New Business of the Network” for CSPs


Announcing: HP OpenNFV Program

Technology & Architecture • Open, NFV-ready architecture, including vertical IP, enabling CSP to

transition to NFV; pulling in and through NEP and emerging ISV solutions and components as desired

OpenNFV Labs • The one-stop center where integration, collaboration & testing can

occur is a safe environment ahead of deployment to carrier networks

Partner Program • Access to SDK’s, API’s, training and integration resources to get

applications tested and ready for CSPs – advancing innovation while reducing risks

Proof of Concepts, Deployment, & Services •  Catalog of Proof of Concepts already completed and ready for

deployment. World class service designed to get you in service and support for years to come

Providing an open, proven and innovative environment for NFV transformation

Technology Architecture

OpenNFV Labs

Partner Programs

POCs, Deployment &

Services


OSS

…

Logical environment

Network Compute & storage

NFV Managem

ent and Orchestration

NFV Orchestrator

VNF Manager

Virtual Infrastructure

Manager

Physical Infrastructure Management

EMS EMS VNF EMS EMS VNF

EMS EMS VNF

EMS EMS EMS

The HP OpenNFV Program solution areas

HP NFV Director Operationalizing NFV through an NFV orchestrator with embedded VNF manager capabilities HP OSS solutions Combining HP’s OSS and IT management capabilities to deliver an OSS adapted to NFV HP Next Generation CloudSystem The leading provider of COTS based NFV Infrastructure HP VNF ecosystem HP VNF coupled with a foundation to support the vast 3rd party NEP and ISV applications

HP OSS Solutions

HP NFV Director

HP Next Generation CloudSystem

HP VNF ecosystem


New - HP NFV Director Enhanced ETSI compliant NFV orchestrator

Resource Management & Orchestration

Virtualization Hypervisors Controllers

… EMS EMS VNF EMS EMS VNF

OSS/BSS

Lifecycle and change mgmt Assurance Fulfillment

Servers and storage Network

Ana

lyti

cs

HP NFV Director


New - HP CSP ready Virtualized Network Functions

Mediation Subscriber Profile Server

Policy Fraud Revenue Assurance

Cloud Service Enablement

SDP API Management

CDN NOC Virtual Service Routers

Home Subscriber

Server

Application Server

Media Resource Function



Standard high-volume servers

Software vendors

Virtual applications Orchestrated

Virtualized


Integration, Collaboration and Testing

New - HP OpenNFV Labs – Global

Foundation •  An NFV foundry supporting HP’s development and

testing of carrier-grade NFV offering

Partners •  Onboarding of partners for validation of the

interoperability of complex multi-vendor applications (accelerating app innovation for CSPs)

For CSPs •  Rapid delivery of customer proof-of-concepts

NFV POC

Take a NFV Collaboration Test Drive Request a PoC Today


Designed to get CSP, ISV, OEM … operational faster

New - HP OpenNFV Services

Enterprise Services •  Hosted & Onsite Labs for Customer PoCs •  Carrier Consulting •  Carrier Application Support Services •  Integration & Support Service

Technology Services •  Platform & Outcome Consulting •  Platform Integration •  Lifecycle Support Services

HP Financial Services


HP OpenNFV in Action today

)

Virtualized Content Delivery Network (US)

Virtualized Content Delivery Network (EMEA)

Virtualized VOIP (EMEA)

HP / Intel Solution Center (EMEA) (NFV orchestrator, vIMS, vCDN)

Various Functions (BRAS, vCDN, vFirewall, vRouter)

Virtualized Session Boarder Controller (APJ)

00

NFV becomes big business in 2014!


Why HP for NFV/SDN?


HP has all the key ingredients for the NFV transition

HP in NFV & SDN

Industry-standard servers

Telecom Software


OF based SDN



HP develops lighthouse SDN customers

2011 HP delivers commercial OpenFlow switches

HP history in NFV and SDN

HP & Stanford collaborate on Ethane 2007

HP engaged in multiple NFV customer POCs 2013 (Q1)

2013 (Q4)

HP demonstrates Federated SDN Controllers, launches SDN Ecosystem

2012

HP starts first NFV POC in Aug 2011

2005 HP introduces Multi-guest OS

2000 HP Superdome supports UNIX-based hypervisors

2008 HP demos OpenFlow Enabled switch

OpenFlow 1.0 released

ETSI forms NFV ISG

SDK, Apps, Training, Support


NFV enablement services

HP: Your Enablement Partner for NFV/SDN

OSS

Orchestration &

Resource Management

Key to the reader: = execution plane = mgmt/control plane

•  HP NFV Director •  HP CloudSystem

«foundation» •  HP OneView

•  HP Telco applications (IVR, CDN, Virtual Router, HSS, CSCF, EPC)

•  Partnerships with all major hypervisor vendors

•  HP VAN SDN controller

•  HP 3PAR Storage •  HP networking •  HP OpenFlow enabled

switches

NFV Applications

Hypervisors/Controllers

Converged Infrastucture

•  HP OSS portfolio

Consulting Implementation Managed Services and Support


Why HP for NFV/SDN?

ü  HW and Software NFV-SDN Ready Portfolio

ü  Expertise and knowledge of CSP’s network and IT

ü World class NFV optimized infrastructure ü  Open architecture enabling choice ü  Portfolio of VNF’s ü  Open NFV partner ecosystem ü  End-to-end lifecycle approach


Thank you

7th sdn expert group seminar - session4

Technology

traic steering

packard development

customer premise

virtualized

existing equipment

oss systems

dynamic nature

network function