1. OPEN-O for MODM Unified NFV/SDN Open Source Orchestrator
Chris Donley, Huawei

2. Disclaimer
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.

3. Why OPEN-O?
Vendor C

4. E2E Unified SDN/NFV Service Orchestrator
Is SDN only enough?
E2E Unified SDN/NFV Service Orchestrator
Virtualization
vCPE
vBRAS
vPE Router
vFW
vLB
SDN Controller
Vender specific
ONOS
ODL
OpenStack
（DC controller）
DomainB GW
TOR
pCPE
BRAS
Legacy
Domain A
MAN Network
Data Center
Access

5. Is Controller enough for SDN?
APP/OSS/BSS
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
SDN Orchestrator
Controller
(ONOS)
Controller (ODL)
EMS
Legacy
Domain
SDN Domain A
SDN Domain B

6. Commercialized NFV-O? SDN-O interface NB Interface Unified IM/
OSS/BSS
SDN-O interface
NB Interface
Commercialized NFVOs
Unified IM/
Canonical DM
Huawei
vCMM
Ericsson
ZTE
Conductor
Nokia
Cloudband
SB Interface
Multiple VIMs
Option1: SDN controller plugin
Option 2: SDN standard interface HP
Director
ADVA
ESO
Cinena
Blue Planet
Gigaspaces
Cloudify
Option 1: VNFM Plugin
Option 2: VNFM standard interface
Lack of integrated orchestration with SDN networking
vCPE use-case demands not only NFV orchestration within the DC and also SDN orchestration for chaining home GW with vCPE and other VNFs to fulfill end-to-end on-demand service orchestration
Lack of reference implementation to enable interoperability before standard specification
Prorietary Information Models of various commercial NFV orchestrators blocks interoperability of various MANO/NFV components and introduces potential vendor(s) locking-in.
There is currently no standard specification on or reference implementation of south bound interface to G-NFVM/S-NFVM.
VNFM
VIM SDN
Controller

7. Unified Open Source Orchestrator
OPEN-O: From OSS to OSS
OSS— Operation Support System
OSS— Open Source Software
OSS/BSS/APP 3
OSS
EMS
Device
Vendor X
Vendor Y
Vendor Z
Vendor S
Service Model definition & mapping & Orchestration
Unified Open Source Orchestrator 2
Network /Device Model definition & mapping
Multi-Controller
Multi-VNFM/VIM
Multi-EMS 1
network resource discovery & abstraction
OPEN-O is working on the new Orchestrator OSS(Open Source Software) as the Next Generation OSS Foundation for ICT Service Agility

8. OPEN-O benefits for Industry
Agility in services & operations
Vendors like plug-in after pre-integration. Operators can plug in/out easily. 5
Most viable to work across vendors 1
Vendors can do OSS pre-integration – reduce OSS integration time & cost. 4
Managed Open Source: PSI is baby sitter without lock-in 2 3
Operators can innovate services based on abstract service element

9. What is OPEN-O project?

10. 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

11. 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

12. Relationship with other standard bodies
Customer Portal/BSS
(E2E Service= VPN+ VAS + Cloud)
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
Restful API
OPEN-O
Cross domain orchestration
SDNO
NFVO
Tacker…
G-VNFM
WAN SBI
VAS SBI
OPEN Cord
EMS
VNF
S-VNFM
OpenStack
EMS
Controller
vFW,vLB,vCPE,vBNG, vEPC…)
Service provider
Public cloud
Legacy network
SDN network
NFVI
VIM

13. 2016 OPEN-O Event Plan Feb. March April May July Sep. Oct.- Dec.
Speech & Demo
on ONS
OPEN-O 1st
Hackfests
OPEN-O 1st release
Feb.
March
April
May
July
Sep.
Oct.- Dec.
Time to declare on May
MWC Intent
Announcement
Official Founding
OPEN-O 2nd Hackfests
OPEN-O
1st Summit

14. Thank you!