blob: 51acf66f0e3e44badce04843b70ecca5d3727d7e (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
|
.. This work is licensed under a Creative Commons Attribution 4.0 International License.
.. http://creativecommons.org/licenses/by/4.0
.. Copyright (C) 2021 Nordix Foundation, Pantheon.tech
.. _architecture:
CPS Architecture
################
.. toctree::
:maxdepth: 1
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.
In this release the CPS is a stand-alone component. Project page describing eventual scope and ambition is here:
`Configuration Persistence Service Project <https://wiki.onap.org/display/DW/Configuration+Persistence+Service+Project>`_
This page reflects the state for Honolulu-R8 release.
.. image:: _static/cps-r8-arch-diagram.png
API definitions
===============
Configuration Persistence Service provides following interfaces.
.. list-table::
:header-rows: 1
* - Interface name
- Interface definition
- Interface capabilities
- Protocol
* - CPS-E-01
- Administrative Data Management
- - create/delete dataspace
- create/delete schema set
- create/delete anchor
- REST
* - CPS-E-02
- Generic Data Access
- - create data node
- read data node by xpath with or without descendants
- update data node by xpath with or without descendants
- REST
* - CPS-E-03
- Generic Data Search
- - query data nodes by xpath prefix and attribute value
- REST
* - CPS-E-04
- Change Notification
- *Not available in Honolulu-R8*
- *N/A*
* - CPS-E-05
- xNF Data Access
- - read xNF data
- query xNF data
- REST
The CPS Basic Concepts are described in :doc:`modeling`.
|
