Install
From ClusterLabs
Contents
|
READ ME FIRST
Please do not attempt to install Pacemaker with anything less than Heartbeat 3.0.0
Since Pacemaker was originally part of Heartbeat, it naturally includes many of the files contained in Heartbeat 2.x Most package managers including YUM, RPM and DEB will complain extremely loudly if you try this.
Versions and Compatibilty
The list of current and supported versions of Pacemaker are available at the Releases page. If you already have Pacemaker installed, please read the documentation on upgrading Pacemaker before following any of the instructions here.
| Version | Last Release | First Released | Last Released |
|---|---|---|---|
| 0.7 | 0.7.3 | June 25, 2008 | Sep 22, 2008 |
| 0.6 | 0.6.7 | Jan 16, 2008 | Dec 15, 2008 |
Binary Packages
RPM
In the beginning, the project used to offer binary packages for the most common distributions. However these days, most distributions do a good job of keeping up-to-date so there was little need to continue.
Pacemaker is currently available on:
- Fedora,
- OpenSUSE,
- RHEL,
- CentOS and Scientific Linux,
- Ubuntu,
- Gentoo,
- Arch,
- Many more
See http://clusterlabs.org/quickstart.html for some distribution specific guides on getting a basic cluster up and running.
Installing on Fedora
As of Fedora-12, Pacemaker is part of the distribution and updates are usually quickly available via the regular channels. There is nothing extra to download, just run:
yum install -y pacemaker corosync
Installing on RHEL-6
Pacemaker has been available as part of RHEL since 6.0 as part of the High Availability (HA) add-on.
While this is an important step, it has created some challenges, because:
- Red Hat funds much of Pacemaker's development, so we prefer to make packages available via their official channels rather than the community site
- Pacemaker is currently listed as Tech Preview (TP) and therefor unsupported by Red Hat
- The HA add-on costs money
Why should I pay for something if I still wont be supported?
Valid question, but there are still plenty of other software (such as corosync openais, cman, and fencing agents) that is supported if you buy the add-on. You also get a warm fuzzy feeling for supporting continued Pacemaker development.
Even if the lack of support is a deal breaker, consider buying at least one copy of the add-on. You'll get software updates for the entire stack and it helps Red Hat gauge the demand for Pacemaker - which could conceivably help it become supported sooner.
When Community Support is Enough
If you're really not interested in support, you have a number of options available:
- Install from the RHEL install media
- Install from the CentOS or Scientific Linux repos
- Download and rebuild the necessary SRPMs from the Red Hat FTP server
The CentOS approach
Add it as a disabled repository:
cat < /etc/yum.repo.d/centos.repo [centos-6-base] name=CentOS-$releasever - Base mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=os enabled=0 #baseurl=http://mirror.centos.org/centos/$releasever/os/$basearch/ EOF
And then install Pacemaker by running:
yum install --enablerepo=centos-6-base pacemaker
Yum then takes care of all the dependencies and (somehow) only uses the pacemaker/corosync/etc packages from CentOS while the rest comes from Red Hat.
Installing on RHEL-6 Compatible Distributions: CentOS, Scientific Linux, etc
As of version 6 of these distros, Pacemaker is part of the distribution and updates are usually quickly available via the regular channels. There is nothing extra to download, just run:
yum install -y pacemaker corosync
Installing on RHEL-5 Compatible Distributions: CentOS, Scientific Linux, etc
First add the Cluster Labs repo:
wget -O /etc/yum.repos.d/pacemaker.repo http://clusterlabs.org/rpm-next/epel-5/clusterlabs.repo
And finally, install Pacemaker:
yum install -y pacemaker corosync
Installing on openSUSE
openSUSE uses zypper instead of yum, but the procedure is much the same:
zypper install pacemaker corosync
Re-Building RPMs for Other Architectures
If your packages are not available for your distro/version, you can rebuild the published rpms to meet your needs. To do this:
- Download the src.rpm
Browse to http://clusterlabs.org/rpm-next/rhel-6/src/ and download the most recent version of Pacemaker. - Tell RPM to rebuild the package
rpmbuild --rebuild pacemaker-[0-9].*.src.rpm
- Install the result
rpm -Uvh /usr/src/packages/RPMS/i586/pacemaker-[0-9]*.rpm
Debian
For current stable versions of Debian, Pacemaker is available from Debian backports.
To install, use your favorite editor to add something like the following to /etc/apt/sources.list
deb http://backports.debian.org/debian-backports squeeze-backports main
Once this has been completed, run:
apt-get update
Finally, to install Pacemaker simply decide which stack you wish to use and run
apt-get -t squeeze-backports install pacemaker corosync
or
apt-get -t squeeze-backports install pacemaker heartbeat
For detailed installation instructions, refer to the Debian Lenny HowTo. If you run into any issues installing, updating, or using these packages, please let us know on the mailing list.
Please note: currently, no direct, "rolling upgrade" path exists for Debian users to move from the woefully outdated Heartbeat 2.1.3 with built-in CRM that continues to be part of the official Debian package repositories. Providing this upgrade path is something that Martin has on his to-do list, but it's a little more challenging than it looks to an observer.
Ubuntu
As of Ubuntu 10.4 (Lucid Lynx), Pacemaker and all its dependancies are part of the distribution. Simply run:
aptitude install corosync pacemaker
or
aptitude install heartbeat pacemaker
Users of Ubuntu versions prior to 10.4 can either install the Debian packages, or try the ones from LaunchPad by adding
deb http://ppa.launchpad.net/ubuntu-ha/ppa/ubuntu karmic main deb-src http://ppa.launchpad.net/ubuntu-ha/ppa/ubuntu karmic main
to /etc/apt/sources.list before running the same aptitude command above.
Other
If no packages are available, you might need to install from source.
Next Steps
Once Pacemaker is installed, the next step is to configure your cluster stack. Check out our quickstart guides or the Initial Configuration page.
