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
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.
Why OPEN-O? Vendor C
Is SDN only enough? E2E Unified SDN/NFV Service Orchestrator Virtualization vFW vBRAS vCPE vPE Router vLB SDN Controller Vender specific ONOS ODL OpenStack � DC controller � DomainB GW TOR pCPE BRAS Legacy Domain A MAN Network Data Center Access
Is Controller enough for SDN? APP/OSS/BSS • Most carriers’ network is hybrid network which includes legacy and SDN, and virtual network SDN Orchestrator • Controller focus on network resource abstraction and path calculation • SDN orchestration focus on end to end service and resource Controller Controller EMS (ONOS) (ODL) orchestration and it is key to enable agile service across multi- Legacy SDN SDN domain � multi-layer and multi- Domain Domain B Domain A vendor
Commercialized NFV-O? OSS/BSS SDN-O NB Interface SDN-O interface Commercialized NFVOs Unified IM/ Huawei Ericsson ZTE Nokia Canonical DM vCMM Conductor Cloudband SB Interface HP ADVA Cinena Gigaspaces Multiple VIMs Cloudify Director ESO Blue Planet Option 1: VNFM Option1: SDN Plugin controller plugin Option 2: VNFM Option 2: SDN standard interface VIM SDN standard VNFM Controller interface
Could Enterprise Solution Meet Telecom Expectation? Orchest rator VNFM ? Orchestrator Enterprise Solution NFVI VNFM Telecom Network Information Monitor Multi-VIMs Multi-Site? Unified API? Model? Capability? Support?
OPEN-O: From OSS to OSS OSS— Operation Support System OSS— Open Source Software 3 OSS/BSS/APP Vendor S Service Model definition & OSS Unified Open Source mapping & Orchestration 2 Orchestrator Network /Device Model EMS EMS EMS definition & mapping Multi- Multi-VNFM/ Multi-EMS 1 Device Device Device Controller VIM network resource discovery & abstraction Vendor X Vendor Y Vendor Z • OPEN-O is working on the new Orchestrator OSS(Open Source Software) as the Next Generation OSS Foundation for ICT Service Agility
China Telecom’s use case: CloudVPN Portal APP Website APP Layer BSS CRM/Billing BSS Layer • SDN supports layer2 connection cross multiple DCs. E2E Service O • In this case, it needs to support: Unified M/O-Layer NFVO Orchestrator SDNO • End-to-end overlay between multi-DCs VNFM • Separated overlay between DC and WAN • Traffic steering for different types traffic C-Layer WAN Controller DC Controller • NFVO and VNFM for vCPE and VAS service • Layered Orchestration architecture VNFs provide cross-domain service Backbone NW vm11 IDC orchestration and global optimization. vm21 PE2 vm12 vm22 vm13 VXLAN-GW1 vm23 VXLAN-GW2 PE1 P1 P2 vm14 OVS/TOR vm24 OVS/TOR IDC VPN VPN VLAN VXLAN TE
KT’s use case: Transport SDN End to End Service Orchestrator • SDN controls transport path SDN Controller over multi-vendor devices in a centralized manner Legacy Transport • Orchestrator optimizes MSPP OXC OXC MSPP end-to-end provisioning New Transport PTN PTN
China Mobile’s use case: Orchestration for TICs Core TIC • Two layers of TICs (Telecom NFVO Open-O Mobile-CP Fix-CP Integrated Cloud) are deployed for SDN Controller virtual network services for both fix Edge TIC NFVO and mobile network. Mobile-DP Fix-DP OTN PTN • Orchestrator is used to coordinate PON the service between the two layers. PTN Enterprise Mobile WLAN Residential home
OPEN-O benefits for Industry Agility in services & operations Vendors like plug-in after pre- integration. Operators can plug in/ 5 out easily. Most viable to work 1 across vendors Vendors can do OSS pre-integration 4 – reduce OSS integration time & cost. Managed Open 2 Source: PSI is baby 3 sitter without lock-in Operators can innovate services based on abstract service element
Significance of Orchestrator Similar to IP • IP, as the anchor, decouples Transport Protocols from • Orchestrator, as the anchor, decouples Operator Service L2 Media, facilitate innovations above & below from Vendor infrastructure, facilitate innovations above & below OTT FTP HTTP RTP Google FB Netflix L4 to L7 Operators TCP UDP HSI VPN …… IP Orchestrator L2 Eth ATM EMS Controller VNF/VIM Vendors Device1 Device2 Device N Device1 Device2 Device N If we can, Open source makes 1 single orchestrator becoming possible, rather than many orchestrators from many vendors
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
Use Case Example: eHealth application of SDN + NFV 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 L2 + L3 download the X-Rays 3. Both the doctor and the hospital need to turn on VPN 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
Sequence Diagram for eHealth Use Case Common Cross SDN Ctrl. VNFM Portal SDN-O NFV-O Service Domain-O Driver 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 Service Decompose/Orchestration response Create and deploy vFirewall Service Execute 2: create IPSec VPN(connect to vFirewall) Notes � Service Decompose /Orchestrate Didn’t describe response the interaction create IPSec VPN response between response response orchestration Common
Join OPEN-O
Strategic use of open source software Your value add e s U c i g e t a r t S 80% OSS 29% Average * Best in class * Source: Gartner Group
OPEN-O fills in the gaps between Infra. to OSS Programming Frameworks Application Platforms VM/VIM Managers Containers Operating Systems Virtual Machines OPEN-O Management and Orchestration OPEN-O Carrier Networking Network Controller Data Plane Services Hardware
Relationship with other standard bodies Customer Portal/BSS (E2E Service= VPN+ VAS + Cloud) Restful API • Open-O plays well with others Cross domain orchestration • ETSI NFV ISG – OPEN-O architecture and data SDNO NFVO models Tacker… • Open Source G-VNFM WAN SBI VAS SBI projects - OPNFV, Open Stack, Open Daylight, ONOS OPEN Cord EMS • As upstream open source project, open OpenStack VNF S-VNFM EMS Controller to work with other forums vFW,vLB,vCP E,vBNG, Service provider vEPC…) Public cloud Legacy SDN NFVI VIM network network
OPEN-O: 1 st 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
2016 OPEN-O Event Plan OPEN-O 1 st Speech & Demo OPEN-O 1 st release Hackfests on ONS 2016.09 2016.03.16 2016.05 Feb. March April May July Sep. Oct.- Dec. 2016.02.23 2016.05 2016.07 Time to declare on May MWC Intent OPEN-O Official Founding OPEN-O 2 nd Hackfests Announcement 1 st Summit
Getting involved in OPEN-O • www.openo.org Contact: • rpaik@linuxfoundation.org
Q&A
Thank you!
Recommend
More recommend
