OPEN-OUnified NFV/SDN Open Source OrchestratorHui Deng, China MobileKai Liu, China TelecomEun Kyoung Paik, KTChris Donley, HuaweiJim Zemlin, Linux Foundation

• The following represents general proposals being worked on by a formation community. The following materials have not been approved or endorsed by the members, but represent current working drafts of discussions that we would like to invite a wider community to participate in.

Disclaimer

Why OPEN-O?

Vendor C

MAN NetworkAccess Data Center

BRASpCPE

VirtualizationvCPE vBRAS vPE Router vFW vLB

E2E Unified SDN/NFV Service Orchestrator

Is SDN only enough?

GW

OpenStackDC controller

TOR

Legacy Domain A

DomainB

Vender specific ONOS ODLSDN Controller

Is Controller enough for SDN?

• Most carriers’ network is hybrid network which includes legacy and SDN, and virtual network

• Controller focus on network resource abstraction and path calculation

• SDN orchestration focus on end to end service and resource orchestration and it is key to enable agile service across multi-domain multi-layer and multi-vendor

LegacyDomain

SDN Domain A

SDN Domain B

Controller(ONOS)EMS

APP/OSS/BSS

SDN Orchestrator

Controller (ODL)

Commercialized NFV-O?

VIM SDN Controller

HuaweivCMM

VNFM

Commercialized NFVOs

Ericsson ZTEConductor

NokiaCloudband

HPDirector

ADVAESO

CinenaBlue Planet

GigaspacesCloudify

OSS/BSS

SB Interface Multiple VIMs Option1: SDN controller plugin Option 2: SDN standard interface

Unified IM/ Canonical DM

Option 1: VNFM Plugin Option 2: VNFM standard interface

NB Interface

SDN-O

SDN-O interface

Could Enterprise Solution Meet Telecom Expectation?

Orchestrator

NFVI

Enterprise Solution

Telecom Network

Information Model?

Monitor Capability? Multi-Site? Unified API? Multi-VIMs

Support?

Orchestrator

VNFM?

VNFM

OPEN-O: From OSS to OSS

OSS— Operation Support SystemOSS— Open Source Software

• OPEN-O is working on the new Orchestrator OSS(Open Source Software) as the Next Generation OSS Foundation for ICT Service Agility

OSS

EMS EMS EMS

Device Device Device

Vendor X Vendor Y Vendor Z

Vendor S

Multi-Controller

Multi-VNFM/VIM Multi-EMS

OSS/BSS/APP

Unified Open Source Orchestrator

Service Model definition & mapping & Orchestration

Network /Device Model definition & mapping

network resource discovery & abstraction

3

2

1

APP Layer Portal APP Website

BSS Layer BSS CRM/Billing

M/O-Layer Unified Orchestrator SDNO NFVO

VNFM

VXLANVPN

PE1

PE2

P1 P2

Backbone NW

VLAN VPN TE

OVS/TORVXLAN-GW2

vm24

vm23

vm22vm21

IDC

VNFs

C-Layer WAN Controller DC Controller

China Telecom’s use case: CloudVPN

• SDN supports layer2 connection cross multiple DCs.

• In this case, it needs to support:• End-to-end overlay between multi-DCs• Separated overlay between DC and WAN• Traffic steering for different types traffic• NFVO and VNFM for vCPE and VAS service

• Layered Orchestration architecture provide cross-domain service orchestration and global optimization.

E2E Service O

OVS/TORvm14

vm13

vm12

vm11 IDC

VXLAN-GW1

KT’s use case: Transport SDN

• SDN controls transport path over multi-vendor devices in a centralized manner

• Orchestrator optimizes end-to-end provisioning

MSPPOXC

LegacyTransport

OXCMSPP

PTNPTN

New Transport

SDN Controller

End to End Service Orchestrator

OTN

China Mobile’s use case:Orchestration for TICs

• Two layers of TICs (Telecom Integrated Cloud) are deployed for virtual network services for both fix and mobile network.

• Orchestrator is used to coordinate the service between the two layers.

EnterpriseWLAN

PON

PTN

PTN

Residential home Mobile

Edge TIC

Core TIC

Mobile-DP

NFVO

NFVOSDN Controller

Open-OMobile-CP Fix-CP

Fix-DP

OPEN-O benefits for Industry

Vendors like plug-in after pre-integration. Operators can plug in/out easily. Most viable to work

across vendors

Agility in services & operations

Managed Open Source: PSI is baby sitter without lock-in

