Merge "Add configurable monitor timeouts for ovn dbs" into stable/stein

deployment/ovn/ovn-dbs-pacemaker-puppet.yaml

@@ -60,6 +60,10 @@ parameters:
     description: >
       Setting this to a unique value will re-run any deployment tasks which
       perform configuration on a Heat stack-update.
+  OVNDBSPacemakerTimeout:
+    description: timeout for monitor of ovn dbs resource in seconds
+    type: number
+    default: 60
 
 conditions:
   puppet_debug_enabled: {get_param: ConfigDebug}
@@ -100,6 +104,7 @@ outputs:
           - tripleo::profile::pacemaker::ovn_dbs_bundle::nb_db_port: {get_param: OVNNorthboundServerPort}
           - tripleo::profile::pacemaker::ovn_dbs_bundle::sb_db_port: {get_param: OVNSouthboundServerPort}
           - tripleo::profile::pacemaker::ovn_dbs_bundle::container_backend: {get_param: ContainerCli}
+          - tripleo::profile::pacemaker::ovn_dbs_bundle::dbs_timeout: {get_param: OVNDBSPacemakerTimeout}
           - tripleo::haproxy::ovn_dbs_manage_lb: false
           - tripleo::ovn_dbs::firewall_rules:
               '121 OVN DB server ports':

releasenotes/notes/setup_timeouts_ovn_dbs-141be475dd2cd7ae.yaml

@@ -0,0 +1,11 @@
+---
+features:
+  - |
+    Under pressure, the default monitor timeout value of 20 seconds is not
+    enough to prevent unnecessary failovers of the ovn-dbs pacemaker resource.
+    While spawning a few VMs in the same time this could lead to unnecessary
+    movements of master DB, then re-connections of ovn-controllers (slaves are
+    read-only), further peaks of load on DBs, and at the end it could lead to
+    snowball effect. Now this value can be configurable by
+    OVNDBSPacemakerTimeout which will configure
+    tripleo::profile::pacemaker::ovn_dbs_bundle (default is set to 60s).