diff options
| author |   Vijay Venkatesh Kumar <vv770d@att.com> | 2019-02-02 06:16:30 +0000 |
|---|---|---|
| committer |   Gerrit Code Review <gerrit@onap.org> | 2019-02-02 06:16:30 +0000 |
| commit | fc3d73e393a3e9e0b6f9def33b5fb7245b0e3280 (patch) | |
| tree | 68d34a13c1bacbcb626e9f667da7567b6ace6efa /input-templates/phinputs.yaml | |
| parent | 5ba300ae425d1cddf622117e5f5af48457b9061e (diff) | |
| parent | 65cb347393869a0e38649bd175fd49ef28b42060 (diff) | |
Merge "blueprint for 4.6.0 policy-handler active-passive"
Diffstat (limited to 'input-templates/phinputs.yaml')
| -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 : |