- clusterlabs menu
Commercially, Pacemaker is primarily a collaborative effort between Red Hat and Novell, however we also receive considerable help and support from the folks at LinBit and the community in general.
The core Pacemaker team is made up of full-time developers from Australia, Austria, Germany, and China. Contributions to the code or documentation are always welcome.
Currently Andrew Beekhof is the Pacemaker project lead.
Pacemaker is an Open Source, High Availability resource manager suitable for both small and large clusters.
Hardware and application failures can result in prolonged downtime and impact your bottom line.
In the event of a failure, resource managers like Pacemaker automatically initiate recovery and make sure your application is available from one of the remaning machines in the cluster.
Your users may never even know there was a problem.
If you've flown in Europe in the last few years, chances are you already have.
Deutsche Flugsicherung GmbH (DFS) uses Pacemaker with Heartbeat to ensure its air traffic control systems are always available.
DFS trusts Pacemaker with peoples' lives, so can you.
Pacemaker is resource agnostic, meaning anything that can be scripted can be made highly available (provided the script conforms to either the LSB or OCF standards)
Only if your applications or design require it, Pacemaker itself has no need for shared storage
Pacemaker supports the popular OCFS2 and GFS2 filesystems. As you'd expect, you can use them on top of real disks or network block devices like DRBD.
Pacemaker supports STONITH for ensuring data integrity and ensuring applications are only active on one host
Pacemaker ships as part of all recent Fedora, openSUSE, and SLES releases.
The project also makes the latest binaries available for Fedora, openSUSE, and EPEL-compatible distributions (RHEL, CentOS, Scientific Linux, etc).
See our install page for more details.
Any changes to Pacemaker's configuration are automatically replicated to other machines. The configuration is also versioned, so any offline machines will be updated when they return.
