| Priority | Description | Notes | Jakarta commitment | Jira(s) |
|---|
| 1 | Retrieve list of modules (names) for a CM handle | Used by applications to get cached information from NCMP about models | Delivered in Istanbul | | Jira |
|---|
| server | ONAP Jira |
|---|
| serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
|---|
| key | CPS-485 |
|---|
|
|
| 2 | Support ncmp-datastores:passthrough-running for read use-case (single CM handle, synchronous only) | Need more details planning and prioritization for use-case not already supported list in this table : CPS-391Spike: Define and Agree NCMP REST Interface#Datastore,PathsandFormatCombinationsforReadOperations | Delivered in Istanbul, just pending Demos | | Jira |
|---|
| server | ONAP Jira |
|---|
| serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
|---|
| key | CPS-615 |
|---|
|
| Jira |
|---|
| server | ONAP Jira |
|---|
| serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
|---|
| key | CPS-646 |
|---|
|
|
| 3 | Separate NCMP-DMI interface from northbound facing 'client' interface | | Committed | | Jira |
|---|
| server | ONAP Jira |
|---|
| serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
|---|
| key | CPS-645 |
|---|
|
|
| 4 | Retrieve cm-handles that have a given list modules |
| Committed | | Jira |
|---|
| server | ONAP Jira |
|---|
| serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
|---|
| key | CPS-644 |
|---|
|
|
| 5 | Support ncmp-datastores:passthrough-running for write use-case (single CM handle, synchronous only) | Replace, Delete & Patch use-cases (#2, #3, #4) in : CPS-391Spike: Define and Agree NCMP REST Interface#Datastore,PathsandFormatCombinationsforWriteOperations | Committed | | Jira |
|---|
| server | ONAP Jira |
|---|
| serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
|---|
| key | CPS-636 |
|---|
|
| Jira |
|---|
| server | ONAP Jira |
|---|
| serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
|---|
| key | CPS-637 |
|---|
|
| Jira |
|---|
| server | ONAP Jira |
|---|
| serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
|---|
| key | CPS-638 |
|---|
|
| Jira |
|---|
| server | ONAP Jira |
|---|
| serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
|---|
| key | CPS-639 |
|---|
|
| Jira |
|---|
| server | ONAP Jira |
|---|
| serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
|---|
| key | CPS-640 |
|---|
|
| Jira |
|---|
| server | ONAP Jira |
|---|
| serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
|---|
| key | CPS-641 |
|---|
|
|
| 6 | Support ncmp-datastores:operational for reading data (single CM handle, synchronous only) | See CPS-391 page for details about supported operations and combinations. Note: There can be some overlap between work items for #5, #6, #11 and #12. Note: This item doesn't include accessing cached data as data sync is not available yet. |
| | Jira |
|---|
| server | ONAP JIRA |
|---|
| serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
|---|
| key | CPS-382 |
|---|
|
|
| 7 | Support ncmp-datastores:running for reading and writing data (single CM handle, synchronous only) | See CPS-391 page for details about supported operations and combinations. Note: There can be some overlap between work items for #5, #6, #11 and #12. |
|
|
| 8 | Support for list as top level data node |
|
| | Jira |
|---|
| server | ONAP Jira |
|---|
| serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
|---|
| key | CPS-491 |
|---|
|
|
| 9 | Support for multiple roots from different modules in one CM handle/anchor |
|
| | Jira |
|---|
| server | ONAP Jira |
|---|
| serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
|---|
| key | CPS-341 |
|---|
|
|
| 10 | Support public CM handle properties |
|
| | Jira |
|---|
| server | ONAP Jira |
|---|
| serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
|---|
| key | CPS-677 |
|---|
|
|
| 11 | Explicit (initial) data-sync for a CM handle (extend model-sync started in step #8) | Triggered by client using REST endpoint on NCMP. Note: This item includes extended support for datastores to access the synced data. |
| | Jira |
|---|
| server | ONAP Jira |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
|---|
| key | CPS-507 |
|---|
|
|
| 12 | Implement -async option for CRUD and Patch operations |
|
|
|
| 13 | Update YANG modules for CM handle without removing and adding it |
|
|
|
| 14 | NCMP should publish notifications for any newly added or deleted cmhandles, or updated metadata (public CM handle properties or YANG modules) | Note: Update support depends on items #10 and #13 |
|
|
| 15 | Support dynamic inventory changes (ONAP DMI Plugin) | React to events from AAI sent over DMaaP, in turn using Inventory API for updates Possible in a generic way or it can also listen to similar events sent by SDN-R (as suggested by Ahila P) |
| | Jira |
|---|
| server | ONAP JIRA |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
|---|
| key | CPS-392 |
|---|
|
| Jira |
|---|
| server | ONAP JIRA |
|---|
| serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
|---|
| key | CPS-393 |
|---|
|
|
| 16 | Automatic (optional) Data Sync | Metadata (per cmHandle) controls whether this will happen or not |
|
|
| 17 | Support multiple cmHandles in a single call (bulk) |
|
|
|
| 18 | Support all cmHandles in a single call? |
|
|
|
| 19 | Invoke YANG modelled RPC or action |
|
|
|
| 20 | Access control for public interfaces (NCMP, CPS-Core, DMI?) |
|
|
|
