OPEN-O Any service on any network denghui@chinamobile.com Christopher.donley@huawei.com
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
Hybrid network needs comprehensive solution EMS APP/OSS/BSS Unified Orchestrator Super Controller Controller (ONOS) Controller (ODL) VNFM 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. Legacy Domain SDN Domain A SDN Domain B VIMs Orchestration is key to enable agile service across multi-domain,multilayer and multi-vendor
Enterprise Solution is insufficient for Telecom For enterprise, Openstack didn t care about the network connectivity service delivery. Limitation: flat network Carriers are required to provide connectivity and have to take care of the E2E delivery. VNF VIM Network VNF VIM VNF VIM Network A Network C VNF VIM Network B Complexity of connectivity service delivery is much higher for telecom than for enterprise Complexity of Telecom VNFs is also much higher than enterprise, such as requirement for 99.999% reliability
Enterprise Solution doesn t meet telecom s requirement NFVI Orchestrator Enterprise NFV VNFM Orchestrator VNFM? Telecom NFV Information Model? BSS/OSS Unified API? Multi-VIMs Support?
OPEN-O: From OSS to OSS for Carriers OSS Operation Support System OSS Open Source Software OSS Vendor S 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 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, along with emerging SDN and NFV Infrastructure.
OPEN-O benefits for Industry Establishment of an open ecosystem Agility in services & operations Avoiding market fragmentation 1 6 Improved quality, security, and stability Avoiding vendor lock-in via interoperable 2 5 Reduced complexity Reduced cost on integration by vendor pre-integration 3 4 Faster time to market
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 Architecture Orchestration Service consists of GS-O/SDN-O/NFV-O and Orchestration Common. GS-O coordinates orchestration across domains. Open-O connects to SDN controllers/vfnm/vim/ems through Drivers. Common Service provides platform service(messaging etc.) Tools consist of model designer &VNF deployment tool. Portal provides GUI mgmt. interface for Open-O.
A Closer Look at OPEN-O GS-O Global Service Orchestrator Targets:E-2-E network service orchestration Biz Goal: Unified service orchestration of Legacy & SDN/NFV network resources under MV circumstance Typical Scenarios: Service LC mgmt. for users/tenants Operation- Service design/deployment/activation/provisioning Maintenance- Close-loop Automation NFV- Orchestrator Targets:Virtualized applications, network functions Biz Goal:NS On boarding, NS LC Mgmt/Resource Mgmt Typical Scenarios: VNF Deployment/On-boarding/Scaling/Faultrecovery SDN-Orchestrator Targets:Network Connectivity Services Biz Goal: Establishing CONNECTIVITY across access & WAN networks Typical Scenarios: Network connectivity mgmt. Traffic Engineering
Orchestration Common: Model Driven Framework Why model-driven? Unified service creation and provisioning process needs a normalized data model, Model driven configuration & management makes system extensible, Model driven framework provides basis for openness of network capability. Highlights: Model conflict detection also provided, both static & dynamic Model DryRun allow validation before service provisioning
Orchestration Common: Analytics and Policy OPEN-O with analytics module and policy module becomes more intelligent. Machine learning methods (e.g. ANN, SVM, logistic regression, etc.) -> Analytics model The analytics module can predict the future situation to interact with the policy module to control / manage the system. Policy SPP SAP Layered Policy Model Policy Designer Policy Validation Policy Engine long term short term predictions GS-O Local policy actions NFV-O/SDN-O Analytics Global policy Data collections Double Closed Loop Short term (quick response) Data -> Analytics -> Policy -> NFVO Component -> Data Long term (slow response) Data -> Analytics -> Policy -> Orchestrator -> NFVO Component -> Data
Modeling Use Case: virtual CPE/CE Catalogue Overlay NS Internet Access Service 500M, with Firewall and NAT Overlay NS (Enterprise) Overlay NS (DC) Underlay NS Internet Access Service 500M with Firewall and Policy Cntl DC Service Chain with vcpe and vnat Underlay Connectivity (complex, multiple CoSs, hierarchical)
Virtual CPE/CE Use Case (One Approach) Design Time Catalogue Global-Service-O (GS-O) Overlay NS Overlay NS Topology/Graph NFV-O (Enterprise) Overlay NS (Enterprise) Underlay NS DC Topology/Graph Firewall Policy Control Enterprise VIM Enterprise Transport Underlay NS Topology/Graph EMS1: pce Controller 1: Connectivity 1 Controller 2: Connectivity n EMS2: TTGW SDN-O Underlay NS Transport vcpe vnat Enterprise SDN Controller EMSs SDN Controllers DC VIM NFV-O (DC) Overlay NS (DC) Underlay NS DC Topology/Graph DC Transport DC SDN Controller
Join OPEN-O
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
Relationship with other standard bodies Open-O plays well with others Customer Portal/BSS (E2E Service= VPN+ VAS + Cloud) ETSI NFV ISG architecture and data models Open Source projects - OPNFV, Open Stack, Open Daylight, ONOS OPEN-O WAN SBI SDNO VAS SBI Restful API Global Service Orchestrator Tacker G-VNFM NFVO We will propose an orchestrator project in OPNFV, OPEN-O will be integrated in OPNFV EMS Controller OPEN Cord EMS VNF S-VNFM OpenStack We are integrating with OPENSTACK VNFM (Tacker) Legacy network SDN network vfw,vlb,vc PE,vBNG, vepc ) NFVI VIM Service provider Public cloud
Relationship with Openstack Global Service-O (GS-O) SDN-O OPEN-O Controller VNFM NFV-O Customer facing services are provided by Open-O OpenStack provides ETSI NFV VNFM and VIM services, not end-to-end orchestration, NFV-O, or connectivity services. NE NE NE VIM Tacker NOVA Neutron Openstack Tacker provides VNF Manager functions Catalog Cinder Swift Basic life-cycle of VNF. Performance and Health monitoring Auto Healing OPNFV/Openstack Nova/Neutron/etc provides VIM service Configuration
2016 OPEN-O Project Roadmap Call for Founding Members until June 1, 2016 Speech & Demo on ONS 2016.03.16 OPEN-O Hackfest 2016.06.20 OPEN-O 1 st release 2016.Q4 Feb. March May June July Sep. 2016.02.23 MWC Announcement Getting involved in OPEN-O Join the FUN! www.openo.org Oct.- Dec. Time to declare later OPEN-O 1 st Summit
Thank You