Pacemaker: Difference between revisions
From DWIKI
m (→FAQ) |
mNo edit summary |
||
| Line 7: | Line 7: | ||
*[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] | *[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] | ||
*http://fibrevillage.com/sysadmin/304-pcs-command-reference | *http://fibrevillage.com/sysadmin/304-pcs-command-reference | ||
*[http://djlab.com/2013/04/pacemaker-corosync-drbd-cheatsheet/ Cheatsheet] | |||
=Commands/tools= | =Commands/tools= | ||
Revision as of 08:23, 15 August 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
- http://fibrevillage.com/sysadmin/304-pcs-command-reference
- Cheatsheet
Commands/tools
- crm
- crmadmin
- cibadm
- pcs
Useful commands
Dump entire crm
cibadm -Q
FAQ
show virtual ip
pcs resource show IPv4_BIND
Error: cluster is not currently running on this node
pcs cluster start
Remove a constraint
pcs constraint list --full
to identify the constraints and then
pcs constraint remove <whatever-constraint-id>
