CPS R11 Release Planning
Overview
Project Name | Enter the name of the project |
|---|---|
Target Release Name | Kohn |
Project Lifecycle State | Incubation |
Participating Companies | Bell Canada, Ericsson, Wipro |
Scope
What is this release trying to address?
Further integrate CPS into ONAP architecture through additional components and interfaces such as
Extend Sync to include data sync and maintaining sync state
AAI integration
Read access to cached data (datastore ncmp-datastores:operational)
Minimum Viable Product
N/A
Requirements
Priority legend | Committent Legend | ||||||||||
Preliminary | Fixed | In Progress | Paused | Completed | De-scoped | Delivered | Committed | Study/Investigation | Partial Delivery | De-scoped | |
ONAP Best Practices (Global Requirements)
ONAP Requirement | Notes | CPS- Jira(s) |
|---|---|---|
Aiming for gold!
| ||
CPS-CORE / CPS-NCMP Requirements
Kohn | Component(s) | Description | Notes | Principle Point of Contact | Jira(s) | |||
|---|---|---|---|---|---|---|---|---|
| 1 | 1 | CPS-NCMP | NCMP should publish notifications for any newly added (once the modules are synced) or deleted cm handles. | Includes implementation of state handling (state persistence) as far as applicable as defined by #7 above | @Priyank Maheshwari | https://lf-onap.atlassian.net/browse/CPS-858 https://lf-onap.atlassian.net/browse/CPS-872 https://lf-onap.atlassian.net/browse/CPS-874https://lf-onap.atlassian.net/browse/CPS-875https://lf-onap.atlassian.net/browse/CPS-876https://lf-onap.atlassian.net/browse/CPS-877https://lf-onap.atlassian.net/browse/CPS-878https://lf-onap.atlassian.net/browse/CPS-909 https://lf-onap.atlassian.net/browse/CPS-977https://lf-onap.atlassian.net/browse/CPS-1015 https://lf-onap.atlassian.net/browse/CPS-1034https://lf-onap.atlassian.net/browse/CPS-1045 https://lf-onap.atlassian.net/browse/CPS-1046https://lf-onap.atlassian.net/browse/CPS-1076https://lf-onap.atlassian.net/browse/CPS-1100https://lf-onap.atlassian.net/browse/CPS-1102https://lf-onap.atlassian.net/browse/CPS-1101https://lf-onap.atlassian.net/browse/CPS-1099https://lf-onap.atlassian.net/browse/CPS-1120https://lf-onap.atlassian.net/browse/CPS-1104 https://lf-onap.atlassian.net/browse/CPS-1162https://lf-onap.atlassian.net/browse/CPS-1163https://lf-onap.atlassian.net/browse/CPS-1165https://lf-onap.atlassian.net/browse/CPS-1167 | ||
| 2 | 2 | CPS-NCMP | Support public CM handle properties | Basic support for public properties + query capability | @Dylan Byrne | https://lf-onap.atlassian.net/browse/CPS-677https://lf-onap.atlassian.net/browse/CPS-817https://lf-onap.atlassian.net/browse/CPS-837https://lf-onap.atlassian.net/browse/CPS-731 | ||
| 3 | 3 | CPS-NCMP | Implement -async option for CRUD and Patch operations (for one CM-Handle) | 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. | @Sourabh Sourabh | https://lf-onap.atlassian.net/browse/CPS-821https://lf-onap.atlassian.net/browse/CPS-828https://lf-onap.atlassian.net/browse/CPS-829https://lf-onap.atlassian.net/browse/CPS-830https://lf-onap.atlassian.net/browse/CPS-832 | ||
| 4 | 4 | https://lf-onap.atlassian.net/browse/REQ-1281Requirement | CPS-NCMP | Support | See CPS-391 page for details about supported operations and combinations. | @Sourabh Sourabh | https://lf-onap.atlassian.net/browse/CPS-870https://lf-onap.atlassian.net/browse/CPS-996https://lf-onap.atlassian.net/browse/CPS-999 https://lf-onap.atlassian.net/browse/CPS-1014https://lf-onap.atlassian.net/browse/CPS-1000https://lf-onap.atlassian.net/browse/CPS-1001https://lf-onap.atlassian.net/browse/CPS-1002https://lf-onap.atlassian.net/browse/CPS-1003 https://lf-onap.atlassian.net/browse/CPS-1119https://lf-onap.atlassian.net/browse/CPS-1164 | |
| 5 | 5 | CPS-NCMP | Support retrieval of YANG module sources for CM handle on the NCMP interface | @Sourabh Sourabh | ||||
| 6 | 6 | CPS-NCMP | DMI Audit | @Toine Siebelink | https://lf-onap.atlassian.net/browse/CPS-1136 https://lf-onap.atlassian.net/browse/CPS-1236 | |||
| 7 | 7 | CPS-NCMP | [investigation/spec] CM data notifications from NCMP to applications including subscriptions | Includes definition of notification and payload format | @kieran mccarthy | https://lf-onap.atlassian.net/browse/CPS-1065https://lf-onap.atlassian.net/browse/CPS-1259 | ||
| 8 | 8 | CPS-NCMP | Implementation of CM data notifications forwarded by NCMP from DMI to application | @Priyank Maheshwari | https://lf-onap.atlassian.net/browse/CPS-1145https://lf-onap.atlassian.net/browse/CPS-1166 | |||
| 9 | 9 | CPS-NCMP | Explicit (initial) data-sync for a CM handle (extend model-sync delivered in Istanbul) | Triggered by client using REST endpoint on NCMP. Note: This item includes extended support for datastores to access the synced data. | @Sourabh Sourabh | https://lf-onap.atlassian.net/browse/CPS-1133https://lf-onap.atlassian.net/browse/CPS-1168 | ||
| 10 | 10 | https://lf-onap.atlassian.net/browse/REQ-1281Requirement | CPS-NCMP | Support update of cached data through a message driven solution | Need to investigate if DMaap or new Kafka/Strimzi message bus should be used | |||
| 11 | 11 | CPS-NCMP | Registration Performance | NCMP shall register new cmhandles (to READY state) at a rate of 11 cmhandles/second (assumes no dmi-plugin delays, assumes 180 modules per cmhandle with 95% module overlap between cmhandles, assumes cache disabled). Treat this as a black box requirement. May mean underlying requirement to have multiple instances, memory requirement etc. Focus right now is 23.Q1 timeframe. | @Sourabh Sourabh | https://lf-onap.atlassian.net/browse/CPS-1172 https://lf-onap.atlassian.net/browse/CPS-1126https://lf-onap.atlassian.net/browse/CPS-1275https://lf-onap.atlassian.net/browse/CPS-1267 | ||
| 12 | 12 | CPS | Data Read Performance | |||||
| 13 | CPS-NCMP | Deletion Performance | NCMP shall delete/remove cmhandles (to DELETING state) at a rate of 50 cmhandles/second with cache disabled (assumes no dmi-plugin delays, assumes 180 modules per cmhandle with 95% module overlap between cmhandles) | |||||
| 14 | CPS-NCMP | Invoke YANG modelled action | Always on operational datastore. Supported for nmcp:passthrough-operational and if executed against ncmp:operational then it is always forwarded to dmi plugin. Is there another story for forwarding to be included as a dependency? Always run as async request. Is this dependent on CPS-1127 - see spin-off user stories table below this on. | |||||
| 15 | CPS-NCMP | Enhanced query support | Currently the passthrough has an 'option' parameter to do a scoped query. Propose to support this in non-passthrough so it is promoted to a fully supported option, e.g. {ncmp-root}/ncmp/v1/ch/335ff/data/ds/ncmp-datastore:passthrough-operational? | |||||
| 16 | CPS_Core / CPS-NCMP | Update YANG schema-set for CM handle without removing and adding it | Cached data is not in scope. Need to specify orphan handling of YANG modules. Needed for node upgrade scenario. | |||||
| 17 | CPS-NCMP | Retrieve single module resource | /v1/ch/{cm-handle}/modules/definitions/{moduleName} | |||||
| 18 | CPS-Core / CPS-NCMP | Existing CPS-path based queries across all CM handles for cached data | Look to define the interface specification for this only. (but best way is to implement for operational/cached data to determine any output formatting issues) | |||||
| 19 | CPS-Core / | Access control for public interfaces (NCMP, CPS-Core, DMI?) | ||||||
| 20 | CPS-NCMP | Fine-grained cache configuration | ||||||
| 21 | CPS-NCMP | Send notification for updated CM handle metadata (public CM handle properties or YANG modules) | ||||||
| 22 | CPS-Core / | Support for HTTPS and authentication
| ||||||
| 23 | TBC | CPS-NCMP | Support | 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. | ||||
| 24 | TBC | CPS-Core / | Support | |||||
| 25 | TBC | CPS-Core | Send notifications on write operation in | |||||
| 26 | CPS-Core / | Support for list as top level data node | https://lf-onap.atlassian.net/browse/CPS-491 https://lf-onap.atlassian.net/browse/CPS-765https://lf-onap.atlassian.net/browse/CPS-766https://lf-onap.atlassian.net/browse/CPS-767 | |||||
| 27 | CPS-Core / | Support for multiple top-elements from different modules in one CM handle/anchor | ||||||
| 28 | CPS-Core / | schema-set update for CM handle with cached data present | Need to address case with incompatible model changes. | |||||
| 29 | (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) | https://lf-onap.atlassian.net/browse/CPS-392https://lf-onap.atlassian.net/browse/CPS-393 | ||||
| 30 | CPS-NCMP | Automatic (optional) Data Sync | Metadata (per cmHandle) controls whether this will happen or not | |||||
| 31 |