OPEN-O Any service on any network

denghui@chinamobile.com

Christopher.donley@huawei.com

• 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

Hybrid network needs comprehensive solution

• Most carriers’ network are hybrid networks (legacy, SDN, and virtual networks)

• Super/domain Controllers focus on network resource abstraction andpath calculation

• Orchestration focuses on end to end service and resource orchestration which requires integrate with OSS/BSS and APPs.

• Orchestration is key to enable agile service across multi-domain，multi-layer and multi-vendor

VIMLegacyDomain

SDN Domain A

SDN Domain B

Controller(ONOS)EMS

APP/OSS/BSS

Super Controller

Controller (ODL)

Unified Orchestrator

VNFM

VIMVIMs

Enterprise Solution is insufficient for Telecom

Network

VNF VNF

VIM VIM

For enterprise, Openstack didn’t care about the network connectivity service delivery.Limitation: flat network

Network A

VNF VNF

VIM VIM

Network B

Network C

Carriers are required to provide connectivity and have to take care of the E2E delivery.

• Complexity of connectivity service delivery is much higher for telecom than for enterprise• Complexity of Telecom VNFs is also much higher than enterprise, such as requirement for 99.999% reliability

Enterprise Solution doesn’t

meet telecom’s requirement

Orchestrator

NFVI

Enterprise NFV

Telecom NFV

Information Model?

BSS/OSS Unified API?Multi-VIMs Support?

Orchestrator

VNFM?

VNFM

OPEN-O: From OSS to OSS for Carriers

OSS— Operation Support System

OSS— Open Source Software

• OPEN-O represents a transition from legacy OSS to a new form of OSS

• A primary goal is to establish an open framework to orchestrate composite services across legacy networks, along with emerging SDN and NFV Infrastructure.

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

OPEN-O benefits for Industry

Improved quality, security, and stability

Avoiding market fragmentation

Avoiding vendor lock-in via interoperable

Faster time to market

6

5

4

2

1

Reduced complexity

Agility in services & operations Establishment of an open ecosystem

Reduced cost on integration by vendor pre-integration

3

What is OPEN-O project?

• 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 Mission & Scope

OPEN-O Architecture

• Orchestration Service consists of GS-O/SDN-O/NFV-O and Orchestration Common. GS-O coordinates orchestration across domains.

• Open-O connects to SDN controllers/VFNM/VIM/EMS through Drivers.

• Common Service provides platform service(Messaging etc.)

• Tools consist of model designer &VNF deployment tool.

• Portal provides GUI mgmt. interface for Open-O.

GS-O Global Service Orchestrator

• Targets:E-2-E network service orchestration

• Biz Goal: Unified service orchestration of Legacy &

SDN/NFV network resources under MV circumstance

• Typical Scenarios: Service LC mgmt. for users/tenants

• Operation- Service design/deployment/activation/provisioning

• Maintenance- Close-loop Automation

NFV- Orchestrator

• Targets：Virtualized applications, network functions

• Biz Goal：NS On boarding, NS LC Mgmt/Resource

Mgmt

• Typical Scenarios：

•VNF Deployment/On-boarding/Scaling/Fault-

recovery

SDN-Orchestrator

• Targets：Network Connectivity Services

• Biz Goal: Establishing CONNECTIVITY across access

& WAN networks

• Typical Scenarios：

•Network connectivity mgmt.

• Traffic Engineering

A Closer Look at OPEN-O

Orchestration Common: Model Driven Framework

Why model-driven?

• Unified service creation and provisioning process needs a normalized data model,

• Model driven configuration & management makes system extensible,

• Model driven framework provides basis for openness of network capability.

Highlights:

•Model conflict detection also provided, both static & dynamic•Model DryRun allow validation before service provisioning

Orchestration Common: Analytics and Policy• OPEN-O with analytics module and policy module becomes more intelligent.• Machine learning methods (e.g. ANN, SVM, logistic regression, etc.) -> Analytics model• The analytics module can predict the future situation to interact with the policy module to control / manage the system.

Double Closed Loop

• Short term (quick response)Data -> Analytics -> Policy -> NFVO Component -> Data

• Long term (slow response)Data -> Analytics -> Policy -> Orchestrator -> NFVO Component -> Data

Data

GS-O

NFV-O/SDN-O

Analytics

Policy short term

long term

predictions

actions

collectionsPolicy Validation

SPP SAP

Policy Designer

Policy Engine

Layered Policy Model

Global policy

Local policy

Catalogue

Modeling Use Case: virtual CPE/CE

Internet Access Service 500M, with Firewall and NATOverlay NS

Internet Access Service 500M with Firewall and Policy Cntl

Overlay NS(Enterprise)

DC Service Chain with vCPE and vNATOverlay NS

(DC)

Underlay Connectivity (complex, multiple CoSs, hierarchical)

Underlay NS

Global-Service-O (GS-O)

NFV-O (DC)NFV-O (Enterprise)

Overlay NS

Overlay NS Topology/Graph

DC Transport

vCPE

vNAT

SDN-O

Underlay NS

Underlay NS Topology/Graph

TransportController 1: Connectivity 1

EMS1: pCE

Controller 2: Connectivity n

EMS2: TTGW

Overlay NS (DC)

Underlay NS DC Topology/Graph

Design TimeCatalogue

Virtual CPE/CE Use Case (One Approach)

Overlay NS (Enterprise)

Enterprise Transport

Firewall

Policy Control

Underlay NS DC Topology/Graph

Enterprise VIMEnterprise SDN

Controller EMSs SDN Controllers DC VIM DC SDN Controller

Join OPEN-O

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,vC

PE,vBNG,

vEPC…)

OPEN-O

WAN SBI VAS SBI

SDNO

Restful API

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

ControllerEMS VNF

NFVO

S-VNFM

VIMNFVI

EMS

G-VNFM

OpenStack

Global Service Orchestrator

Legacy network

SDN network

Service providerPublic 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

• We will propose an orchestrator project in OPNFV, OPEN-O will be integrated in OPNFV

• We are integrating with OPENSTACK VNFM (Tacker)

OPEN Cord

Relationship with Openstack

Global Service-O (GS-O)

SDN-O NFV-OOPEN-O

•Customer facing services are provided

by Open-O

•OpenStack provides ETSI NFV VNFM and VIM services, not end-to-end

orchestration, NFV-O, or connectivity

services.

VNFM

NE NE VIM

Openstack Tacker provides VNF Manager functions

Catalog

Basic life-cycle of VNF

Performance and Health monitoring

Auto Healing

Configuration

NE Tacker

NOVA

Cinder

Neutron

Swift

…….

OPNFV/Openstack Nova/Neutron/etc provides VIM service

Controller

2016 OPEN-O Project Roadmap

MayFeb. March June Sep.July

MWC

Announcement

2016.02.23

Speech & Demo

on ONS

2016.03.16

OPEN-O

1st Summit

Oct.- Dec.

OPEN-O 1st

release

2016.Q4

OPEN-O

Hackfest

Time to declare later

Call for Founding Members until June 1, 2016

2016.06.20

• www.openo.org

Getting involved in OPEN-O

Join the FUN!

Thank You