Allow overriding corosync token_timeout

There are cases where the default allotted time (10s) is not enough.
This only works during cluster setup.

Change-Id: Ieecb8ce044123fbfcca9ee2d70ca9bad616b7cda

deployment/pacemaker/pacemaker-baremetal-puppet.yaml

@@ -46,6 +46,11 @@ parameters:
     type: string
     description: The password for the 'pcsd' user for pacemaker.
     hidden: true
+  CorosyncTokenTimeout:
+    type: number
+    description: Time in milliseconds until a token loss is declared after
+                not receiving a token.
+    default: 10000
   CorosyncSettleTries:
     type: number
     description: Number of tries for cluster settling. This has the
@@ -150,7 +155,7 @@ outputs:
         pacemaker::corosync::manage_fw: false
         pacemaker::resource_defaults::defaults:
           resource-stickiness: { value: INFINITY }
-        corosync_token_timeout: 10000
+        corosync_token_timeout: {get_param: CorosyncTokenTimeout}
         pacemaker::corosync::settle_tries: {get_param: CorosyncSettleTries}
         pacemaker::resource::bundle::deep_compare: true
         pacemaker::resource::ip::deep_compare: true

releasenotes/notes/corosync_token_timeout-d674c873c505cfe6.yaml

@@ -0,0 +1,6 @@
+---
+features:
+  - |
+    Add option to override the default corosync token_timeout value.
+    There are cases where the default allotted time (10s) is not enough.
+    This only works during cluster setup (first deployment).