aboutsummaryrefslogtreecommitdiffstats
path: root/overcloud.yaml
diff options
context:
space:
mode:
authorEmilien Macchi <emilien@redhat.com>2016-01-13 13:04:22 -0500
committerGiulio Fidente <gfidente@redhat.com>2016-03-05 03:23:04 +0100
commit664df3372d9b922c08a1e893ee49632613cbcc6b (patch)
tree0745a8ef289742a7b41275f06ccd1cb47df6314c /overcloud.yaml
parent7981f69c034c5d08abade7f62161aeec65045814 (diff)
Allow to enable IPv6 on Corosync
To enable IPv6 in Corosync, you'll need to set the --ipv6 parameter when building the cluster. To do so, we need to specify this parameter in puppet configuration when running ::pacemaker::corosync class. So we have now a new parameter: CorosyncIPv6 which is a boolean, False by default. If set to True, it will pass right options to enable IPv6 when building the Pacemaker cluster. Change-Id: I485f1399964ddd7a201ed19ec6580b8a136b3acd
Diffstat (limited to 'overcloud.yaml')
-rw-r--r--overcloud.yaml5
1 files changed, 5 insertions, 0 deletions
diff --git a/overcloud.yaml b/overcloud.yaml
index c91d2e11..0f33665e 100644
--- a/overcloud.yaml
+++ b/overcloud.yaml
@@ -77,6 +77,10 @@ parameters:
default: []
description: Should be used for arbitrary ips.
type: json
+ CorosyncIPv6:
+ default: false
+ description: Enable IPv6 in Corosync
+ type: boolean
Debug:
default: ''
description: Set to True to enable debugging on all services.
@@ -906,6 +910,7 @@ resources:
CloudDomain: {get_param: CloudDomain}
ControlVirtualInterface: {get_param: ControlVirtualInterface}
ControllerExtraConfig: {get_param: controllerExtraConfig}
+ CorosyncIPv6: {get_param: CorosyncIPv6}
Debug: {get_param: Debug}
EnableFencing: {get_param: EnableFencing}
ManageFirewall: {get_param: ManageFirewall}