Filip Krzywka | 4bb79b7 | 2018-09-25 10:57:17 +0200 | [diff] [blame] | 1 | .. This work is licensed under a Creative Commons Attribution 4.0 International License. |
| 2 | .. http://creativecommons.org/licenses/by/4.0 |
| 3 | |
| 4 | Configuration |
| 5 | ============= |
| 6 | |
| 7 | HV-VES expects to be able to fetch configuration directly from consul service in following JSON format: |
| 8 | |
| 9 | .. code-block:: json |
| 10 | |
| 11 | { |
| 12 | "dmaap.kafkaBootstrapServers": "kafka-host:9093", |
| 13 | "collector.routing": [ |
| 14 | { |
| 15 | "fromDomain": "PERF3GPP", |
| 16 | "toTopic": "topic-1" |
| 17 | }, |
| 18 | { |
| 19 | "fromDomain": "HEARTBEAT", |
| 20 | "toTopic": "topic-2" |
| 21 | }, |
| 22 | ... |
| 23 | ] |
| 24 | } |
| 25 | |
| 26 | |
| 27 | During ONAP OOM/Kubernetes deployment this configuration is created from HV-VES cloudify blueprint. |
| 28 | |
| 29 | Endpoint on which HV-VES seeks configuration can be configured during deployment as described in installation_. |
| 30 | |
| 31 | .. _installation: ./installation.html |