X-Git-Url: https://gerrit.onap.org/r/gitweb?a=blobdiff_plain;f=docs%2Farchitecture.rst;h=acde1b1cae4975296be952257d0eae21aac09cf1;hb=b869181fae9a688fa517ecb43a30b8331b82ccdc;hp=12a51e222baca6bfda7a6a70d4b6582b74f86df7;hpb=8640868a6d2cb0a33bdd324c8078e63def9dbe16;p=cps.git diff --git a/docs/architecture.rst b/docs/architecture.rst index 12a51e222..acde1b1ca 100644 --- a/docs/architecture.rst +++ b/docs/architecture.rst @@ -16,7 +16,7 @@ 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 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 `_ @@ -61,9 +61,9 @@ Configuration Persistence Service provides the following interfaces. * - CPS-E-04 - Change Notification - - Kafka is used as the event messaging system - - running instance is supplied independently from ONAP DMaaP component or any Kafka instance deployed from ONAP + - running instance is supplied independently from any Kafka instance deployed from ONAP - published events contain Timestamp, Dataspace, Schema set, Anchor and JSON Data Payload - - DMaaP + - Kafka * - CPS-E-05 - xNF Data Access - - read xNF data