| 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 | Might make Istanbul  | | Jira |
|---|
| server | ONAP Jira |
|---|
| serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
|---|
| key | CPS-485 |
|---|
|
|
| 2 | Explicit (initial) data-sync for a CM handle (extend model-sync started in step #8) | Triggered by client using REST endpoint on NCMP |
| | 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 |
|---|
|
|
| 3 | 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. |
| | Jira |
|---|
| server | ONAP JIRA |
|---|
| serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
|---|
| key | CPS-382 |
|---|
|
|
| 4 | 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. |
|
|
| 5 | Support dynamic inventory changes (ONAP DMI Plugin) | React to events from AAI sent over DMaaP, in turn using API in #7 for updates Possible in a generic way o 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 |
|---|
|
|
| 6 | Retrieve list of cm-handles that have a given module |
|
|
|
| 7 | Automatic (optional) Data Sync | Metadata (per cmHandle) controls whether this will happen or not |
|
|
| 8 | Implement -async option for CRUD and Patch operations |
|
|
|
| 9 | Support multiple cmHandles in a single call (bulk) |
|
|
|
| 10 | Support all cmHandles in a single call? |
|
|
|
| 11 | Invoke YANG modelled RPC or action |
|
|
|
