CPS R14 Release Planning
New Delhi (N) | ||
India Gate in New Delhi, March 20, 2016 (Credit: A. Savin, WikiCommons) |
Requirements
Priority legend | |||||
Preliminary | Priority Agreed | 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
Priority | Epic/Component/Owner/Team/Target | Description | Notes | Jira(s) |
---|---|---|---|---|
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) | Getting issues... |
2 |
| 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) | |
3 |
| CM Handle Connectivity Freshness/Staleness | Need to model what staleness is (current CPS only has concept of model-sync state, nothing about connectivity) | Done: Getting issues... |
4 |
| Update YANG schema-set for CM handle using ModuleSetTag |
|
|
5 |
| Merge CM data subscriptions in NCMP when forwarding it to DMI |
| |
6 |
| Support Alternate ID (3GPP) for CM Handle ID | NCMP's CmHandle registration endpoint shall be changed to accept a new String parameter which proposed name is alternateId. | Done: Getting issues... |
7 |
| CPS & NCMP Feature Enhancement for M Release: Delta Feature | Moved up on Previously Priority 19 |
|
8 |
| Update NCMP LCM events to include alternate id | * NCMP LCM event should send notification events with FDN identifier in the alternateid (deprecation period: correlationid=md5-hash, alternateId=FDN) | Done: Getting issues... |
9 |
| Audit Logging. NCMP to support audit logging |
*NEWLY ADDED → Customer installation was impacted |
|
10 |
| Support for Async datajobs Not just for reading specific fdn, but rather QUERY Group of FDN , it's just a broadcast to every DMI plugin. The response should mimic sending a broadcast to 2 or more CM Handles CPS Team wil only do java interface. REST Interface is done in DCM | NEW interface aligning with 3GPP i.e FDN instead of CM-HandleIds (Read use case can re-use existing dataOperationz impl. after mapping FDNs to CMHandleIds for input and back for output!) Read, Create, Update, Delete and Action support. I.e for passthrough only * NCMP to introduce a qualifier to be used along with the DMI plugin so NCMP can break the request with multiple cmhandle into batches based on the DMI plugin and the Qualifier (where qualifier should be EMS name / id). |
|
11 |
| CPS/NCMP delivery process |
| |
12 |
| Retrieve single module resource No Epic, Single User Story | /v1/ch/{cm-handle}/modules/definitions/{moduleName} | |
13 | - CPS-2166Getting issue details... STATUS
| Forwarding CM Data Notifications based on Subscription |
Interdependent on - - CPS-1812Getting issue details... STATUS --newly added-- |
|
14 | - CPS-2170Getting issue details... STATUS
| Adding limit to legacy batch (bulk) interface | proposed hardcoded limit of 50 cm handles | |
15 | - CPS-2172Getting issue details... STATUS
| Enable Open Telemetry tracing | Configuration impacts only. Ericsson has delivered the required configuration files | |
16 | - CPS-989Getting issue details... STATUS
| Replace RestTemplate with WebClient |
| |
17 | Update remaining existing/legacy NCMP APIs to support alternateId (FDN) | Update existing/legacy NCMP APIs to support FDN / alternateId Depends on - CPS-1704Getting issue details... STATUS (which now has a lower priority) Agreed with stakeholders on These open issues are not a blocker, we would leave LCM event as Legacy event and proceed with - CPS-2009Getting issue details... STATUS |
| |
18 | ||||
19 | Update existing single sync cmhandle APIs to support alternative id (containing FDNs) | |||
20 |
| NCMP to support the 3GPP ProvMnS CRUD interfaces. NCMP to Support new 3GPP sync single FDN request | Implement new NCMP CRUDAQ sync interface aligned with 3GPP API (Read and write use cases) - Wrapper on existing/legacy API | |
21 | NCMP to support datajob results in S3 | NCMP to introduce a qualifier to be used along with the DMI plugin so NCMP can break the request with multiple cmhandle into batches based on the DMI plugin and the Qualifier (where qualifier should be EMS name / id). | ||
22 |
| TBAC - 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. | 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. |
|
23 | 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 |
| |
24 | 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) | ||
25 |
| Event Digest | Additional field to help clients filter CM AVC Events | |
26 | 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, Liquibase is used in CPS to manage data(upgrades) - Now available.
| |
27 | Spike for documenting Kafka interfaces using AsyncAPI | - Documentation Generation - Code Generation (contract first, stubs) | ||
28 | Refactor legacy NCMP ASync Response Events to use Cloud Events format | (M) TBC |
| |
29 | Access control for topics which are created by NCMP. | Spike needs to be conducted. Dependent of TBAC implementations. | ||
30 | Invoke YANG modelled sync action | Invoke YANG modelled action Invoke YANG modelled RPC, Specification required. Rebbot/Reset type of actions on node. Include to the sync one | Always on operatio |