OPEN-O Unified NFV/SDN Open Source Orchestrator. Hui Deng, China Mobile Chris Donley, Huawei Jim Zemlin, Linux Foundation

Transcription

1 OPEN-O Unified NFV/SDN Open Source Orchestrator Hui Deng, China Mobile Chris Donley, Huawei Jim Zemlin, Linux Foundation

2 Why OPEN-O? Vendor C

3 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

4 SDN Dilemma: No Cross Domain Solution APP/OSS/BSS SDN Orchestrator EMS (Vendor specific) WAN Controller (ONOS) WAN Controller (ODL) Legacy Domain A Domain B Most carriers network is hybrid network which includes legacy and SDN, physical and virtual network SDN orchestration focus on end to end service and resource orchestration, it is key to enable agile operations across multi-domains and multivendors

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

6 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?

7 OPEN-O: From OSS to OSS OSS Operation Support System OSS Open Source Software OSS Vendor S EMS EMS EMS OSS APP APP Network programming interface Open Source Orchestrator Standardized open interface BSS Device Device Device VNFM Controller EMS Vendor X Vendor Y Vendor Z VNF Forwarding HW Legacy OPEN-O is working on the new Orchestrator OSS(Open Source Software) as the Next Generation OSS Foundation for ICT Service Agility

8 China Telecom s use case: CloudVPN End-to-end Orchestration SDN can support layer2 connection cross multiple DCs. Layered Orchestration architecture can provide crossdomain service orchestration and global optimization. vm11 vm12 DC-O DC Controller IDC DC1 Backbone-O WAN controller Backbone NW traffic DC2 DC-O DC Controller IDC vm21 vm22 vm13 vm14ovs/tor VXLAN-GW1PE1 P1 P2 vm23 PE2 VXLAN-GW2 OVS/TORvm24 VXLAN VPN TE VPN VXLAN

9 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

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

11 OPEN-O benefits for industry Simplification, Less customization, faster integration Carrier No vendor-in, more freedom of service innovation Service agility enabled by unified Orchestrator OSS Vendor OPEN Source Orchestrator Equipment Vendor standardized open interface, Lower entry cost Easier using network capability, accelerate innovation APP vendor

12 What is OPEN-O?

13 OPEN-O Mission Statement create a carrier grade framework for NFV orchestration (NFVO and VNFM) and SDN orchestration, implemented and released as open source software, supporting common data models and interoperability across multiple VIMs, upon which end user service providers can build and run robust network services including industry-specific applications in support of cloud, NFV, and SDN environments Keep updating with Governance

14 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 Keep updating according Pre- TSC next Tuesday

15 SDN-O SW Architecture Focused on connectivity for Network Services. Routers and switches, optical devices, access devices, etc. Supports SDN and legacy devices Keep updating according Pre- TSC next Tuesday Can provision and provide assurance directly to devices supporting Netconf/YANG. Also integrates with SDN controllers and EMS/ NMS systems Simplifies and accelerates service creation for network services Layer 2/Layer 3 VPN Bandwidth on demand SDNO Template Mgr SDN Res Mgr Abstract NBI API Model Driven Abstract SBI Cloud VPN WAN VPN

16 NFV-O SW Architecture Provides NFV global management and automatic deployment Common Data Models facilitate service innovation, interoperability Keep updating according Pre- TSC next Tuesday Integrates with multiple VIMs and VNFMs through an abstract driver layer NFVO Model Designer Catalog Abstract NBI API NS/VNF LifeCycle Mgr Workflow Abstract SBI NFV Res Mgr Monitor

17 Join OPEN-O

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

19 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

20 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 MEF - LSO

21 OPEN-O: 1 st unified NFV/SDN Open Source Orchestrator OPEN-O Press Conference on MWC 2016 OPEN-O is driven by operators, supported by mainstream SDN&NFV vendors

22 2016 OPEN-O Event Speech & Demo on ONS OPEN-O 1 st Hackfests OPEN-O 1 st release Feb. March April May June Sep. Oct MWC Intent Announcement Official Founding OPEN-O Summit OPEN-O 2 nd Hackathon

23 All the elements are coming Project moves fast Product is stable Profit is coming

24 Getting involved in OPEN-O Under discussion in community

25 Contact(s):

26 Q&A

27 Thank you!