Prepare glusterfs to role based setup
Change-Id: I215ee12680154bb03fd200c608111e1dce0cf265
Related-Prod: https://mirantis.jira.com/browse/PROD-23104
Needed-by: Ib790fd65113fa62e62ec3b3cf715bebdec95e06c
diff --git a/classes/cluster/drivetrain-ha/infra/config.yml b/classes/cluster/drivetrain-ha/infra/config.yml
index 96c4963..8c95485 100644
--- a/classes/cluster/drivetrain-ha/infra/config.yml
+++ b/classes/cluster/drivetrain-ha/infra/config.yml
@@ -73,6 +73,7 @@
linux_system_codename: xenial
single_address: ${_param:cicd_control_node01_address}
keepalived_vip_priority: 103
+ glusterfs_node_role: primary
cicd_control_node02:
name: ${_param:cicd_control_node02_hostname}
domain: ${_param:cluster_domain}
@@ -84,6 +85,7 @@
single_address: ${_param:cicd_control_node02_address}
keepalived_vip_priority: 102
docker_swarm_role: worker
+ glusterfs_node_role: secondary
cicd_control_node03:
name: ${_param:cicd_control_node03_hostname}
domain: ${_param:cluster_domain}
@@ -95,4 +97,5 @@
single_address: ${_param:cicd_control_node03_address}
keepalived_vip_priority: 101
docker_swarm_role: worker
+ glusterfs_node_role: secondary