Update existing documentation
Added information about DCAE ves-openapi-manager
in existing docs pages.
Issue-ID: DCAEGEN2-2577
Signed-off-by: Edyta Krukowska <edyta.krukowska@nokia.com>
Change-Id: I4b237ee55734e31db6621b0cb91eabea5c8abb4c
diff --git a/docs/sections/architecture.rst b/docs/sections/architecture.rst
index 3c8094e..31164d6 100644
--- a/docs/sections/architecture.rst
+++ b/docs/sections/architecture.rst
@@ -41,6 +41,7 @@
- Policy Handler: Handler for fetching policy updates from Policy engine; and updating the configuration policies of KV entries in Consul cluster KV store for DCAE components.
- Service Change Handler: Handler for interfacing with SDC; receiving new TOSCA models; and storing them in DCAE's own inventory.
- DCAE Inventory-API: API for DCAE's TOSCA model store.
+ - VES OpenApi Manager: Optional validator of VES_EVENT type artifacts executed during Service distributions.
- Platform services
- Consul: Distributed service discovery service and KV store.
- Postgres Database: DCAE's TOSCA model store.
@@ -71,7 +72,11 @@
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)
-.. image:: images/R7_architecture diagram.png
+..
+ The following diagram has been created on https://app.diagrams.net/. There is an editable version of the diagram
+ in repository under path docs/sections/images/architecture_diagram. Import this file to mentioned page to edit diagram.
+
+.. image:: images/R8_architecture_diagram.png
Deployment Scenarios