OPEN-O Unified NFV/SDN Open Source Orchestrator Hui Deng, China - - PowerPoint PPT Presentation

OPEN-O

Unified NFV/SDN Open Source Orchestrator

Hui Deng, China Mobile Kai Liu, China Telecom Eun Kyoung Paik, KT Chris Donley, Huawei Jim 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 Network Access Data Center BRAS pCPE

Virtualization

vCPE vBRAS vPE Router vFW vLB

E2E Unified SDN/NFV Service Orchestrator

Is SDN only enough?

GW OpenStack

DC controller

TOR

Legacy Domain A DomainB

Vender specific ONOS ODL

SDN 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

• rchestration and it is key to

enable agile service across multi- domainmulti-layer and multi- vendor

Legacy Domain SDN Domain A SDN Domain B

Controller (ONOS) EMS

APP/OSS/BSS

SDN Orchestrator

Controller (ODL)

Commercialized NFV-O?

VIM SDN Controller Huawei vCMM

VNFM

Commercialized NFVOs

Ericsson ZTE

Conductor

Nokia

Cloudband

HP Director ADVA ESO Cinena

Blue Planet Gigaspaces

Cloudify 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?

Orchest rator 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 System OSS— 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

VXLAN VPN

PE1 PE2 P1 P2

Backbone NW

VLAN VPN TE

OVS/TOR VXLAN-GW2 vm24 vm23 vm22 vm21

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

• rchestration and global optimization.

E2E Service O

OVS/TOR vm14 vm13 vm12 vm11

IDC

VXLAN-GW1

KT’s use case: 
 Transport SDN

• SDN controls transport path
• ver multi-vendor devices in

a centralized manner

• Orchestrator optimizes

end-to-end provisioning

MSPP OXC Legacy Transport OXC MSPP PTN PTN 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.

Enterprise WLAN PON PTN PTN

Residential home

Mobile Edge TIC Core TIC

Mobile-DP NFVO NFVO SDN Controller

Open-O Mobile-CP Fix-CP

Fix-DP

OPEN-O benefits for Industry

Vendors like plug-in after pre-

• integration. Operators can plug in/
• ut 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 3 2 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

IP

TCP 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 Vendors

VNF/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-rays
• 2. 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 encryption
• 5. 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

• f SDN + NFV

Sequence Diagram for eHealth Use Case

Portal Common Service Cross Domain-O SDN-O NFV-O SDN Ctrl. Driver VNFM Driver

Service request(eHealth) Service request(eHealth) API gateway: Service request(eHealth) Service Catalog: Verify Service Decompose Service Service Execute 1: vFirewall Create and Deploy Create and deploy vFirewall Service Execute 2: create IPSec VPN(connect to vFirewall) create IPSec VPN Service Decompose/Orchestration Service Decompose /Orchestrate response response response

Notes Didn’t describe the interaction between

• rchestration

Common

response response

Join OPEN-O

Strategic use of open source software


29%

80% OSS

Average * Best in class

* Source: Gartner Group

S t r a t e g i c U s e

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-O

OPEN-O

vFW,vLB,vCP E,vBNG, vEPC…)

OPEN-O

WAN SBI VAS SBI

SDNO

Restful API

Customer Portal/BSS

(E2E Service= VPN+ VAS + Cloud) Controller EMS

VNF

NFVO S-VNFM VIM

NFVI

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

April Feb. March May Sep. July

MWC Intent Announcement 2016.02.23 Speech & Demo

• n ONS

2016.03.16 Official Founding 2016.05 OPEN-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!