From e284409662fd311bd78fa88b92a5ca8945481ac1 Mon Sep 17 00:00:00 2001 From: kjaniak Date: Wed, 14 Nov 2018 15:42:03 +0100 Subject: Restore proto schemas in docs Change-Id: I1f95122cf8ddd510873bf0d7d3e77231c91a400d Issue-ID: DCAEGEN2-972 Signed-off-by: kjaniak --- docs/sections/services/ves-hv/configuration.rst | 31 ------------------------- 1 file changed, 31 deletions(-) delete mode 100644 docs/sections/services/ves-hv/configuration.rst (limited to 'docs/sections/services/ves-hv/configuration.rst') diff --git a/docs/sections/services/ves-hv/configuration.rst b/docs/sections/services/ves-hv/configuration.rst deleted file mode 100644 index f2b726f4..00000000 --- a/docs/sections/services/ves-hv/configuration.rst +++ /dev/null @@ -1,31 +0,0 @@ -.. This work is licensed under a Creative Commons Attribution 4.0 International License. -.. http://creativecommons.org/licenses/by/4.0 - -Configuration -============= - -HV-VES expects to be able to fetch configuration directly from consul service in following JSON format: - -.. code-block:: json - - { - "dmaap.kafkaBootstrapServers": "kafka-host:9093", - "collector.routing": [ - { - "fromDomain": "PERF3GPP", - "toTopic": "topic-1" - }, - { - "fromDomain": "HEARTBEAT", - "toTopic": "topic-2" - }, - ... - ] - } - - -During ONAP OOM/Kubernetes deployment this configuration is created from HV-VES cloudify blueprint. - -Endpoint on which HV-VES seeks configuration can be configured during deployment as described in installation_. - -.. _installation: ./installation.html \ No newline at end of file -- cgit 1.2.3-korg