OPEN-O Unified NFV/SDN Open Source Orchestrator

Transcription

1 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

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 Virtualization Is SDN only enough? vcpe vbras vpe Router vfw vlb SDN Controller Vender specific ONOS ODL OpenStack DC controller DomainB pcpe BRAS Legacy Domain A GW TOR Access MAN Network Data Center

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

6 Commercialized NFV-O? SDN-O OSS/BSS SDN-O interface NB Interface Unified IM/ Canonical DM Option 1: VNFM Plugin Option 2: VNFM standard interface Huawei vcmm HP Director VNFM Commercialized NFVOs Ericsson ADVA ESO ZTE Conductor Cinena Blue Planet VIM Nokia Cloudband Gigaspaces Cloudify SDN Controller SB Interface Multiple VIMs Option1: SDN controller plugin Option 2: SDN standard interface

7 Orchest rator Enterprise Solution NFVI VNFM Could Enterprise Solution Meet Telecom Expectation? Orchestrator VNFM? Telecom Network Information Model? Monitor Capability? Multi-Site? Unified API? Multi-VIMs Support?

8 OPEN-O: From OSS to OSS OSS Operation Support System OSS Open Source Software Vendor S OSS EMS EMS EMS Device Device Device Vendor X Vendor Y Vendor Z Multi- Controller OSS/BSS/APP Unified Open Source Orchestrator Multi-VNFM/ VIM Multi-EMS 3 Service Model definition & mapping & Orchestration 2 Network /Device Model definition & mapping 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

9 China Telecom s use case: CloudVPN APP Layer Portal APP Website SDN supports layer2 connection cross multiple DCs. In this case, it needs to support: End-to-end overlay between multi-dcs Separated overlay between DC and WAN Traffic steering for different types traffic NFVO and VNFM for vcpe and VAS service Layered Orchestration architecture provide cross-domain service orchestration and global optimization. BSS Layer BSS CRM/Billing M/O-Layer Unified Orchestrator Backbone NW E2E Service O NFVO SDNO VNFM C-Layer WAN Controller DC Controller vm11 vm12 IDC PE2 VNFs vm21 vm22 vm13 vm14 OVS/TOR VXLAN-GW1 PE1 P1 P2 vm23 VXLAN-GW2 OVS/TORvm24 IDC VLAN VPN TE VPN VXLAN

10 KT s use case: Transport SDN SDN controls transport path over multi-vendor devices in a centralized manner Orchestrator optimizes end-to-end provisioning Legacy Transport New Transport PTN MSPP End to End Service Orchestrator SDN Controller OXC OXC MSPP PTN

11 China Mobile s use case: Orchestration for TICs Two layers of TICs (Telecom Integrated Cloud) are deployed for virtual network services for both fix and mobile network. Core TIC Mobile-CP Edge TIC Mobile-DP Fix-CP SDN Controller Fix-DP NFVO NFVO Open-O Orchestrator is used to coordinate the service between the two layers. PON OTN PTN PTN Residential home WLAN Enterprise Mobile

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

13 Significance of Orchestrator Similar to IP IP, as the anchor, decouples Transport Protocols from L2 Media, facilitate innovations above & below Orchestrator, as the anchor, decouples Operator Service from Vendor infrastructure, facilitate innovations above & below FTP HTTP RTP TCP UDP IP Eth ATM Device1 Device2 Device N L4 to L7 L2 Google FB Netflix HSI VPN Orchestrator EMS Controller VNF/VIM Device1 Device2 Device N OTT Operators Vendors If we can, Open source makes 1 single orchestrator becoming possible, rather than many orchestrators from many vendors

14 What is OPEN-O project?

15 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

16 End-to-End SDN/NFV Orchestration ETSI NFV MANO compliant Modular and multiplatform Service and Resource Orchestration YANG and TOSCA support OPEN-O SW Architecture

17 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 download the X-Rays 3. Both the doctor and the hospital need to turn on 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 L2 + L3 VPN

18 Sequence Diagram for ehealth Use Case Portal Common Service Cross Domain-O SDN-O NFV-O SDN Ctrl. Driver VNFM Driver Service request(ehealth) Service request(ehealth) API gateway: Service request(ehealth) Service Catalog: Verify Service response response response Decompose Service Service Execute 1: vfirewall Create and Deploy response Create and deploy vfirewall Service Execute 2: create IPSec VPN(connect to vfirewall) response create IPSec VPN Service Decompose/Orchestration Service Decompose /Orchestrate Notes Didn t describe the interaction between orchestration Common

19 Join OPEN-O

20 Strategic use of open source software Your value add Strategic Use 80% OSS 29% Average * Best in class * Source: Gartner Group

21 OPEN-O fills in the gaps between Infra. to OSS Programming Frameworks Application Platforms VM/VIM Managers Containers Operating Systems Virtual Machines Management and Orchestration Carrier Networking Network Controller Data Plane Services Hardware OPEN-O

22 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 As upstream open source project, open to work with other forums OPEN-O EMS Legacy network WAN SBI SDNO Controller SDN network Customer Portal/BSS (E2E Service= VPN+ VAS + Cloud) VAS SBI Restful API OPEN Cord Cross domain orchestration Tacker EMS VNF vfw,vlb,vcp E,vBNG, vepc ) NFVI G-VNFM NFVO S-VNFM VIM OpenStack Service provider Public cloud

23 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

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

25 Getting involved in OPEN-O Contact:

26 Q&A

27 Thank you!