Page History

create rest interface on northbound for GET/POST/PUT/DELETE to access yang data.
Note. Currently driven by "E2E Network Slicing" Use Case mix of CPS-CORE and NCMP Interface

1. interfaces for yang data are: operational, intended, pass-through (selection can be done by parameter)

2. check with netconf-sim if current nw slicing yang model can be imported including its imports.

Create  dmi-registry. Data Model Inventory Interface (DMI)

'Internal service' no public Java or REST API

responsibilities are

1. Store & retrieve cm-handle/dmi-plugin mapping in yang modelled CPS data table.
   1. include additional data (key-value pars as provided by dmi-Plugin)
2. Dmi manager is to select the dmi instance at runtime for cm handle for a northbound (write) request
   

Common standard (REST and Java?) interface for extensibility

create dmi plugin for onap. For production its responsibility of admin to provide instance of dmi. 

1. Define and agree DMI REST Interface (Ericsson will provide output internal study)
2. Implement Plugin Registration (DMI Plugin Side)
3. create module dmi-onap-plugin Rest and Impl modules. Suggestion (TBC):
   1. sub-module dmi-notification-handler
   2. sub-module dmi-rest
   3. sub-module dmi-plugin
4. create infra for separate spring boot application and docker image for dmi-plugin

1. extract dmi-plugin into separate container consensus on rest interface is needed.

1. At first, on A&AI change event over DMaap, create mapping for cm-handle and dmi instance and sync yang model and data.
   1.  Filter (register) only yang modelled xnf instances's cm-handle, based on event header information of Node

1. MVP: hard-coded inventory list
2. Spike A&AI inventory list
3. Spike A&AI event subscription & filtering

1. Spike SDNC Interface for Model Retrieval

1. dmi plugin instance (onap-dmi) have sdnc connector to access sdnc.
2. call get/post/put/delete towards restconf interface (forward northbound write requests)

1. Spike SDNC Interface for CRUD Operations