...
| 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 | Committed | |
| 2 | Publish and Share DMI Plugin Rest interface proposal | detailed for Istanbul scope, general structure only for functionality related to later releases | Committed | |
| 3 | Register a DMI Plugin (NCMP) | sends an event with initial inventory (TBC) | Committed | |
| 4 | Initial Inventory (semi hardcoded e.g. hidden rest endpoint or some kind of properties file, ONAP only) | Committed | ||
| 5 | Read operations for single cmHandle, synchronous only | using 'pass-through' scenario (default on no data present for cm-handle) In I timeframe ncmp will support the following datastore parameters
| Committed | |
| 6 | Create, Update & Delete operations for single cmHandle , synchronous only (fall back to plugin - this means your not specifying any datastore and there is no cache) | using 'pass-through' scenario (default on no data present for cm-handle) I don’t expect them to be different at all from a NCMP/DMI plugin perspective | Commited | |
| 7 | Inventory Changes define and implement interface to add & remove cm handle | Committed | ||
| 8 | Model discovery (get and store model for a cm-handle) | Committed | ||
| 9 | Retrieve list of modules (names) for a cmHandle - make higher priority | Committed | ||
| 10 | Manual (initial) data sync | Committed | ||
| 11 | Support dynamic inventory changes (ONAP DMU Plugin) | react to DMaapP events using methods define under #5 | Committed | |
| 12 | Read operations for single cmHandle, synchronous only | using 'pass-through' scenario (default on no data present for cm-handle) In I timeframe ncmp will support the following datastore parameters
| Committed | |
| 13 | Create, Update & Delete operations for single cmHandle , synchronous only (fall back to plugin - this means your not specifying any datastore and there is no cache) | using 'pass-through' scenario (default on no data present for cm-handle) I don’t expect them to be different at all from a NCMP/DMI plugin perspective | Stretch | |
| Stretch | ||||
| 12 | 14 | Yang Patch operations for single cmHandle with ds = pass-through, synchronous only | Stretch | |
| 1513 | Retrieve list of cm-handles that have a given module | Stretch | ||
| 1614 | Support yang-date+json output for all datastores | Stretch | ||
| 1715 | Trigger (initial) Data Sync | Metadata (per cmHandle) controls whether this will happen or not | Out of Scope | |
| 1816 | Implement -async option for CRUD and Patch operations | Out of Scope | ||
| 1917 | Support multiple cmHandles in a single call (bulk) | Out of Scope | ||
| 2018 | Support all cmHandles in a single call? | Out of Scope | ||
| 2119 | Support ds = operation-running for read and query operations | Out of Scope | ||
| 2220 | Support yang-data+json output format for ds = operational running | Out of Scope |
...