Interface to External Controllers and SD-WAN Use Case SD-WAN Use Case Team

Contributors: Supporting Companies Contributing Members Evgeniy Zhukov Nagarajan, Ramesh A. Sharma, Anurag Y.

Agenda Enhance ONAP platform capabilities for support of external controllers such as sd-wan systems Controller artefacts on-boarded into ONAP, and ONAP configures them to the level they are ready to provision and manage services. ONAP provisions and monitor the e2e service SD-WAN API between Controller and ONAP Administrate SD-WAN Controller itself, and its client services. Demonstrate SD-WAN vendor neutralization on Mediation layer. Accommodation emerging Industry standards for SD-WAN Solution, like 5G, SDN, NFV, Slicing, LSO and other concepts. SD-WAN Controller implementation Options Can be developed from the scratch by ONAP Community Can be based on existing SD-WAN Vendor product (Interest from Versa) Can be combination of above A B C

ONAP Platform Enhancements For External Controller

General Business Drivers Integration of ONAP to external “controllers” is motivated by need to interface to domain specific systems to provide end2end automation for fulfilment and assurance SD-WAN systems such as Versa, Velocloud, Viptela and Nuage SD-Access such as virtual OLT hardware abstraction (VOLTHA) proposed by att Geographic or operating group specific systems such as at China Telecom, and Vodafone Requires enhancement to ONAP Platform as described on Wiki Page and captured in release 2 functional requirements priority list

ONAP Platform Requirements R1: Lifecycle Management (LCM) for External Controller - ONAP to manage the lifecycle of the external controller as a set of VNFs itself R1.1: Controller Registration in ESR and update AAI with controller URI R1.2: Create resource template for controller VNFs using vnf sdk/ design studio R2: External controller resource-facing service Onboarding R2.1: SDC should support definition/import of service provided by external controller For eg. SDWAN branches and virtual links connecting them (as a black box TOSCA template to be nested/combined with other services per R2.3) R2.2: Should support LCM for services provided by external controllers Create the workflow engine script which SO will execute. R2.3: SDC should support designing services supported by native ONAP and external controller provided services Eg., Combining SD-WAN services with Firewall, WAN optimizer etc., 3rd party VNFs

ONAP Requirements R3: Service Fulfilment R3.1: Instantiate the service provided by external controller from VID R3.2: SO shall decompose the service template into parts to be completed by external controller vs native ONAP components and invoke the appropriate LCM workflow R3.3: SO will interact with AAI and it will locate the external controller for the service and its URI R3.5: Invoke the external controller via external controller adapter R4: External Controller Adaptor R4.1: Should support generic/standard APIs for interaction with underlying external controller - MEF Presto interface standards are candidate for standard APIs

ONAP Requirements R5: AAI - Federated Inventory R5.1: Shall support storing of metadata only for service and fetch detailed information from underlying controller as needed R5.2: Stores the external controller information as registered via ESR R6: DCAE R6.1: Collection of metrics and events from external controller as relevant to the service health monitoring R6.2: HOLMES to support correlation of events and metrics between external controller services and native ONAP services depending on the e2e service components

ONAP Requirements R7: CLAMP R7.1: CLAMP should support template for closed loop assurance of external controller services

SD-WAN API between Controller and ONAP

SD-WAN API and Functional Architecture ONAP SD-WAN Services - Context Slice SD-WAN Slice NBI: SWAPI Mediation Layer HA Bootstrap Service Topology Service Connectivity Service Security Service Notification Service SDWAN Controller SBI: NetConf SDWAN CPE SD-WAN Controller not need recursion with other SD-WAN Controllers

OSS/BSS/GUI ONAP NB API MPLS/INTERNET SDWAN Operations ONAP NB API Portal (GUI/CLI) Dashboard OA&M (VID) External Data Movement & APIs A&AI Service Orchestration Domain Service Descriptors Domain Service Descriptors ESR Design-time Common Service SDC DMaaP Auth. Microservice Bus … VNF SDK Policy DCAE Alarm Correlation (Holmes) … Multi-VIM/ Cloud SDN NFV Other Controllers CLAMP Cloud & WAN OpenStack VMware RackSpace Azure ...... SD-WAN Overlay Systems Alarms/Events 3rd Party/ONAP Component Based SDWAN Systems Analytics Manager Controller REST APIs for configuration MPLS INTERNET BRANCH1 BRANCH2 Overlay IPSEC/VXLAN SD-WAN VNF Underlay MPLS/INTERNET SD-WAN VNF

Bootstrap Operation 0b 0a Admin configures Address Controller S/N CPE FQDN Controller (XML) 0b Day0 Configuration for CPE 0a CPE Redirect Server Controller OSS Address Controller Enables zero touch discovery and onboarding of the CPE device

Connectivity Services ISP1 ISP2

Topology Services

Notification Services SO/SSP Netconf IPFIX Syslog SNMP Delay Jitter Bw Loss TWAMP BFD Controller

SD-WAN Controller implementation

SD-WAN Controller implementation Options (TBD) SD-WAN system typically of following components SD-WAN Manager: Provisioning of SD-WAN services on vCPE SD-WAN Controller: BGP based route reflector for route information propogation SD-WAN Analytics (optional): System for metrics and events from vCPE SD-WAN pBG: Physical CPE server for hosting vBG (option) Implementation Options for components Developed from the scratch by ONAP Community Developed based on existing SD-WAN Vendor product (Interest from Versa) Can be combination of above

Thanks