Pacemaker: Difference between revisions
From DWIKI
mNo edit summary |
m (→Links) |
||
| Line 5: | Line 5: | ||
*[http://jensd.be/156/linux/building-a-high-available-failover-cluster-with-pacemaker-corosync-pcs Building a high-available failover cluster with Pacemaker, Corosync & PCS] | *[http://jensd.be/156/linux/building-a-high-available-failover-cluster-with-pacemaker-corosync-pcs Building a high-available failover cluster with Pacemaker, Corosync & PCS] | ||
*[https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html-single/High_Availability_Add-On_Administration/index.html HIGH AVAILABILITY ADD-ON ADMINISTRATION] | *[https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html-single/High_Availability_Add-On_Administration/index.html HIGH AVAILABILITY ADD-ON ADMINISTRATION] | ||
*[https://www.digitalocean.com/community/tutorials/how-to-create-a-high-availability-setup-with-corosync-pacemaker-and-floating-ips-on-ubuntu-14-04 How To Create a High Availability Setup with Corosync, Pacemaker, and Floating IPs on Ubuntu 14.04] | |||
=Commands/tools= | =Commands/tools= | ||
Revision as of 14:18, 8 July 2016
uses Corosync or heartbeat, it seems corosync is the one to go for.
Links
- Cluster Labs
- Building a high-available failover cluster with Pacemaker, Corosync & PCS
- HIGH AVAILABILITY ADD-ON ADMINISTRATION
- How To Create a High Availability Setup with Corosync, Pacemaker, and Floating IPs on Ubuntu 14.04
Commands/tools
- crm
- crmadmin
- cibadm
- pcs
Useful commands
Dump entire crm
cibadm -Q
FAQ
Error: cluster is not currently running on this node
pcs cluster start
