CPS R13 Release Planning
- 1 Montreal Release (M)
- 2 Requirements
- 3 Functionalities
- 3.1.1 User Stories
- 3.2 Other Information
- 3.2.1 Platform Maturity
- 3.2.2 Vendor Neutral
- 3.2.3 Free and Open Source Software
- 3.2.4 Charter Compliance
 | ||
Credit: Arild Vågen. Licensed under Creative Commons Attribution-Share Alike 4.0 International license. | ||
Requirements
Priority legend | |||||
Preliminary | Planned for current ONAP Release | In Progress | Paused/Blocked | Completed | De-scoped |
ONAP Best Practices (Global Requirements) and similar
ONAP Requirement | Notes | CPS- Jira(s) |
|---|---|---|
ONAP script might help us with common quality issues and save reviewing time |
CPS-CORE / CPS-NCMP Requirements
Epic/Component/Owner/Team/Target | Description | Notes | Jira(s) | ||
|---|---|---|---|---|---|
| 1 | 1 |
| Data Write/Read Performance | See also CPS-Core Read & Write (large load) Test Results from Wipro/Fujitsu See Montreal Read/Write Performance for latest performance results (23/08) | |
| 2 | 2 |
|
| Note. These items is now incorporated in https://lf-onap.atlassian.net/browse/CPS-1812 (#7 below) any remaining work items have been move to that epic instead. | Notifications
Subscriptions
|
| 3 | 3 |
| Support update of cached data through a message driven solution. | Receive VES Event and transform it into a 'standard DMI→NCMP events (schema owned by NCMP) |
|
| 4 | 4 |
| Batch (bulk) Operations (Get, Query) | Allow batch operations for NCMP REST and CPS-Core Java Interfaces. All new events will comply to cloudevents. https://lf-onap.atlassian.net/browse/CPS-1717 |
|
| 5 | 5 |
| CM Handle Connectivity Freshness/Staleness | Need to model what staleness is (current CPS only has concept of model-sync state, nothing about connectivity) | |
| 6 | 6 |
| Update YANG schema-set for CM handle using ModuleSetTag |
| |
| 7 | 7 |
| Merge CM data subscriptions in NCMP when forwarding it to DMI | Implementing Data Notifications & Subscription Notifications on a US by US basis | |
| 8 | 8 |
| Access Control for resources to ensure that operators can restrict access control to only those users (human/machines) that are authorized to execute CRUD operations on those resources. | ||
| 9 |
| CM data subscriptions from application to DMI [Part 2]. It includes creating subscription with wildcard cmhandles. | This epic was created to take on additional scope which got added to CPS-1616. | ||
| 10 |
| Event Digest | Additional field to help clients filter CM AVC Events | ||
| 11 |
| AVC Subscription, advance filter | Filter on 'Type' instead of list of CM Handle IDs → 'Type' could be defined as the yang module set containing a specific module (name and version) | ||
| 12 | 12 |
| Support for list as top level data node | ||
| 13 | 13 |
| CPS & NCMP Feature Enhancement for M Release | ||
| 14 | Yet to agree priority | A decision was made to abandon json+problem format | |||
| 15 |
| Spike for documenting Kafka interfaces using AsyncAPI | - Documentation Generation - Code Generation (contract first, stubs) | ||
| 16 |
| Refactor legacy NCMP ASync Response Events to use Cloud Events format | (M) | ||
| 17 | TBC | Support NCMP-CPS upgrade | Currently only custom upgrade is supported. (upon request) Requirement: It shall be possible to upgrade NCMP-CPS from release N-1 to N (without requiring manual intervention/workarounds). N is defined as any release requested by ESH
Technical Debt to be addressed: Liquibase is used in CPS to manage data(upgrades) in CPS Study: Resolve technical debt (mixed data). NCMP Data upgrade. CPS Core need to support model upgrade so that NCMP can use it, | ||
| 18 | TBC | Support multiple identifiers (alternatives for CM Handle ID) | (M) - Not sure. Scope not known yet. | ||
| 19 | Access control for topics which are created by NCMP . | Spike needs to be conducted. | |||
| 20 | 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. KMC : Can we deprioritize - this can be run against passthrough-operational for now. Just have to agree on the API / URL for the action to progress at this stage so that the passthrough-operational form is aligned with final operational form. | |||
| 21 | Enhanced query support (fields) | Currently the passthrough has an 'fields' 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? KMC : Do we support restconf like queries or xpath only? (L) . | |||
| 22 | Enhanced query support (scope) | Currently the passthrough has an 'fields' parameter to do a scoped query. KMC : Do we support restconf like queries or xpath only? (L) | |||
| 23 | TBC | 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 | Support | (S) As per #18 | ||
| 25 | TBC | Support relationships for 'Instance Identifier' | Should be possible to identify a cmhandle using multiple instance identifiers. | ||
| 26 | Retrieve single module resource | /v1/ch/{cm-handle}/modules/definitions/{moduleName} | |||
| 27 | Access control for public interfaces (NCMP, CPS-Core, DMI?) | KMC : What level of access control is there today - both on CPS and NCMP interfaces? | |||
| 28 | Fine-grained cache configuration | ||||
| 29 | Support for HTTPS and authentication
| Validation required whether this is still needed. | |||
| 30 | TBC | Send notifications on write operation in | |||
| 31 | schema-set update for CM handle with cached data present | Need to address case with incompatible model changes. | |||
| 32 | Invoke YANG modelled RPC | Specification required. Rebbot/Reset type of actions on node. | |||
| 33 | DMI Audit for DMI restarts | ||||
| 34 | Fetch a list of cmhandles along with their private properties as response from NCMP. |
Spin-off user stories, yet to be prioritized
Jira | Component(s) | Related Work Item | Description | Notes |
|---|---|---|---|---|
CPS-NCMP | ||||
CPS-NCMP |