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. Ensure all (CPS-Core) Read operations are mirrored
2. Remove/migrate? 'hardcoded generic models used in H release"
3. Spike API for Update and Delete Operations
   1. consider 'bypass' option

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

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-since mapping in yang modelled CPS data table.
   1. include additional data (key-value pars as provided by dmi-service)
2. Dmi manager is to select the dmi instance at runtime for cm handle for a northbound (write) request
   

1. create new module for dmi-registry
2. create yang-model (ncpncmp-dmi-regsitryregistry) in cps repository for cm-handle->dmi-service mappingpluginmapping. To store relations between cm-handle (anchor) and dmi-service plugin (instances)
3. Create anchor with model from step 2 in new (ncmp-admin) dataspace?!
   (once upon deployment)
4. create API to
   1. create new dmi-service plugin entry during registration
5. create API to
   1. Register cm-handle->dmi-service plugin entry when new cm-handle
   2. Get dmi-service plugin for given cm-handle
   3. Delete cm-handle->dmi-service plugin registration
   4. Delete dmi-service plugin ? TBC

1. separate stories for data and model.

Common standard (REST and Java?) interface for extensibility

create dmi service for pluginfor onap. For production its responsibility of admin to provide instance of dmi. This story is mainly for testing purpose. 

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
2. dmi plugin instance (onap-dmi) have sdnc connector to access sdnc.
3. call get/post/put/delete towards restconf interface (forward northbound write requests)

1. Defined and Agree common (java?) Interface
2. create module dmi-onap-serviceplugin Rest and Impl modules
   1. create sub-module dmi-notification-handler
   2. create sub-module dmi-adapters
   3. create sub-module dmi-rest and dmi-serviceplugin
3. create infra for separate spring boot application and docker image for dmi-serviceplugin

1. extract dmi-instance plugin into separate container consensus on rest interface is needed.rename dmi-instance->dmi-service

1. enhance ncmp-cps interface (need to identify).