Reference Material

Jira
server ONAP JIRA
columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId 425b2b0a-557c-3c0c-b515-579789cceedb
key CPS-333
Jira
server ONAP JIRA
serverId 425b2b0a-557c-3c0c-b515-579789cceedb
key REQ-717
Release Planning: Istanbul
https://wiki.onap.org/download/attachments/93006150/CPS-NCMP-Design.pptx?version=1&modificationDate=1614348138000&api=v2

...

Priorities & Scope for Istanbul Release

Priority	Description	Notes	Istanbul commitment
1	Publish and Share NCMP Rest interface proposal	detailed for Istanbul scope, general structure only for functionality related to later releases
2	Publish and Share DMI Plugin Rest interface proposal	detailed for Istanbul scope, general structure only for functionality related to later releases
3	Register a DMI Plugin
4	Initial Inventory (semi hardcoded)
5	Inventory Changes (add & remove cm handle)
6	Model discovery (get and store model for a cm-handle)
7	Full (initial) data sync
8	Support dynamic inventory changes (react to DMaapP events)
9	Read operations for single cmHandle with ds = pass-through, synchronous only
10	Create, Update & Delete operations for single cmHandle with ds = pass-through, synchronous only	I don’t expect them to be different at all rom a NCMP/DMI plugin perspective
11	Yang Patch operations for single cmHandle with ds = pass-through, synchronous only		Stretch
12	Retrieve list of modules (names) for a cmHandle		Stretch
13	Support yang-date+json output for all datastores		Stretch
14	Implement -async option for CRUD and Patch operations		Out of Scope
15	Support multiple cmHandles in a single call (bulk)		Out of Scope
16	Support all cmHandles in a single call?		Out of Scope
17	Support ds = operation-running for read and query operations		Out of Scope
18	Support yang-data+json output format for ds = operational running		Out of Scope

...