Stake Holder Detailed Requirements
CPS-Core Requirements
NCMP Requirements
Priority legend:
| Preliminary | Fixed | In Progress | Completed | De-scoped |
| Priority | Jakarta Requirement Jira | 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 | CPS-485 - Getting issue details... STATUS | ||
| 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 | |||
| 3 | Separate NCMP-DMI interface from northbound facing 'client' interface |
| Committed | CPS-645 - Getting issue details... STATUS | ||
| 4 | Retrieve cm-handles that have a given list modules | Committed | CPS-644 - Getting issue details... STATUS | |||
| 5 | Allow separate registration of DMIDataPlugin and DmiModelPugin | Committed | CPS-736 - Getting issue details... STATUS | |||
| 6 | 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 | |||
| 7 | 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. | CPS-382 - Getting issue details... STATUS | |||
| 8 | 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. | ||||
| 9 | Support for list as top level data node | CPS-491 - Getting issue details... STATUS | ||||
| 10 | Support for multiple roots from different modules in one CM handle/anchor | CPS-341 - Getting issue details... STATUS | ||||
| 11 | Support public CM handle properties | Basic support for public properties + query capability (separate user story to be defined) | ||||
| 12 | Support retrieval of YANG module sources for CM handle on the NCMP interface | |||||
| 13 | 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. | ||||
| 14 | Implement -async option for CRUD and Patch operations | Required for potentially long running requests Note below to be agreed.,,
Responses always published by NCMP to the client topic. dmi-plugin may publish to NCMP on a local/private topic. Response event payload contains the public topic name. | ||||
| 15 | Update YANG modules for CM handle without removing and adding it | |||||
| 16 | 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 | ||||
| 17 | (ONAP) E2E Slicing Use-Case | 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) | |||
| 18 | Automatic (optional) Data Sync | Metadata (per cmHandle) controls whether this will happen or not | ||||
| 19 | Support multiple cmHandles in a single call (bulk) | |||||
| 20 | Support all cmHandles in a single call? | |||||
| 21 | Invoke YANG modelled RPC or action | |||||
| 22 | Access control for public interfaces (NCMP, CPS-Core, DMI?) |
Temporal DB Requirements
Improvements & Technical Debt (all components)