diff options
| author |   Alex Shatov <alexs@att.com> | 2019-01-31 16:15:08 -0500 |
|---|---|---|
| committer | Alex Shatov <alexs@att.com> | 2019-01-31 16:15:08 -0500 |
| commit | 65cb347393869a0e38649bd175fd49ef28b42060 (patch) | |
| tree | 3d1cd05da6686fa26a413cb77ffe662be2e11739 /input-templates | |
| parent | 99cdec225e8f86646715d56748daa412e9488ce7 (diff) | |
blueprint for 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: Iae93746336a38af4248a1c77fdcf98e31ce956bd
Signed-off-by: Alex Shatov <alexs@att.com>
Issue-ID: DCAEGEN2-932
Diffstat (limited to 'input-templates')
| -rw-r--r-- | input-templates/phinputs.yaml | 8 |
1 files changed, 7 insertions, 1 deletions
diff --git a/input-templates/phinputs.yaml b/input-templates/phinputs.yaml index 89a3de5..4078208 100644 --- a/input-templates/phinputs.yaml +++ b/input-templates/phinputs.yaml @@ -28,6 +28,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 @@ -71,7 +77,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 : |