OSM ONAP Harmonization Solution Agenda OSM ONAP Harmonization

OSM - ONAP Harmonization Solution

Agenda OSM – ONAP Harmonization Prerequisites • • • GSM Meeting and proposed Scenario Modeling Harmonization ONAP modular architecture and ETSI NFV Compliance OSM – ONAP Harmonization Solution Proposal • • Use case: OSM enriched by DCAE and AAI Onboarding of YANG VNFD/NSD models ONAP Common run-time models to be supported by OSM DCAE VES and AAI client API’s

GSMA Meeting Participants ü Deutche Telecom: klaus. martiny@telekom. de; ü Vodafone: abdel. rabi@vodafone. com; tanja. richter 1@vodafone. com; Oscar. Gallego@vodafone. com ü Telefonica: antonio. elizondo@telefonica. com; ü BT: milind. 2. bhagwat@bt. com; ü Telenor: Pal. Gronsund@telenor. com; Stein Hansen <stein. hansen@telenor. com>; ü China Mobile: dengli@chinamobile. com; ü AT&T: mazin@research. att. com; am 803 u@att. com; vb 1946@att. com; ü Verizon: srinivasa. m. kalapala@verizon. com; ü Orange: Vincent Danno <vincent. danno@orange. com>; ü KDDI: koga@kddi. com ü ZTE: Tu. Jia. Sun@zte. com. cn; ü Huawei: louis. lou@huawei. com; denghui 12@huawei. com; ü Amdocs: Alla Goldner

Harmonization Scenario Considered in GSMA Meeting SO DCAE SDC catalogue VNF-D YANG ETSI NFV SOL 004 ETSI NFV SOL 006 VNF-Juju charms Common Run -time DM Onboarding AAI VF-C OSM Model’s Distribution SDC 3 -rd OSMparty Parsers OSM repository OSM-O VCA SDC onboard the OSM YANG model and translate it into an Internal DM SDC distributes applicable models, parsers and other artifacts to • • ONAP components OSM components including YANG VNFD/NSD ONAP RO OSM

F 2 F Dublin Architecture – Modeling Joint Meeting Summary Onboarding/Internal Model • Agree to have one unified model for onboarding descriptors (1), internal model (2) and run-time instance model (3), which are described as separate objects and mapping between them are showed • Describe which model (class) is used for onboarding, for internal output and for run-time use VNF Instance Model Design • • Analyze the current 3 sources of the VNF instance model: AAI implementation, ETSI specs and VFC inventory Starting from building one unified information model for the VNF instance NS/Service Instance Model Design • Have an agreement on the relation between NSD and SD, NS instance and Service instance

OSM - ONAP Harmonization Prerequisites Unified Onboarding Model and Common Extendable Internal IM/DM Design-Time VNF/PNF Dev. Ops Run-Time On-boarding Design TOSCA (SOL 001) Instantiation Operations VF-C Common internal Service Design HEAT PNF (SOL 001) Unified On-boarding TOSCA-X WIP Aligned with ETSI IFA 011 Common Run-time Instance SO/APPC/DCAE/AAI VNF/NS Instance Models YANG (SOL 006) OSM • • A “common language” between VNF vendors and ONAP service designers A “common language” inter-components 6

OSM Support YANG VNF Onboarding, Service Design and artifacts distribution Design-Time VNF/PNF Dev. Ops On-boarding PNF TOSCA (SOL 001) Design Instantiation YANG translation tool Unified model for On-boarding TOSCA-X AAI VNF/NS Instance AAI Client Closed Loop – DCAE VES CSAR with YANG VNFD Operations SO/APPC/DCAE/AAI E 2 E Service SOL 004 packages VNF YANG (SOL 006) Scripts & Data Run-Time • • DCAE VES client OSM A YANG to TOSCA translation tool to be developed in SDC or VNF-SDK SDC design AAI statuses and DCAE events for OSM SDC distribute the AAI client and DCAE VES client to OSM CSAR with YANG VNFD should be also passed to OSM Orchestrator 7

