CPS 2025 Q3-Q4 Release Planning
2025 Now Closed. Please continue to https://lf-onap.atlassian.net/wiki/spaces/DW/pages/579272722
Requirements
Preliminary | Priority Agreed | Requirement Gathering | In Progress | Pending Integration | Paused/Blocked | Completed | De-scoped |
CPS-CORE / CPS-NCMP Requirements
Epic/Component/Owner/Team/Target | Description | Notes | Jira(s) | |
|---|---|---|---|---|
| 1 | https://lf-onap.atlassian.net/browse/CPS-2081 https://lf-onap.atlassian.net/browse/CPS-2082 https://lf-onap.atlassian.net/browse/CPS-2083
| CPS-Core Feature Enhancement for Oslo Release: Delta Feature | NOTE: Reopened |
|
| 2 | https://lf-onap.atlassian.net/browse/CPS-2690
| Datajobwrite Performance Measurement |
| https://lf-onap.atlassian.net/issues/?jql=parent%20%3D%20CPS-2690 |
| 3 | https://lf-onap.atlassian.net/browse/CPS-2010
|
Requirement Gathering by @Kolawole Adebisi-Adeolokun with Laslo Lang
| NCMP to introduce a qualifier to be used along with the DMI plugin so NCMP can break the request with multiple cm handles into batches based on the DMI plugin and the Qualifier (where qualifier should be EMS name / id).
| |
| 4 | https://lf-onap.atlassian.net/browse/CPS-1992
|
| Implement new NCMP CRUDAQ sync interface aligned with 3GPP API (Read and write use cases) - Wrapper on existing/legacy API Probably not need but to be confirmed: |
|
| 5 | https://lf-onap.atlassian.net/browse/CPS-2166
| Forwarding CM Data Notifications to Topic in Subscription. 250 million CM notifications per day that need to be processed and distributed to ? different topics Need to clarify characteristics requirements as it was mentioned that only a small (single digit?) percentage of notifications will be handled by CPS-NCMP |
Interdependent on - https://lf-onap.atlassian.net/browse/CPS-1812 | https://lf-onap.atlassian.net/issues/?jql=parent%20%3D%20CPS-2166 |
| 6 | https://lf-onap.atlassian.net/browse/CPS-2775
| Move DMI API definition to CPS/NCMP codebase |
| https://lf-onap.atlassian.net/issues/?jql=parent%20%3D%20CPS-2775 |
| 7 | https://lf-onap.atlassian.net/browse/CPS-2876
| NCMP to introduce;
| Additional: Event Schema change to support any old/new values. I.e. make schema more generic using a property map. |
|
| 8 | https://lf-onap.atlassian.net/browse/CPS-2874
| Moving Additional Properties and potentially the State attribute to the top-level object structure Most work ill be migration procedures and rollback | POC carried out showed there are potentially performance benefit if addition properties are moved to the top level object structure for some NCMP use case, see more information PoC Only retrieve parent objects |
|
| 9 | https://lf-onap.atlassian.net/browse/CPS-2521
| Sync Actions Invoke YANG modelled action Invoke YANG modelled RPC, Specification required. Reboot/Reset type of actions on node. Include to the sync one | 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 sync request. Is this dependent on CPS-1127 - see spin-off user stories table below this on. @kieran mccarthy : Can we de-prioritize - 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. (S) - for passthrough. *Spec out before Sept'23. No implementation. Nov 9, 2023 can datajob cover this ?, currently no support for 'actions'. Action name at the end of resourceid. split ticket into, action with and without responses. | https://lf-onap.atlassian.net/issues/?jql=parent%20%3D%20CPS-2521
|
| 10 | https://lf-onap.atlassian.net/browse/CPS-2969
| See https://lf-onap.atlassian.net/wiki/spaces/DW/pages/16521596/CM+Data+Notification+Subscription+LCM+incl.+merge#CMDataNotificationSubscriptionLCM(incl.merge)-Functional Functional Requirement #11 in CPS-E-09e
| Spring (annotation) support this but also require non default Kafka configuration for Tx and enforcing Once-Only with Tx | https://lf-onap.atlassian.net/issues/?jql=parent%20%3D%20CPS-2969 |
| 11 | https://lf-onap.atlassian.net/browse/CPS-2978
|
| Only Add (and forward) ExecutionPolicy Field | https://lf-onap.atlassian.net/issues/?jql=parent%20%3D%20CPS-2978
|
| 12 | https://lf-onap.atlassian.net/browse/CPS-1872
| Fetch a list of cm handles along with their private properties as response from NCMP. |
| https://lf-onap.atlassian.net/issues/?jql=parent%20%3D%20CPS-1872
|
| 13 | https://lf-onap.atlassian.net/browse/CPS-2675
| Revive ONAP DMI Plugin to demo in OAM stack with SDNC etc. |
| https://lf-onap.atlassian.net/issues/?jql=parent%20%3D%20CPS-2675 |
| 14 | https://lf-onap.atlassian.net/browse/CPS-2933
| Introduce an open-source Kubernetes container management system to simplify and standardize the management of CPS and NCMP containers. This will provide a consistent orchestration layer, enabling deployment, scaling, and monitoring whether the containers are hosted directly on physical servers or on virtual machines. | Goal is to have cps-and-ncmp deployment over k8s cluster including the right resources (should be aligned with stakeholders) to mimic their deployment. | |
| 15 | https://lf-onap.atlassian.net/browse/CPS-1345
| 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, Nov 8, 2023 Liquibase is used in CPS to manage data(upgrades) - Now available.
(XL) - Scope needs to be defined. Risk is scope not identified, efforts might increase. |
|
| 16 | https://lf-onap.atlassian.net/browse/CPS-1704
| Refactor legacy NCMP ASync Response Events to use Cloud Events format
| (M) TBC |
|
| 17 | https://lf-onap.atlassian.net/browse/CPS-2233
| CM Subscription with DME interface
|
Newly Added | |
| 18 | https://lf-onap.atlassian.net/browse/CPS-1915
|
| TBAC Study still ongoing, schedule an internal meeting to go through study doc, until sidecar is well define and implemented cps can't do nothing. Sidecar should specify the interfaces.
| |
| 19 | https://lf-onap.atlassian.net/browse/CPS-1781
| CM data subscriptions from application to DMI [Part 2]. For all cmhandle (general) | This epic was created to take on additional scope which got added to CPS-1616.
| |
| 20 | https://lf-onap.atlassian.net/browse/CPS-1965
| AVC Subscription, advance filter. Part 2 of cmhandles It includes creating subscription with patternmatch cmhandles. | 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) |
|
| 21 |
| Event Digest | Additional field to help clients filter CM AVC Events
|
|
| 22 |
| Split from [CPS-2521] Invoke YANG modelled synchronous action - Jira |
| |
| 23 | 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? @kieran mccarthy : Do we support restconf like queries or xpath only? (L) . *Spec out before Sept'23. No implementation.
|
| |
| 24 | Enhanced query support (scope) | Currently the passthrough has an 'fields' parameter to do a scoped query. @kieran mccarthy : Do we support restconf like queries or xpath only? (L) *Spec out before Sept'23. No implementation. |
| |
| 25 | 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. Read from operations. (S) - Forward only. No validation or data enhancements (add prefixis) |
|
| 26 | TBC | Support | (S) As per #18 |
|
| 27 | TBC | Support relationships for 'Instance Identifier' | Should be possible to identify a cmhandle using multiple instance identifiers. |