Operators can innovate services based on abstract service element

Vendors can do OSS pre-integration – reduce OSS integration time & cost.

5

4

32

1

Significance of Orchestrator Similar to IP

If we can, Open source makes 1 single orchestrator becoming possible, rather than many orchestrators from many vendors

IPTCP UDP

FTP HTTP RTP

Eth ATM

Device1 Device2 Device N

• IP, as the anchor, decouples Transport Protocols from L2 Media, facilitate innovations above & below

• Orchestrator, as the anchor, decouples Operator Service from Vendor infrastructure, facilitate innovations above & below

Orchestrator

HSI VPN

Google FB Netflix

EMS Controller

…… Operators OTT

VendorsVNF/VIM

Device1 Device2 Device N

L4 to L7

L2

What is OPEN-O project?

OPEN-O Mission & Scope

• Enabling end-to-end service agility across SDN, NFV, and legacy networks via a unified orchestration platform supporting NFV orchestration (NFVO and VNFM) and SDN orchestration.

• This platform will be implemented and periodically released as open source software. Its modular nature will support common and vendor-specific data models and interoperability across multiple controllers, VNFs, VIMs and VNFMs.

• Open-O will allow service providers to maximize the use of available network capacity, reduce customization, and accelerate innovation in a multivendor ecosystem

OPEN-O SW Architecture

• End-to-End SDN/NFV Orchestration

• ETSI NFV MANO compliant

• Modular and multiplatform• Service and Resource

Orchestration• YANG and TOSCA support

User Story:1. A doctor sends a patient to the hospital for X-rays2. The doctor needs to set up a VPN connection

between his office and the hospital (L2/L3 vpn) to download the X-Rays

3. Both the doctor and the hospital need to turn on firewall VNFs

4. They also need to turn on encryption5. The VPN should adjust the amount of bandwidth it

delivers – for example, a lot of bandwidth for the X-rays, but only a little for billing records

L2 + L3

VPN

Use Case Example: eHealth application of SDN + NFV

Sequence Diagram for eHealth Use Case

Portal Common Service

Cross Domain-O SDN-O NFV-O SDN Ctrl.

DriverVNFMDriver

Service request(eHealth)Service request(eHealth)

API gateway: Service request(eHealth)

Service Catalog: Verify Service

Decompose ServiceService Execute 1: vFirewall Create and Deploy

Create and deploy vFirewallService Execute 2: create IPSec VPN(connect to vFirewall)

create IPSec VPN

Service Decompose/Orchestration

Service Decompose /Orchestrate

responseresponseresponse

NotesDidn’t describe the interaction between orchestration Common

response

response

Join OPEN-O

Strategic use of open source software

29%

80% OSS

Average * Best in class* Source: Gartner Group

Strategic

Use

Your value add

OPEN-O fills in the gaps between Infra. to OSS

Carrier Networking

Network Controller

Virtual Machines

Operating Systems

Application Platforms

Programming Frameworks

VM/VIM Managers

Hardware

Data Plane Services

Containers

Management and Orchestration OPEN-OOPEN-O

vFW,vLB,vCPE,vBNG, vEPC…)

OPEN-OWAN SBI VAS SBI

SDNO

Restful API

Customer Portal/BSS(E2E Service= VPN+ VAS + Cloud)

ControllerEMS VNF

NFVO

S-VNFM

VIMNFVI

EMS

G-VNFM

OpenStack

Cross domain orchestration

Legacy network

SDN network

Service provider Public cloud

Tacker…

Relationship with other standard bodies

• Open-O plays well with others

• ETSI NFV ISG – architecture and data models

• Open Source projects - OPNFV, Open Stack, Open Daylight, ONOS

• As upstream open source project, open to work with other forums

OPEN Cord

OPEN-O: 1st unified NFV/SDN Open Source Orchestrator

OPEN-O Press Conference on MWC 2016

• OPEN-O project intent is driven by operators and got early supports from 15 SDN&NFV mainstream vendors

AprilFeb. March May Sep.July

MWC IntentAnnouncement

2016.02.23

Speech & Demo on ONS

2016.03.16

Official Founding

2016.05OPEN-O

1st Summit

2016.05

OPEN-O 1st Hackfests

2016.07

Oct.- Dec.

OPEN-O 1st release

2016.09

OPEN-O 2nd Hackfests

2016 OPEN-O Event Plan

Time to declare on May

Getting involved in OPEN-O• www.openo.org

Contact:• rpaik@linuxfoundation.org

Q&A

Thank you!