...
| 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 | Committed | |
| 4 | Initial Inventory (semi hardcoded) | Committed | |
| 5 | Inventory Changes (define and implement interface to add & remove cm handle) | Committed | |
| 6 | Model discovery (get and store model for a cm-handle) | Committed | |
| 7 | Full (initial) data sync | Committed | |
| 8 | Support dynamic inventory changes ( | react to DMaapP events )using methods define under #5 | Committed |
| 9 | Read operations for single cmHandle with ds = , synchronous only | using 'pass-through, synchronous only' scenario (default on no data present for cm-handle) | Committed |
| 10 | Create, Update & Delete operations for single cmHandle with ds = , synchronous only | using 'pass-through, synchronous only I ' scenario (default on no data present for cm-handle) I don’t expect them to be different at all rom a NCMP/DMI plugin perspective | Committed |
| 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 | Retrieve list of cm-handles that have a given module | Stretch | |
| 14 | Support yang-date+json output for all datastores | Stretch | |
| 1415 | Implement -async option for CRUD and Patch operations | Out of Scope | |
| 1516 | Support multiple cmHandles in a single call (bulk) | Out of Scope | |
| 1617 | Support all cmHandles in a single call? | Out of Scope | |
| 1718 | Support ds = operation-running for read and query operations | Out of Scope | |
| 1819 | Support yang-data+json output format for ds = operational running | Out of Scope |
...