Code Review
/
cps.git
/ blobdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
|
commitdiff
|
review
|
tree
raw
|
inline
| side by side
Merge "[STRIMZI] Add strimzi kafka notes"
[cps.git]
/
docs
/
architecture.rst
diff --git
a/docs/architecture.rst
b/docs/architecture.rst
index
b703cfa
..
acde1b1
100644
(file)
--- a/
docs/architecture.rst
+++ b/
docs/architecture.rst
@@
-6,8
+6,6
@@
CPS Architecture
################
CPS Architecture
################
-.. warning:: draft
-
.. toctree::
:maxdepth: 1
.. toctree::
:maxdepth: 1
@@
-18,19
+16,24
@@
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.
The Configuration Persistence Service (CPS) provides storage for run-time configuration and operational
parameters that need to be used by ONAP.
-In this release CPS is no longer a stand alone component and is released along with Cps-Temporal and the NCMP-DMI
Plugin.
+In this release CPS is no longer a stand alone component and is released along with Cps-Temporal and the NCMP-DMI
-
Plugin.
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 Istanbul-R9 release.
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 Istanbul-R9 release.
-.. image:: _static/cps-r8-arch-diagram.png
+.. image:: _static/star.png
+ :class: float-left
+
+**Note:** SDC and AAI interfaces have not yet been implemented.
+
+.. image:: _static/cps-r9-arch-diagram.png
API definitions
===============
API definitions
===============
-Configuration Persistence Service provides following interfaces.
+Configuration Persistence Service provides
the
following interfaces.
.. list-table::
:header-rows: 1
.. list-table::
:header-rows: 1
@@
-41,7
+44,7
@@
Configuration Persistence Service provides following interfaces.
- Protocol
* - CPS-E-01
- Administrative Data Management
- Protocol
* - CPS-E-01
- Administrative Data Management
- - - create
/delete
dataspace
+ - - create dataspace
- create/delete schema set
- create/delete anchor
- REST
- create/delete schema set
- create/delete anchor
- REST
@@
-57,12
+60,25
@@
Configuration Persistence Service provides following interfaces.
- REST
* - CPS-E-04
- Change Notification
- REST
* - CPS-E-04
- Change Notification
- - *Not available in Honolulu-R8*
- - *N/A*
+ - - Kafka is used as the event messaging system
+ - running instance is supplied independently from any Kafka instance deployed from ONAP
+ - published events contain Timestamp, Dataspace, Schema set, Anchor and JSON Data Payload
+ - Kafka
* - CPS-E-05
- xNF Data Access
- - read xNF data
- query xNF data
- REST
* - CPS-E-05
- xNF Data Access
- - read xNF data
- query xNF data
- REST
+ * - CPS-E-06
+ - Temporal Data Access
+ - - data storage and access
+ - REST
+ * - CPS-E-07
+ - Admin
+ - - logging levels and configuration
+ - monitoring
+ - health including liveliness state and readiness state
+ - metrics through Prometheus
+ - Various
The CPS Basic Concepts are described in :doc:`modeling`.
The CPS Basic Concepts are described in :doc:`modeling`.