summaryrefslogtreecommitdiffstats
path: root/kubernetes/vfc/charts/vfc-vnfmgr/Chart.yaml
diff options
context:
space:
mode:
authorAlex Shatov <alexs@att.com>2019-01-31 16:17:59 -0500
committerAlex Shatov <alexs@att.com>2019-01-31 16:17:59 -0500
commite619af968c4470a5d9bc5076a7eb6f4afcbcacfb (patch)
tree18f25e839b9168a3aadd59a64fe6a9cc3d33878e /kubernetes/vfc/charts/vfc-vnfmgr/Chart.yaml
parent2b182642d4a6761815ac8172e759a022119622ee (diff)
4.6.0 policy-handler active-passive
DCAEGEN2-932: - mode_of_operation: active or passive = active is as before this change = in passive mode the policy-handler * closes the web-socket to PDP * skips the periodic catch_ups * still periodically checks for reconfigure * still allows usig the web-server to retrieve policies from PDP - default is active - when mode_of_operation changes from passive to active, the policy-handler invokes the catch_up right away - config-kv contains the optional override field mode_of_operation = changing the mode_of_operation in config-kv and invoking POST /reconfigure will bring the new value and change the mode of operation of the policy-handler if no service_activator section is provided in consul-kv record - reduced the default web-socket ping interval from 180 to 30 seconds because PDP changed its default timeout on the web-socket from 400 seconds to 50 seconds Change-Id: Iab66270dc4b1ee1ec422350be794ff161cd4a512 Signed-off-by: Alex Shatov <alexs@att.com> Issue-ID: DCAEGEN2-932
Diffstat (limited to 'kubernetes/vfc/charts/vfc-vnfmgr/Chart.yaml')
0 files changed, 0 insertions, 0 deletions