OPEN- Any service on any network

[email protected] [email protected] 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 Hybrid network needs comprehensive solution

APP/OSS/BSS • Most carriers’ network are hybrid networks (legacy, SDN, and virtual networks) Unified Orchestrator • Super/domain Controllers focus on network resource abstraction and path calculation Super Controller • Orchestration focuses on end to end service and resource orchestration which requires Controller Controller EMS (ONOS) (ODL) VNFM integrate with OSS/BSS and APPs. • Orchestration is key to enable agile Legacy SDN SDN VIM ， Domain Domain A Domain VIMs service across multi-domain multi- layer and multi-vendor Enterprise Solution is insufficient for Telecom For enterprise, Openstack didn’ care Carriers are required to provide about the network connectivity service connectivity and have to take care of the delivery. E2E delivery. Limitation: flat network

VNF VNF VNF VNF Network Network VIM Network VIM VIM A C 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’ requirement

Orchestrator Orchestrator Enterprise NFV ? VNFM NFVI VNFM Telecom NFV

Information Multi-VIMs BSS/OSS Unified API? Model? Support? OPEN-O: From OSS to OSS for Carriers

OSS— Operation Support System OSS— Open Source Software

OSS/BSS/APP 3 Vendor S Service Model definition & OSS mapping & Orchestration Unified Open Source Orchestrator 2 Network /Device EMS EMS EMS Model definition & mapping Multi- Multi- Multi-EMS Device Device Device Controller VNFM/VIM 1 network resource Vendor Vendor Vendor 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

Improved quality, Avoiding market fragmentation 1 6 security, and stability

Avoiding vendor lock-in via 2 interoperable 5 Reduced complexity

3 4 Reduced cost on integration by Faster time to market vendor pre-integration 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:-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 SDN-Orchestrator

• Targets：Virtualized applications, network functions • Targets：Network Connectivity Services • Biz Goal： On boarding, NS LC Mgmt/Resource • Biz Goal: Establishing CONNECTIVITY across access Mgmt & WAN networks • Typical Scenarios： • Typical Scenarios： •VNF Deployment/On-boarding/Scaling/Fault- •Network connectivity mgmt. recovery • 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.. 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.

Global policy Double Closed Loop GS-O long term • Short term (quick response) Data -> Analytics -> Policy -> NFVO Component -> Data Policy short term Local policy SPP SAP actions NFV-O/SDN-O • Long term (slow response) Layered Policy Model Data -> Analytics -> Policy -> Orchestrator -> NFVO Policy Designer Component -> Data Policy Validation Policy Engine collections Analytics predictions Data Modeling Use Case: virtual CPE/CE

Catalogue

Overlay NS Internet Access Service 500M, with Firewall and NAT

Overlay NS Internet Access Service 500M with Firewall and Policy (Enterprise) Cntl

Overlay NS DC Service Chain with vCPE and vNAT (DC)

Underlay Connectivity Underlay NS (complex, multiple CoSs, hierarchical) Virtual CPE/CE Use Case (One Approach) Design Time Global-Service-O (GS-O) Catalogue Overlay NS Overlay NS Topology/Graph

NFV-O (Enterprise) SDN-O NFV-O (DC)

Overlay NS (Enterprise) Underlay NS Overlay NS (DC) Underlay NS DC Underlay NS Underlay NS DC Topology/Graph Topology/Graph Topology/Graph Enterprise Firewall EMS1: pCE vCPE Transport Controller 1: Transport DC Policy Connectivity 1 Transport Control Controller 2: vNAT Connectivity EMS2: TTGW Enterprise SDN Enterprise VIM DC SDN EMSs SDN Controllers DC VIM Controller 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 OPENOPEN--O Carrier Networking Network Controller Data Plane Services Hardware Relationship with other standard bodies

• Open-O plays well with Customer Portal/BSS others (E2E Service= VPN+ VAS + Cloud) • ETSI NFV ISG – Restful API architecture and data Global Service Orchestrator models OPEN-O • Open Source projects - SDNO NFVO OPNFV, Open Stack, Tacker… G-VNFM Open Daylight, ONOS WAN SBI VAS SBI • We will propose an orchestrator project in OPEN Cord EMS OPNFV, OPEN-O will be integrated in OPNFV EMS Controller VNF S-VNFM OpenStack

• We are integrating with vFW,vLB,vC PE,vBNG, Service provider OPENSTACK VNFM vEPC…) (Tacker) Public cloud Legacy SDN NFVI VIM network network Relationship with Openstack

Global Service-O (GS-O) •Customer facing services are provided by Open-O •OpenStack provides ETSI NFV VNFM OPEN-O SDN-O NFV-O and VIM services, not end-to-end orchestration, NFV-O, or connectivity services. Controller VNFM

NE Tacker NE NE VIM 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 OPEN-O OPEN-O 1st on ONS Hackfest release 2016.03.16 2016.06.20 2016.Q4

Feb. March May June July Sep. Oct.- Dec.

2016.02.23 Time to declare later MWC OPEN-O Announcement 1st Summit Getting involved in OPEN-O Join the FUN! • www.openo.org Thank You