summaryrefslogtreecommitdiffstats
path: root/docs/sections/architecture.rst
diff options
context:
space:
mode:
authorVENKATESH KUMAR <vv770d@att.com>2019-06-07 01:31:10 -0400
committerVENKATESH KUMAR <vv770d@att.com>2019-06-07 11:20:28 -0400
commit9a351fdb1611fd7247d60f76c7b4faab8c0981c7 (patch)
treee31d6c216533ef5e5f1cda754582850a3b42545d /docs/sections/architecture.rst
parentcd55fc2ecf6d42e78821ee381a983e0e48c680b4 (diff)
Add VES-tls deploy
Change-Id: I7c1f90fc4a5ccabaed7faaa3883e5e14779ba975 Signed-off-by: VENKATESH KUMAR <vv770d@att.com> Issue-ID: DCAEGEN2-1593
Diffstat (limited to 'docs/sections/architecture.rst')
-rw-r--r--docs/sections/architecture.rst6
1 files changed, 2 insertions, 4 deletions
diff --git a/docs/sections/architecture.rst b/docs/sections/architecture.rst
index 9daa7070..349f58b5 100644
--- a/docs/sections/architecture.rst
+++ b/docs/sections/architecture.rst
@@ -24,10 +24,8 @@ transported among different DCAE service components.
DCAE use Consul's distributed K-V store service to manage component configurations where each key is based on the unique identity of a
DCAE component (identified by ServiceComponentName), and the value is the configuration for the corresponding component. The K-V store for each service components is
-created during deployment. DCAE platform creates and updates the K-V pairs based on information provided as part of the control loop blueprint deployment, or through
- a notification/trigger received from other ONAP components such as Policy Framework and CLAMP. Either through periodically polling or proactive pushing, the DCAE
- components get the configuration updates in realtime and apply the configuration updates. DCAE Platform also offers dynamic template resolution for configuration
-parameters that are dynamic and only known by the DCAE platform, such as dynamically provisioned DMaaP topics. This approach standardizes component deployment and
+created during deployment. DCAE platform creates and updates the K-V pairs based on information provided as part of the control loop blueprint deployment, or through a notification/trigger received from other ONAP components such as Policy Framework and CLAMP. Either through periodically polling or proactive pushing, the DCAE
+ components get the configuration updates in realtime and apply the configuration updates. DCAE Platform also offers dynamic template resolution for configuration parameters that are dynamic and only known by the DCAE platform, such as dynamically provisioned DMaaP topics. This approach standardizes component deployment and
configuration management for DCAE service components in multi-site deployment.