Tâche #13121
Scénario #11706: Faire fonctionner la haute disponibilité sur EOLE 2.5 (Sphynx inclus)
Revoir le template corosync.conf
Status:
Fermé
Priority:
Normal
Assigned To:
Target version:
Remaining (hours):
0.0
Description
Entre autre, déclarer les 2 nœuds du cluster sous cette forme :
nodelist { node { ring0_addr: 10.0.254.11 name: sphynx } node { ring0_addr: 10.0.254.11 name: sphynxb } }
Définir le quorum :
quorum { # Quorum for the Pacemaker Cluster Resource Manager provider: corosync_votequorum # Number of bare metal hosts, VM are managed by pacemaker and # “expected_votes” will increase when they get started expected_votes: 2 # Two node mode two_node: 1 # Pacemaker resources (so VMs) will not be started until # number of nodes is equal to “expected_votes” wait_for_all: 1 last_man_standing: 1 }
Associated revisions
Ajustement de la configuration corosync sur 2.5
dicos/02_haute_dispo.xml :- ajout d'un délais avant le début de supervision des services
- Possibilité de ressources en Load Balancing
tmpl/corosync.conf : - service pacemaker géré en externe
- fonctionnement en mode quorum avec 2 noeuds et 1 survivant
diagnose/150-ha : - prise en compte de l'id du noeud dans les commandes crm
ref #13121 @3h
Test et configuration du quorum du cluster en mode two_nodes
corosync.conf : wait_for_all: 0
ref #13121 @2h
History
#1 Updated by Fabrice Barconnière about 8 years ago
- Description updated (diff)
#2 Updated by Fabrice Barconnière almost 8 years ago
- Status changed from Nouveau to En cours
#3 Updated by Fabrice Barconnière almost 8 years ago
- Description updated (diff)
- Assigned To set to Fabrice Barconnière
#4 Updated by Fabrice Barconnière almost 8 years ago
- % Done changed from 0 to 100
- Remaining (hours) changed from 3.0 to 0.25
#5 Updated by Fabrice Barconnière almost 8 years ago
- Status changed from En cours to Résolu
#6 Updated by Joël Cuissinat almost 8 years ago
- Status changed from Résolu to Fermé
- Remaining (hours) changed from 0.25 to 0.0
Vu.