diff options
| author |   Vijay VK <vv770d@att.com> | 2019-06-10 15:57:41 +0100 |
|---|---|---|
| committer | VENKATESH KUMAR <vv770d@att.com> | 2019-06-10 15:48:33 -0400 |
| commit | c9a8aa4dc4e7641a4e5ab0f2a81cd8d15de3b41a (patch) | |
| tree | c0272880acdc2dacf4e3453a13dcf7ad396668c5 /docs/sections/architecture.rst | |
| parent | 9a351fdb1611fd7247d60f76c7b4faab8c0981c7 (diff) | |
Update typos and VES deploy notes
Change-Id: Ibb0b96307b53dc3179fe2f0d8c900962ee99ac0c
Signed-off-by: VENKATESH KUMAR <vv770d@att.com>
Issue-ID: DCAEGEN2-1541
Signed-off-by: VENKATESH KUMAR <vv770d@att.com>
Diffstat (limited to 'docs/sections/architecture.rst')
| -rw-r--r-- | docs/sections/architecture.rst | 6 |
1 files changed, 1 insertions, 5 deletions
diff --git a/docs/sections/architecture.rst b/docs/sections/architecture.rst index 349f58b5..f4084eeb 100644 --- a/docs/sections/architecture.rst +++ b/docs/sections/architecture.rst @@ -22,11 +22,7 @@ data collection needs, event processors for data standardization, analytics tha collection and analytics, and support other ONAP functions. Service components and DMaaP buses form the "data plane" for DCAE, where DCAE collected data is 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 -configuration management for DCAE service components in multi-site deployment. +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 configuration management for DCAE service components in multi-site deployment. DCAE R4 Components |