OPEN-O Architecture Any service on any network

Chris Donley

Christopher.donley@huawei.com

TSC Chair

Why Open Orchestration?

SDN & NFV Adoption

2

Source: Coleman Parkes Research. 2015 for HPE

VIM

SDN CtrlVNFM

BSS: Product Layer

OSS:Service Layer

Network:Resource Layer

App/BSS/OSS

Portal(GUI)

VIM

Customer Facing Service Spec

Resource Facing Service Spec

Network Service Spec

PNFs VNFs

Product Spec

Resource Spec SDN CtrlG-VNFM

GS-OGlobal Service O

SDN-ONFV-O

Promotional/Bundled/Simple Offerings

Product SpecProduct

Resource Facing Service SpecResource Facing Service

Network Service SpecNetwork Service

Resource SpecNetwork Resource

Customer Facing Service

TMF

Customer

Device

ETSI NFV

From OSS to OSS: Where OPEN-O fits in a Carrier Network

TOSC

A

YAN

G

OPEN-O Architecture

4

TOSCA

Yang

Portals OperatorGUI

OSS

Infrastructure Legacy Networks

SDNNetworks

NFVI

Tools

CommonServices

Orchestration Services

SDN-O NFV-O

GS-O

BSS

End-UserPortals

GS-O Global Service Orchestrator

• Targets:E-2-E network service orchestration

• Goal: Unified service orchestration of Legacy & SDN/NFV

network resources

• 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

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

• Typical Scenarios：

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

recovery

SDN-Orchestrator

• Targets：Network Connectivity Services

• Goal: Provide 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 •both static & dynamic

•Model Dry Run 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 and 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

Use Case: vCPE

VLAN VXLAN IPSec

WAN

ThinCPE

PE1

TOR

OS

APP

OS

APP

TOR

OS

APP

OS

BRAS CP

VXLAN VLAN

VIM2(OS2)

DC Controller(Neutron Plugin)

WAN ControllerSuper/D

Controller

AccessController

OPEN-O

GW

overlay

underlay VLAN MPLS BGP L3VPN

OSvCPE

OSvFW

Enterprise Site

Tenant Cloud for Enterprise

POP/TIC Edge

G-VNFM1(Juju/vFW, …)

VIM1(OS1)

S-VNFM1(vCPE)

G-VNFM2(SFC/vVA

S)Neutroninterface

SDN-O NFV-OLegend:

PE2SPTN

pCPEResidential BRAS DP

TIC Core

MPLSTP L2VPN

PE1

S-VNFM1(BRAS CP)

SPTN

VLAN SPTN MPLSTP L3VPN

Catalogue

Modeling for 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 TimeCatalog

Virtual CPE/CE Use Case

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

Current Status• Architecture Committee

– Agreement on preliminary architecture– Integration plan incorporating 7 codebases

• TSC Kickoff – June 7-9• Planning first release

– 4 projects approved (so far)• NFV-O, GS-O, SDN-O, Common Services

– 2+ projects under review• VNF Onboarding, Common TOSCA

12

OPEN-O Release 1 Planning

Common(TOSCA)

Workflow

Parser

Catalog

Model Designer

GS-O

Service Decomposer

Service Lifecycle Mgr.

ServiceFormation

Abstract NBI

GUI Portal

SDNDriver

ACCESS/WAN SDN Controller Drivers

SDN-O

SDN Res.Mgr.

Abstract NBI

Abstract SBI

VPN

SDN Lifecycle Mgr.

Traffic Optimize

SDNMonitor

EMS/NMS Driver

VIM Drivers

GUI Portal

VNFM Drivers

VIM Drivers

NFV SDNController Drivers

NFV-O

NFV Res. Mgr.

NFV Monitor

NS Lifecycle Mgr.

Abstract NBI

Abstract SBI

NFVDriver

GUI Portal

Common Service

HA

Log

Driver Mgr.

Micro-Service Bus

Protocol Stack

Auth.

VNF Onboarding

Q&A

Thank You