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

1 files changed, 7 insertions, 1 deletions

diff --git a/kubernetes/dcaegen2/charts/dcae-bootstrap/resources/inputs/k8s-policy_handler-inputs.yaml b/kubernetes/dcaegen2/charts/dcae-bootstrap/resources/inputs/k8s-policy_handler-inputs.yaml
index 50ac16ffc9..9cd37b5e2a 100644
--- a/kubernetes/dcaegen2/charts/dcae-bootstrap/resources/inputs/k8s-policy_handler-inputs.yaml
+++ b/kubernetes/dcaegen2/charts/dcae-bootstrap/resources/inputs/k8s-policy_handler-inputs.yaml
@@ -31,6 +31,12 @@ application_config:
     policy_retry_count : 5
     policy_retry_sleep : 5
 
+    # mode of operation for the policy-handler
+    # either active or passive
+    # in passive mode the policy-hanlder will not listen to
+    #                 and will not bring the policy-updates from policy-engine
+    mode_of_operation : "active"
+
     # config of automatic catch_up for resiliency
     catch_up :
         # interval in seconds on how often to call automatic catch_up
@@ -77,7 +83,7 @@ application_config:
         # optional timeout_in_secs specifies the timeout for the http requests
         timeout_in_secs: 60
         # optional ws_ping_interval_in_secs specifies the ping interval for the web-socket connection
-        ws_ping_interval_in_secs: 180
+        ws_ping_interval_in_secs: 30
     # deploy_handler config
     #    changed from string "deployment_handler" in 2.3.1 to structure in 2.4.0
     deploy_handler :