Orange Contribution to ONAP project Northbound API October

Orange Contribution to ONAP project Northbound API October update Ludovic Robert / Hervé Poupon Orange October 16 th, 1017

Orange contribution to ONAP Project Objectives of the work: § § Through a first API (or small set of APIs ) and simple use case implementation quickly learn lessons about the functional and technical gaps to integrate ONAP to a BSS for fulfilment with minimal customization on BSS Get a first assessment of ONAP/MSO API native capabilities vs TMF API Assumptions: 2 § TMF Open APIs will be leveraging to articulate the and ONAP (Legato LSO) § The initial software architecture will not be optimized and will consist of “façades” on top of existing ONAP APIs, but the implementation will also bring lessons to help refine the best target software architecture § Benefit from support of other teams to perform configurations of ONAP modules which are pre-requisites to Service Orchestrator requests (ie design-time catalogue configuration in SDC) Target date: interface between BSS

When ? Orange contribution to ONAP Project – Drop 1 before e Northbound TMF API Product order mngt component API scope: § BSS triggers a POST service. Order to an API Layer on top of ONAP. § This layer stores service. Order and triggers MSO workflow request to MSO API Request Handler § API Layer is responsible for service. Order status update (retrieving information from ONAP) § ONAP Adaptation. Layer use PATCH operation to update service. Order with delivery milestone § Request POST service. Order Response POST service. Order (id) Request GET service. Order/id Service order mngt component Request delivery. Request (using service. Order format) Request PATCH service. Order Contribution Tech. Scope acknowledge Adaptation Layer Provide FIND/GET Service. Order to BSS Optional features (not in first drop) 3 § Service. Order delivery notification (triggered from API Layer) ONAP nd of ‘ 1 7 PO Response GET service. Order (order detail) SO

When ? Orange contribution to ONAP Project – after drop 1 TBD Northbound TMF API Expand ONAP footprint: Product order mngt component Assess service. Order component integration within ONAP – which means: – Service order are stored in ONAP component ONAP extension ? Request POST service. Order Response POST service. Order (id) Request GET service. Order/id Service order mngt component – Relationship between service order management component and MSO are ‘ONAP-Internal ‘ (what about adaptation layer role ? Could be merged with MSO ? ) 4 Adaptation Layer ? ONAP PO Response GET service. Order (order detail) SO

Orange contribution to ONAP Project – after drop 1 When ? TBD Northbound TMF API Expand API footprint: § Assess capabilities to expose service catalog API from SDC and alignment with TMF API § Leverage service catalog API to improve service Order API dynamic service order build based on catalog information – – 5 Service order API SO Service Catalog API Service inventory API Master catalog provides Product. Spec Service. SPec SDC catalog API provide service. Spec information to build accordingly service. Order/item/relationship § Assess capabilities to expose service inventory. API from AAI and alignment with TMF API § Leverage service inventory API to tackle service management UC (modification of existing service) Service catalog ONAP Service inventory