-
Epic
-
Resolution: Done
-
Medium
-
None
-
None
-
Configuration Persistence Service in R8
-
Specification
-
GO
-
Original Scope
-
XL
-
GO
-
Green
-
GO
-
GO
-
Green
Description of Use Case / Requirement: Continuing development of Configuration Persistence Service (CPS) in R7 – Currently hosted by the CC-SDK project. This will enhance API and of the schema internal C&PS database used to support existing and R7 use cases. In parallel other activities will drive a Model driven C&PS PoC and State management PoC.
Owners (one of these should be the Assignee - use @ notation):
(Supporting): bencheung , tfinnerty
Link to HLD/LLD (if any):
https://wiki.onap.org/pages/viewpage.action?pageId=92996419
Dependency Relationships with Other Projects: ONAP/3GPP & O-RAN Alignment: Standards Defined Notifications over VES for development of the Standards-Defined VES. REQ-327
Project Impact (Test Only (TO), Code (C)): (C)
Support Status for each Affected Project (Supported (S); Partially Supported (P); Not Supported (N)): (S)
Requirements:
CPS: New ONAP Platform Component
- Impact: New ONAP Platform component/project
- Companies Supporting: Ericsson, Bell Canada, Nokia, AT&T, Wipro
- Number Developers/Testers: 6
CPS has no (dependency-type) impacts on any existing project or use case. There are however two use cases that will become clients/users of CPS:
- End-to-End Network Slicing
- SON OOF (PCI)
API Changes
- As CPS is a new component the API is still under construction. The full proposal for the API can be found here: https://wiki.onap.org/display/DW/CCSDK-2870+DP%3A+CPS+REST+API+Documentation+-+PROPOSAL
Non Functional Requirements
- N/A
Integration Leads (use @ notation):
- clones
-
REQ-1 ONAP Requirement Template
- To Do
-
REQ-537 Long-term IPv4/IPv6 dual stack networking support
- Done
- is blocked by
-
ONAPARC-640 (Honolulu-R8) - Func - Configuration Persistence Service in R8
- Closed
-
REQ-630 Integration Test for CPS
- Done