Doc updates for London

[dcaegen2.git] / docs / sections / services / ves-hv / run-time-configuration.rst

diff --git a/docs/sections/services/ves-hv/run-time-configuration.rst b/docs/sections/services/ves-hv/run-time-configuration.rst
index c2352c7..4da0b10 100644 (file)
--- a/docs/sections/services/ves-hv/run-time-configuration.rst
+++ b/docs/sections/services/ves-hv/run-time-configuration.rst
@@ -7,7 +7,13 @@ Run-Time configuration
 ======================
 
 HV-VES dynamic configuration is primarily meant to provide DMaaP Connection Objects (see :ref:`dmaap-connection-objects`).
-These objects contain information necessary to route received VES Events to correct Kafka topic. This metadata will be later referred to as Routing definition.
+
+.. note:: Kafka config info.
+    In the case of HV-VES, this configuration method is purely used as a generic reference.
+    The underlying kafka connection config is managed as part of the dcea helm configuration.
+
+These objects contain information necessary to route received VES Events to correct Kafka topic.
+This metadata will be later referred to as Routing definition.
 
 Collector uses DCAE-SDK internally, to fetch configuration from Config Binding Service.
 
@@ -42,7 +48,4 @@ For more information, see :ref:`supported_domains`.
 Providing configuration during OOM deployment
 ---------------------------------------------
 
-The configuration is created from HV-VES Cloudify blueprint by specifying **application_config** node during ONAP OOM/Kubernetes deployment. Example of the node specification:
-
-.. literalinclude:: resources/blueprint-snippet.yaml
-    :language: yaml
\ No newline at end of file
+The configuration is created from HV-VES Helm charts defined under **applicationConfig**  during ONAP OOM/Kubernetes deployment.