1. ONAP Interface to External Controllers
Accenture
Netcracker

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

3. General Business Drivers and Rationale
Background
Operator networks are often organized into geographical and/or administrative network domains which in turn consist of multiple service domains or layers (multi-layer, multi-domain concept)
Each service domain is composed of resources, virtual and/or physical, and supported by a domain controller which manages services provided by those resources
Integration of ONAP to external domain controllers is motivated by need to interface to domain specific systems to provide end2end automation for fulfilment and assurance across multi-layer/domains
Examples include
Service Domains/Layers
SD-WAN: Includes resources such as uCPE (physical), SD-WAN VNF and provides services such as site-to-site VPN. Commercial solutions include vendors such as Versa, Viptela, Velocloud, Nuage etc.,.
SD-Access: Includes resources such as OLT and ONU (physical and virtual) and provides access connectivity as a service independent of access type and vendor. Commercial solutions include Nokia, Calix etc.,
SD-Optical: OSI Layer0 Management in WDM Technology Specific Domain, to provide services such as data center interconnect
Geo/Admin Network Domains
Geographic domains: Large operators such as China Telecom have domains consisting of regions/provinces. Each of these regions and associated resources are managed by autonomous domain controllers
Administrative domains: Large operators such as Vodafone have operating groups, eg., Vodafone UK/Germany etc., that are managed autonomously

4. Business Drivers and Rationale
Sample Standards/Industry Initiatives for Domain Abstraction
MEF Presto Emerging standards to define interface between LSO and network domain specific provisioning, monitoring
MEF SD-WAN Presto Interface between LSO/SOF and SD-WAN Controller (Understanding SD-WAN Managed Services: Service Components, MEF LSO Reference Architecture, and Use Cases, see also slide 11)
VOLTHA abstraction for SD-Access covering GPON today but plan to extend to DSL etc., (see also slide 10)
ONF TAPI Interface, standard API defined by the Open Networking Foundation (ONF) that allows a TAPI client, such as a carrier’s orchestration platform or a customer’s application, to retrieve information from and control a domain of transport network equipment controlled by a TAPI server such as a Transport SDN Controller
ONF Multi-Layer Multi-Domain approach:
A Network Domain is defined as a logical collection of resources, either physical or virtual or both, absed typically on geo/admin boundaries
A Service Domain/Layer is defined as a logical sub-collection of resources that provide a service
managed by a domain service controller

5. Implementation Options*
Master-Slave (Option 1): External domain system as a slave orchestration system to master ONAP orchestration
Subtending SDN Controller (Option 2): External controller as a subtending controller to ONAP SDN controller or under multi-VIM as external controller
Set of VNFs (Option 3): External domain system viewed as a set of management and control VNFs under ONAP control
*Based on discussions/proposals with ONAP Community

6. OSS/BSS/GUI ONAP NB API
Option 1
E2E 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
Ext Controller Adapter
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
......
Domain Controller
Alarms/Events
Domain controller may not be singular and can include multiple components depending on resources and services offered by the domain eg.,
Manager – Configuration of resources
Controller – Control Plane, eg., BGP
Analytics – Domain Events/Metrics
MANO – VNF LCM
REST APIs for configuration
Domain Orchestrator
Analytics
Manager
Controller
MANO
SD-WAN
SD-Access
SD-Optical
SD-RAN
SD-DataCenter …

7. OSS/BSS/GUI ONAP NB API
Option 2
E2E 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
......
Domain Controller
Domain controller may not be singular and can include multiple components depending on resources and services offered by the domain eg.,
Manager – Configuration of resources
Controller – Control Plane, eg., BGP
Analytics – Domain Events/Metrics
MANO – VNF LCM
REST APIs for configuration &
Events
Domain Orchestrator
Analytics
Manager
Controller
MANO
SD-WAN
SD-Access
SD-Optical
SD-RAN
SD-DataCenter …

8. OSS/BSS/GUI ONAP NB API
Option 3
E2E 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
......
Domain Controller
Domain controller may not be singular and can include multiple components depending on resources and services offered by the domain eg.,
Manager – Configuration of resources
Controller – Control Plane, eg., BGP
Analytics – Domain Events/Metrics
MANO – VNF LCM
REST APIs for configuration
Domain Orchestrator VNF
Analytics VNF
Manager
VNF
Controller
VNF
MANO
VNF
Alarms/Events
SD-WAN
SD-Access
SD-Optical
SD-RAN
SD-DataCenter …

9. ONAP Requirements for Option 1

10. ONAP Requirements
R1: Lifecycle Management (LCM) for External Controller Components – OOM
R1.1: Controller Registration in ESR and update AAI with controller URI
R1.2: LCM for controller components, ie., bring up controller, monitor, scale as needed
R2: External Controller Resource-facing Service Onboarding - SDC
R2.1: SDC should support definition/import of service provided by external controller
Eg., TOSCA template and/or YANG model of service supported by controller
R2.2: Should support LCM for services provided by external controller
Create the workflow engine script which SO will execute for CRUD operations with respect to the external controller provided service(s)
R2.3: SDC should support designing composite services including services provided by native ONAP and those provided by the external controller

11. ONAP Requirements R3: Service Fulfilment – SO/AAI
R3.1: 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.2: SO will interact with AAI and it will locate the external controller for the service and its URI
R3.3: Invoke the external controller via external controller adapter
R4: External Controller Adaptor – SO/External APIs
R4.1: Should support generic/standard APIs (eg., MEF Presto) for interaction with external controller

12. ONAP Requirements R5: Federated Inventory - AAI
R5.1: Shall support storing of metadata only for external controller service
and fetch detailed information from underlying controller as needed
R5.2: Stores the external controller information as registered via ESR
R6: Service Assurance - 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

13. ONAP Requirements R7: Closed loop control - CLAMP
R7.1: CLAMP should support template for closed loop assurance of external controller services
R8: Policy Federation - Policy
R8.1: Federation of service policies to be enforced by external controller
R8.2: Policy for service assurance of external controller services
R9: Slice Manager – New Component Proposed (Creates and manages domain slices ) in ONAP
R9.1 Connectivity between endpoints;
R9.2 Resources isolation to process traffic where required;
R9.3 Processes for network/operations management and business support.

14. Appendix: Industry Examples of Domain Controllers
And Interface to E2E Service Orchestration

15. VOLTHA Controller Integration to Orchestration
Source: Open Access, Att Presentation to Open Compute Foundation, May 15, 2017

16. MEF LSO and SD-WAN Architecture
LSO Presto Focus Areas