4bf4bab995
Avoid accumulating invalid/defunct virtual IP entries in the HA config file. use correct 'clean' name when adding a node and its virtual IP Also fix a nit in the sample HA config file BUG: 1250601 Change-Id: I0e6a251334e854d0003d5930ca804f972900b624 Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com> Reviewed-on: http://review.gluster.org/11841 Tested-by: NetBSD Build System <jenkins@build.gluster.org> Tested-by: Gluster Build System <jenkins@build.gluster.com> Reviewed-by: Meghana M <mmadhusu@redhat.com> Reviewed-by: soumya k <skoduri@redhat.com> Reviewed-on: http://review.gluster.org/13717 Smoke: Gluster Build System <jenkins@build.gluster.com> CentOS-regression: Gluster Build System <jenkins@build.gluster.com> NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
23 lines
867 B
Plaintext
23 lines
867 B
Plaintext
# Name of the HA cluster created.
|
|
# must be unique within the subnet
|
|
HA_NAME="ganesha-ha-360"
|
|
#
|
|
# The gluster server from which to mount the shared data volume.
|
|
HA_VOL_SERVER="server1"
|
|
#
|
|
# N.B. you may use short names or long names; you may not use IP addrs.
|
|
# Once you select one, stay with it as it will be mildly unpleasant to
|
|
# clean up if you switch later on. Ensure that all names - short and/or
|
|
# long - are in DNS or /etc/hosts on all machines in the cluster.
|
|
#
|
|
# The subset of nodes of the Gluster Trusted Pool that form the ganesha
|
|
# HA cluster. Hostname is specified.
|
|
HA_CLUSTER_NODES="server1,server2,..."
|
|
#HA_CLUSTER_NODES="server1.lab.redhat.com,server2.lab.redhat.com,..."
|
|
#
|
|
# Virtual IPs for each of the nodes specified above.
|
|
VIP_server1="10.0.2.1"
|
|
VIP_server2="10.0.2.2"
|
|
#VIP_server1_lab_redhat_com="10.0.2.1"
|
|
#VIP_server2_lab_redhat_com="10.0.2.2"
|