OSM Support OSM inter-working with ONAP DCAE and AAI at run-time Design-Time Run-time States Instantiation Operations SO/APPC/DCAE/AAI E 2 E Service AAI VNF/NS Instance Closed Loop – DCAE VES • Statuses, events, faults AAI Client DCAE VES client OSM At the run-time OSM is updated about status and events modeled at the design time 8

OSM - ONAP Harmonization Solution Highlights Item Current OSM Current ONAP and OSM Tasks Information model for VNFD Aligned with ETSI IFA 011 Data Model for VNF onboarding Aligned with ETSI SOL 006 (YANG) • VNF package onboarding ETSI SOL 004 supporting YANG VNFD ETSI SOL 004 supporting TOSCA VNFD Data Model for Service design 2 Service models are considered • ETSI NFV SOL 001 - NSD • AT&T TOSCA based AID OSM and ONAP cooperation to develop • Common extendable IM/DM for service design • Composite/shared resources support Data Model for Runtime and distribution 2 Run-time models are considered • ETSI NFV SOL 001/SOL 003 • AID based OSM and ONAP cooperation • On developing a common extendable IM/DM for Run-time for VNF/Service Instance SDC adds OSM to a distribution path Run-time components Support of harmonization NA NA OSM to support • AAI client API and DCEA VES client • Data Model for run-time NB/SB API’s • ETSI Or/Or • TMF API SOL 005/TMF API OSM and ONAP cooperation • On developing a common extendable External API • TOSCA - aligned with ETSI SOL 001 HEAT Develop a common TOSCA model for on-boarded VNF/PNF aligned with IFA 011 Develop a translation tool from YANG to TOSCA • OSM work with ONAP SDC or VNF-SDK on tools • Important as an entry point for OSM! Parsing the TOSCA YAML Entry definition file to distinct between TOSCA and YANG VNFD

OSM - ONAP Harmonization Requirements for Discussion Item SDC Tasks (mostly) and other ONAP componenets Note Common IM/DM for onboarded VNFD/PNFD Develop a common TOSCA model for on-boarded VNF/PNF aligned with IFA 011 YANG VNFD onboarding Develop a translation tool from YANG (ETSI SOL 006) to TOSCA (ETSI SOL 001) OSM task VNF package onboarding Parsing the TOSCA YAML Entry definition file to distinct between TOSCA and YANG VNFD ETSI SOL 004 supporting TOSCA VNFD Relevant ETSI contribution is drafted Data Model for Service design Common extendable IM/DM for service design • Composite/shared resources support Two DM’s are considered • ETSI NFV SOL 001 - NSD • AT&T TOSCA based AID Data Model for Run-time and distribution Developing a common extendable IM/DM for Run-time for VNF/Service Instance 2 Run-time models are considered • ETSI NFV SOL 001/SOL 003 • AID based VES and AAI clients Distributing the AAI client API and DCEA VES client based on on-boarded model OSM task Interfaces/API’s for orchestration/management Interconnection of OSM and ONAP Consider NB/SB One option is ONAP External API and API Gateway to support inter-carrier interactions between a carrier that has an ONAP implementation and another carrier that has implemented OSM To be decided • • ETSI Or/Or Common External TMF API

Harmonization Activity in ONAP Proposed Action Items for OSM Data Models for On-boarded VNFD’s – promote ETSI NFV SOL WG tasks • • • YANG data model (ETSI NFV-SOL 006) implementing the IFA 011 Info model for VNFD VNF package (ETSI NFV-SOL 004) to support YANG VNFD and other formats Working with ETSI on enhancing NS modeling for composite resources approach Modeling and other harmonization activity • • Developing a tool for translating YANG to TOSCA Help Developing a common extendable TOSCA based data model for on-boarded VNF descriptors Help Developing a common extendable data model for Run-time OSM integration with ONAP run-time data model (VES and AAI API’s) Create a Task force to coordinate cross communities modeling harmonization

Thank you