summaryrefslogtreecommitdiffstats
path: root/docs/sections/architecture.rst
diff options
context:
space:
mode:
authorTony Hansen <tony@att.com>2020-04-27 18:30:52 +0000
committerGerrit Code Review <gerrit@onap.org>2020-04-27 18:30:52 +0000
commit1d9549e5adf1feab7a5b269e3748b5027fec3746 (patch)
tree28f2ec8aa3a23b160fc025a3cc4380f1487a9ced /docs/sections/architecture.rst
parent119b02361f6eb3d9f34202d2ae4c2dab467dfadd (diff)
parent7cfaea2ee5e73a5a0a669da3b8c949000245cb83 (diff)
Merge "dcae r6 doc updates cont."
Diffstat (limited to 'docs/sections/architecture.rst')
-rw-r--r--docs/sections/architecture.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/sections/architecture.rst b/docs/sections/architecture.rst
index bd97770a..3bc3ceb6 100644
--- a/docs/sections/architecture.rst
+++ b/docs/sections/architecture.rst
@@ -43,7 +43,6 @@ The following lists the components included in ONAP DCAE . All DCAE components
- DCAE Inventory-API: API for DCAE's TOSCA model store.
- Platform services
- Consul: Distributed service discovery service and KV store.
- - PNDA: Platform for Network Data Analytics.
- Postgres Database: DCAE's TOSCA model store.
- Redis Database: DCAE's transactional state store, used by TCA for supporting persistence and seamless scaling.
@@ -60,12 +59,13 @@ The following lists the components included in ONAP DCAE . All DCAE components
- Docker based Threshold Crosssing Analytics
- Heartbeat Services
- SON-Handler Service
- - Microservices
+ - Event processors
- PNF Registration Handler
- VES Mapper Service
- PM-Mapper Service
- BBS-EventProcessor Service
- PM Subcription Handler
+ - DataLake Handlers
The figure below shows the DCAE architecture and how the components work with each other. The components on the right constitute the Platform/controller components which are statically deployed. The components on the right represent the services which can be both deployed statically or dynamically (via CLAMP)