diff options
| author |   Filip Krzywka <filip.krzywka@nokia.com> | 2019-03-19 15:53:15 +0100 |
|---|---|---|
| committer | Filip Krzywka <filip.krzywka@nokia.com> | 2019-04-11 11:33:05 +0200 |
| commit | 12acf3e8deaf15c6e5263b2b402c966f495057f1 (patch) | |
| tree | 4afa68c835536413d4d8290856659cebeb0dc1c7 /docs/sections/services/ves-hv/run-time-configuration.rst | |
| parent | 580eae246a3ac7bf9533df96d20c0fc9b5425d3c (diff) | |
Update HV-VES documentation
- include changes to collector configuration, especially moving from
command line parameters to configuration file
- include changes to run-time configuration i.e. moving from direct
Consul requests to CBS usage
- changes in design.rst cover extraction of protofiles from hv-ves
repository to sdk
- also swapped rstTable to rstCSVTable in deployment.rst as they
are easier to maintain
Change-Id: I5cdee7170d03edaf31615e40f6cb6ad14a6a2331
Issue-ID: DCAEGEN2-1352
Signed-off-by: Filip Krzywka <filip.krzywka@nokia.com>
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, 4 insertions, 6 deletions
diff --git a/docs/sections/services/ves-hv/run-time-configuration.rst b/docs/sections/services/ves-hv/run-time-configuration.rst index 76d622c6..5efc6e31 100644 --- a/docs/sections/services/ves-hv/run-time-configuration.rst +++ b/docs/sections/services/ves-hv/run-time-configuration.rst @@ -8,7 +8,7 @@ Run-Time configuration (see :ref:`deployment`) -HV-VES can fetch configuration directly from Consul service in the following JSON format: +HV-VES fetches configuration from Config Binding Service in the following JSON format: .. code-block:: json @@ -50,10 +50,8 @@ The configuration is created from HV-VES Cloudify blueprint by specifying **appl fromDomain: perf3gpp toTopic: HV_VES_PERF3GPP -Endpoint on which HV-VES seeks configuration can be set during deployment as described in :ref:`deployment`. +HV-VES waits 10 seconds (default, configurable during deployment with **firstRequestDelay** option, see :ref:`configuration_file`) before the first attempt to retrieve configuration from CBS. This is to prevent possible synchronization issues. During that time HV-VES declines any connection attempts from xNF (VNF/PNF). -HV-VES waits 10 seconds (default, configurable during deplyoment with **first-request-delay** option, see :ref:`deployment`) before the first attempt to retrieve configuration from Consul. This is to prevent possible synchronization issues. During that time HV-VES declines any connection attempts from xNF (VNF/PNF). +After first request, HV-VES asks for configuration in fixed intervals, configurable from file configuration (**requestInterval**). By default interval is set to 5 seconds. -After first request, HV-VES asks for configuration in fixed intervals, configurable from command line (**request-interval**). By defualt interval is set to 5 seconds. - -In case of failing to retrieve configuration, collector temporarily extends this interval and retries. After five unsuccessfull attempts, container becomes unhealthy and cannot recover. HV-VES in this state is unusable and the container should be restarted. +In case of failing to retrieve configuration, collector retries the action. After five unsuccessful attempts, container becomes unhealthy and cannot recover. HV-VES in this state is unusable and the container should be restarted. |