Summit 16: Open-O Mini-Summit - Vision and Update, Deng Hui, Chair, OPEN-O Governing Board, China Mobile

1. OPEN-O Vision and Update
2016 OPEN-O Mini-Summit
June 21, 2016
Deng Hui, China Mobile, Chair, OPEN-O Board (denghui@chinamobile.com)

2. Agenda
 Vision – Why OPEN-O
 Update – We launched on June 2nd, 2016
2

3. • 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 Vision

4. NFV
Unified Orchestration is the Key
MAN NetworkAccess Telecom Cloud Core Telecom CloudpCPE
E2E Unified SDN/NFV Service Orchestrator
NFV
vCPE vBRAS vPE Router vFW vLB
GW
OpenStack
（DC controller
）
TOR
Legacy Domain A
DomainB
Vendor specific ONOS ODL
Core SDN Controller
SDN
OpenStack）
TOR
NFV SDN

5. Open Orchestration
Bridging the Gap between SDN & NFV
5
Compute Storage Network
Hardware Resources
Virtualisation Layer
Virtualised
Infrastructure
Manager(s)
VNF
Manager(s)
VNF 2
OSS/BSS
NFVI
VNF 3VNF 1
Virtual
Compute
Virtual
Storage
Virtual
Network
EMS 2 EMS 3EMS 1
Service, VNF and
Infrastructure Description
Orchestrator
MANO
Infrastructure
Layer
Control
Layer
Application
Layer
SDN Applications
API
Network Services
API
API
Network
Services
ONF SDN ArchitectureETSI NFV Architectural Framework

6. Hybrid network
• Most carriers’ network are hybrid
networks (legacy, SDN, and virtual
networks)
• Super/domain Controllers focus on
network resource abstraction and
path 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
VIMLegacy
Domain
SDN
Domain A
SDN
Domain B
Controller
(ONOS)EMS
APP/OSS/BSS
Super
Controller
Controller
(ODL)
Unified Orchestrator
VNFM
VIMVIMs

7. Enterprise Solution ==> Telecom
Orchestrator
NFVI
Enterprise NFV
Telecom NFV
Information
Model?
BSS/OSS Unified API?
Multi-VIMs
Support?
Orchestrator
VNFM
?VNFM

8. From OSS to OSS
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, emerging SDN and NFV Infrastructure.
OSS
EMS EMS EMS
Device Device Device
Vendor X Vendor Y Vendor Z
Vendor S
Multi- SDN
Controller
Multi-
VNFM/VIM
Multi-EMS
BSS/APP
OPEN-O
Service Model definition &
mapping & Orchestration
Network /Device Model
definition & mapping
Network resource
discovery & abstraction
3
2
1

9. VIM
SDN CtrlVNFM
BSS:
Product Layer
OSS:
Service Layer
Network:
Resource Layer
App/BSS
Portal
(GUI)
VIM
Customer Facing Service Spec
Resource Facing Service Spec
Network Service Spec
PNFs VNFs
Product Spec
Resource Spec SDN CtrlS/G-VNFM
GS-O
Global 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
ETSINFV
Business Layer:
Operation Layer:
Network Layer:
How OPEN-O evolve with BSS/OSS/NMS/EMS
TOSCA
YANG

10. SFC with OPEN-O
①Customer orders an E2E service
②GS-O owns E2E VNFFG
③NFV-O owns local SFCs, and its SFC Engine
instructs VNFM and SDN controller for SFC
deployment
④⑤Multiple VNFMs are employed in
instantiating various VNFs as SFs for a single SFC
⑥SDN Controller instructs the Classifier and
OVS/ToR to set up the rules for Chaining.
GS-O
NFV-O
SDN-Ctrl G-VNFM S-VNFM1
BSS
Customer
SFC Engine
Ctrl Plugin VNFM Plugin
Customer Order❶
VNFFG-Chain❷
VNFFG-Chain❸
Local Chaining❻
Internet
Model Decomposition
Product Specification
Service Specification
S-VNFMm
3rd party VNFs❹ Vendory VNFs❹Vendorx VNFs❹
Classifier OVS/ToR
❺ ❺VNF1 VNF2 ❺ ❺VNFk-1 VNFk VNFn-1 VNFn❺ ❺
SFFs

11. 1st release 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 Controller
Super/D Controller
Access
Controller
OPEN-O
GW
overlay
underlay VLAN MPLS BGP L3VPN
OS
vCPE
OS
vFW
Enterprise
Site
Tenant Cloud
for Enterprise
POP/TIC Edge
G-VNFM1
(Juju/vFW, …)
VIM1
(OS1)
S-VNFM1
(vCPE)
G-VNFM2
(SFC/vVAS)
Neutron
interface
SDN-O NFV-OLegend:
PE2
SPTN
pCPEResidential BRAS DP
TIC Core
MPLSTP L2VPN
PE1
S-VNFM1
(BRAS CP)
SPTN
VLAN SPTN MPLSTP L3VPN

12. OPEN-O A Closer Look
SDN
Driver
VNFM
Drivers
VIM
Drivers
ACCESS/WAN SDN
Controller Drivers
NFV SDN
Controller Drivers
Orchestrator Service
Model Designer
Portal GUI Portal … Test
&
Lab
(for
feature)GS-O
Service
Decomposer
Service
Lifecycle Mgr.
Service
Formation
Abstract NBI
SDN-O
SDN
Res.
Mgr.
Abstract NBI
Abstract SBI
NFV-O
NFV Res. Mgr.
NFV Monitor
NS Lifecycle
Mgr.
Abstract NBI
Abstract SBI
VPN
SDN Lifecycle Mgr.
Traffic
Optimize
VAS
Mgr.
…
SDN
Monitor
Common
Tosca
Lifecycle Mgr.
Framework
Template Mgr.
Model Driven
Framework
Policy Driven
Framework
Common
Res. Mgr
…
Common
Service
HA
Log
Driver Mgr.
…
Micro-Service
Bus
Protocol Stack
Auth.
EMS/NMS
Driver
Parser
NFV
Driver
Workflow
Catalog
VIM
Drivers

13. Key OPEN-O Projects
 GS-O
End-to-End service composition
and orchestration
 NFV-O
 Virtualized network services
 LCM, RM, Monitor, SFC
13
 SDN-O
 SDN-based connectivity service
 legacy Infrastructure
 Common Services
 Building blocks for other modules
 Micro Service Message-bus
 HA, etc.
 Common Tosca
 Parser
 Workflow
 Catalog

14. OPEN-O Status
 Formation, June, 2016
 11 Members
 Growing community:
> 100 Developers committed
 Release 1.0:
Targeted to end of 2016
 OPNFV integration: Planned
 Join today!
www.open-o.org
 For more details:
 Marc Cohn
mcohn@linuxfoundation.org
14
Any Service over Any Network

15. Relationship with other OSS/Standard bodies
 ETSI NFV ISG –
architecture and info
models
 Open Source projects
OPNFV
Open Stack
Open Daylight
ONOS
vFW,vLB,vCP
E,vBNG,
vEPC…)
OPEN-O
WAN SBI VAS SBI
SDNO
Restful API
Customer Portal/BSS
(E2E Service= VPN+ VAS + Cloud)
ControllerEMS VNF
NFVO
G/S-VNFM
(vendor, Juju)
VIM
NFVI
EMS
OpenStack
Global Service Orchestrator
Legacy
network
SDN
network
Service provider
Public cloud
CORD

16. 谢谢
Thank You
www.linuxfoundation.org

17. Eating our own dog-food