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. Mirror each CRUD operation
2. Remove/migrate? 'hardcoded generic models used in H release"

Create  dmi-manager. Data Model Inventory (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-instance)
2. Dmi manager is to select the dmi instance at runtime for cm handle for a northbound (write) request
   

1. Set up new module for DMI-manager (agree name)
2. Create yang model for cm-handle and dmi instance identifier mapping
3. CRUD operation on registry

Common standard (REST and Java?) interface for extensibility

create dmi instance for 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 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

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