CPS Architecture
High Level Component Definition and Architectural Relationships
The Configuration Persistence Service (CPS) provides storage for run-time configuration and operational parameters that need to be used by ONAP.
CPS is no longer a stand alone component and is released along with and the NCMP-DMI-Plugin.
Project page describing eventual scope and ambition is here: Configuration Persistence Service Project
This page reflects the state for the latest release.
API definitions
Configuration Persistence Service provides the following interfaces.
Interface name |
Interface definition |
Interface capabilities |
Protocol |
---|---|---|---|
CPS-E-01 |
Administrative Data Management |
|
REST |
CPS-E-02 |
Generic Data Access |
|
REST |
CPS-E-03 |
Generic Data Search |
|
REST |
CPS-E-04 |
Change Notification |
|
Kafka |
CPS-E-05 |
xNF Data Access |
|
REST |
CPS-E-07 |
Admin |
|
Various |
The CPS Basic Concepts are described in CPS Modeling.