CPS R12 Release Planning
Overview
Project Name | Enter the name of the project |
|---|---|
Target Release Name | London |
Project Lifecycle State | Incubation |
Participating Companies | Deutsche Telecom (Tech Mahindra) , Ericsson, Fujitsu, Wipro |
Scope
What is this release trying to address?
Upgradability (CPS, NCMP)
Version strategy to control Continuous Delivery (CPS and NCMP)
Technical debt of NCMP data be handled by Liquibase in CPS
Yang Module Upgrade
backward compatible
backward incompatible
Data Transformation/Migration
Drop (and resync)
Service Maturity CPS
Delivery Pipelines
Helm best practices (design rules)
FOSS audit
Service Maturity NCMP (TBC)
Performance (CPS, NCMP)
CPS Data read
CPS Model-based query
Registration algorithm change (using schemaSet hash)
CM Handle Connectivity State
Notification Configuration
Model based
Instance based
Query Propagation
Amalgamate responses
Capability Exchange (during registration/updates)
Stretch Goals
Forwarding non-passtrough
data request
notifications
Cache Configuration
Model based
Instance based, container, leaf
AAI integration
Extend Read(query) access to cached data (datastore ncmp-datastores:operational)
cpsPath support in NCMP
field' and 'depth' RestConf-Like support in CPS (and NCMP)
Extend CPS-Path (query) capabilities
CPS Target Based Access Control (TBAC)
Ownership of dataspaces using OAuth2
NCMP Access Control
Multiple Identifiers for Anchors (CM Handles)
Minimum Viable Product
N/A
Requirements
Priority legend | |||||
Preliminary | Planned for current ONAP Release | In Progress | Paused | Completed | De-scoped |
ONAP Best Practices (Global Requirements) and similar
ONAP Requirement | Notes | CPS- Jira(s) |
|---|---|---|
Aiming for gold!
| ||
ONAP script might help us with common quality issues and save reviewing time |
CPS-temporal Requirements (TBC)
CPS-CORE / CPS-NCMP Requirements
London | Component(s) | Description | Notes | Team & | Jira(s) | ||
|---|---|---|---|---|---|---|---|
| 1 | 1 | 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-1172https://lf-onap.atlassian.net/browse/CPS-1275https://lf-onap.atlassian.net/browse/CPS-1267https://lf-onap.atlassian.net/browse/CPS-1400 | |
| 2 | 2 | CPS-NCMP | Data Write/Read Performance | NCMP (read) Requirements
@kieran mccarthy For this step we can focus on just returning just the cmhandlesIds. Anything further can be covered by another step. Note. This now overlaps with work be done with Wipro/Fujitsu, see CPS Performance Testing | Team 1 @Daniel Hanrahan | https://lf-onap.atlassian.net/browse/CPS-1171https://lf-onap.atlassian.net/browse/CPS-1326https://lf-onap.atlassian.net/browse/CPS-1344 https://lf-onap.atlassian.net/browse/CPS-1443 https://lf-onap.atlassian.net/browse/CPS-1475https://lf-onap.atlassian.net/browse/CPS-1509 | |
| 3 | 3 | CPS-NCMP | Support | See CPS-391 page for details about supported operations and combinations. | @Sourabh Sourabh | ||
| 4 | 4 | CPS-Core | DMI Audit |
| @Toine Siebelink | ||
| 5 | 5 | 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-1259https://lf-onap.atlassian.net/browse/CPS-1362 | |
| 6 | 6 | CPS-NCMP | Implementation of CM data notifications forwarded by NCMP from DMI to application | Implementing Data Notifications & Subscription Notifications on a US by US basis | Team 2 @Priyank Maheshwari | Notifications https://lf-onap.atlassian.net/browse/CPS-1385https://lf-onap.atlassian.net/browse/CPS-1386 Subscriptions https://lf-onap.atlassian.net/browse/CPS-1431https://lf-onap.atlassian.net/browse/CPS-1392https://lf-onap.atlassian.net/browse/CPS-1393https://lf-onap.atlassian.net/browse/CPS-1394 https://lf-onap.atlassian.net/browse/CPS-1561https://lf-onap.atlassian.net/browse/CPS-1573https://lf-onap.atlassian.net/browse/CPS-1599 | |
| 7 | 7 | CPS-NCMP | 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) | Team 2 @Priyank Maheshwari | https://lf-onap.atlassian.net/browse/CPS-1434https://lf-onap.atlassian.net/browse/CPS-1411https://lf-onap.atlassian.net/browse/CPS-1412https://lf-onap.atlassian.net/browse/CPS-1413 | |
| 8 | 8 | 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) | Team 1 @Sourabh Sourabh | https://lf-onap.atlassian.net/browse/CPS-1173https://lf-onap.atlassian.net/browse/CPS-1422https://lf-onap.atlassian.net/browse/CPS-1426https://lf-onap.atlassian.net/browse/CPS-1424 https://lf-onap.atlassian.net/browse/CPS-1423https://lf-onap.atlassian.net/browse/CPS-1438https://lf-onap.atlassian.net/browse/CPS-1437https://lf-onap.atlassian.net/browse/CPS-1439https://lf-onap.atlassian.net/browse/CPS-1464 | |
| 9 | 9 | CPS-NCMP | Bulk Operations (Get, Query) | Allow bulk operations for NCMP (and/or) CPS REST Interfaces | Team 1 | https://lf-onap.atlassian.net/browse/CPS-1515 https://lf-onap.atlassian.net/browse/CPS-1550 https://lf-onap.atlassian.net/browse/CPS-1553 https://lf-onap.atlassian.net/browse/CPS-1555 https://lf-onap.atlassian.net/browse/CPS-1556 https://lf-onap.atlassian.net/browse/CPS-1557 https://lf-onap.atlassian.net/browse/CPS-1558 https://lf-onap.atlassian.net/browse/CPS-1560 | |
| 10 | 10 | CPS-NCMP | CM Handle Connectivity Freshness/Staleness | Need to model what staleness is (current CPS only has concept of model-sync state, nothing about connectivity) | |||
| 11 | 11 | https://lf-onap.atlassian.net/browse/CPS-1128 Deutsche Telekom | CPS-Core / | Support for list as top level data node | Sub Team | https://lf-onap.atlassian.net/browse/CPS-491https://lf-onap.atlassian.net/browse/CPS-765https://lf-onap.atlassian.net/browse/CPS-766https://lf-onap.atlassian.net/browse/CPS-767 | |
| 12 | 12 | https://lf-onap.atlassian.net/browse/CPS-1128 Deutsche Telekom | CPS-Core / | Support for multiple top-elements from different modules in one CM handle/anchor | Sub Team | https://lf-onap.atlassian.net/browse/CPS-1051https://lf-onap.atlassian.net/browse/CPS-341 | |
| 13 | NCMP-CPS | 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, | ||||
| 14 | CPS-Core | Support multiple identifiers (alternatives for CM Handle ID) | |||||
| 15 | Support for 'Instance Identifier' | Should be possible to identify a cmhandle using multiple instance identifiers | |||||
| 16 | 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. 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. | ||||
| 17 | CPS-NCMP | Enhanced query support | 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? | ||||
| 18 | Move above 8 | 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. | |||
| 19 | CPS-NCMP | Retrieve single module resource | /v1/ch/{cm-handle}/modules/definitions/{moduleName} | ||||
| 20 | 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) | ||||
| 21 | CPS-Core / | Access control for public interfaces (NCMP, CPS-Core, DMI?) | KMC : What level of access control is there today - both on CPS and NCMP interfaces? | ||||
| 22 | CPS-NCMP | Fine-grained cache configuration | |||||
| 23 |