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)
- Version strategy to control Continuous Delivery (CPS and NCMP)
- 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 ConfigurationModel basedInstance based
Query PropagationAmalgamate responsesCapability 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
Priority | London Requirement Jira | Component(s) | Description | Notes | Team & Work-Item Owner | Jira(s) |
---|---|---|---|---|---|---|
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. | |||
2 | CPS-NCMP CPS-Core | 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 | - CPS-1171Getting issue details... STATUS - CPS-1326Getting issue details... STATUS - CPS-1344Getting issue details... STATUS - CPS-1443Getting issue details... STATUS- CPS-1445Getting issue details... STATUS
-
CPS-1475Getting issue details...
STATUS
-
CPS-1509Getting issue details...
STATUS
| |
3 | CPS-NCMP | Support ncmp-datastores:operational for querying data (single CM handle, synchronous only) | See CPS-391 page for details about supported operations and combinations. | |||
4 | CPS-Core CPS-NCMP | DMI Audit |
| |||
5 | CPS-NCMP | [investigation/spec] CM data notifications from NCMP to applications including subscriptions | Includes definition of notification and payload format | kieran mccarthy | ||
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 | Notifications
-
CPS-1385Getting issue details...
STATUS
-
CPS-1386Getting issue details...
STATUS
Subscriptions
-
CPS-1431Getting issue details...
STATUS
-
CPS-1392Getting issue details...
STATUS
-
CPS-1393Getting issue details...
STATUS
-
CPS-1394Getting issue details...
STATUS
- CPS-1561Getting issue details... STATUS - CPS-1573Getting issue details... STATUS - CPS-1599Getting issue details... STATUS | |
7 | CPS-NCMP | Support update of cached data through a message driven solution. Respond to VES Events from Devices in ONAP | Receive VES Event and transform it into a 'standard DMI→NCMP events (schema owned by NCMP) | Team 2 | ||
8 | CPS-NCMP (CPS-Core) | Deletion Performance / Delete CM Handles on criterion (TBC) | 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) Note: check with Gergely on priority as DELETING state will prevent user to act on cmhandle Note 2. This might need to be split into 'Delete on criterion ie. public/private property' and delete for 'internal/test use' performance | Team 1 | - CPS-1173Getting issue details... STATUS - CPS-1422Getting issue details... STATUS - CPS-1426Getting issue details... STATUS - CPS-1424Getting issue details... STATUS - CPS-1423Getting issue details... STATUS - CPS-1438Getting issue details... STATUS - CPS-1437Getting issue details... STATUS - CPS-1439Getting issue details... STATUS - CPS-1464Getting issue details... STATUS | |
9 | CPS-NCMP | Bulk Operations (Get, Query) | Allow bulk operations for NCMP (and/or) CPS REST Interfaces | Team 1 | - CPS-1515Getting issue details... STATUS - CPS-1550Getting issue details... STATUS - CPS-1553Getting issue details... STATUS - CPS-1555Getting issue details... STATUS - CPS-1556Getting issue details... STATUS - CPS-1557Getting issue details... STATUS - CPS-1558Getting issue details... STATUS - CPS-1560Getting issue details... STATUS | |
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 | CPS-Core / CPS-NCMP | Support for list as top level data node | Sub Team | |||
12 | CPS-Core / CPS-NCMP | Support for multiple top-elements from different modules in one CM handle/anchor | Sub Team | |||
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 NCMP-CPS | 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 / CPS-NCMP | 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 | CPS-NCMP | Send notification for updated CM handle metadata (public CM handle properties or YANG modules) | ||||
24 | CPS-Core / CPS-NCMP | Support for HTTPS and authentication
| ||||
25 | TBC | CPS-NCMP | Support ncmp-datastores:running for reading data (single CM handle, synchronous only) | 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. | ||
26 | TBC | CPS-Core / CPS-NCMP | Support ncmp-datastores:running for writing data (single CM handle, synchronous only) | |||
27 | TBC | CPS-Core | Send notifications on write operation in ncmp-datastores:running for (single CM handle, synchronous only) | |||
28 | CPS-Core / CPS-NCMP | 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) | |||
30 | CPS-NCMP | Automatic (optional) Data Sync | Metadata (per cmHandle) controls whether this will happen or not | |||
31 | CPS-NCMP | Invoke YANG modelled RPC |
Spin-off user stories, yet to be prioritized
Jira | Component(s) | Related Work Item | Description | Notes |
---|---|---|---|---|
CPS-NCMP | ||||
CPS-NCMP | ||||
CPS-NCMP | ||||
CPS-NCMP | ||||
CPS-NCMP | Investigation on the use of Liquibase to install NCMP artifacts | |||
CPS-NCMP | ||||
CPS | 7 (performance) | Add prefix for containers in different Modules in a PERFORMANT way | ||
CPS | 4 |