diff options
Diffstat (limited to 'docs/sections/services/ves-hv/run-time-configuration.rst')
| -rw-r--r-- | docs/sections/services/ves-hv/run-time-configuration.rst | 10 |
1 files changed, 8 insertions, 2 deletions
diff --git a/docs/sections/services/ves-hv/run-time-configuration.rst b/docs/sections/services/ves-hv/run-time-configuration.rst index c2352c7e..830ed664 100644 --- 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. @@ -45,4 +51,4 @@ 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 + :language: yaml |