apt-get install libnet-ldap-perl libnet-ssleay-perl libnet-ip-perl libnet-dns-perl libauthen-radius-perl libnet-imap-simple-perl libnet-imap-simple-ssl-perl libhtml-parser-perl libcrypt-ssleay-perl libfont-afm-perl libhtml-tree-perl libconvert-asn1-perl libmail-pop3client-perl libhtml-format-perl libhtml-tagset-perl libwww-perl libnet-libidn-perl libio-socket-ssl-perl

apt-get install libsocket6-perl libio-socket-inet6-perl linux-headers-2.6.26-2-amd64 pkg-config libxml2-dev libbz2-dev uuid-dev zlib1g-dev xsltproc libxslt1-dev libglib2.0-dev

First Steps

Setup a number of variables that we'll use throughout the build process. Adjust them to your needs.

 export PREFIX=/usr
 export LCRSODIR=$PREFIX/libexec/lcrso 
 export CLUSTER_USER=hacluster
 export CLUSTER_GROUP=haclient

Create a user and group for the cluster

 getent group ${CLUSTER_GROUP} >/dev/null || groupadd -r ${CLUSTER_GROUP}
 getent passwd ${CLUSTER_USER} >/dev/null || useradd -r -g ${CLUSTER_GROUP} -d /var/lib/heartbeat/cores/hacluster -s /sbin/nologin -c "cluster user" ${CLUSTER_USER}

 

Cluster Glue

Obtain the latest Cluster Glue sources, then create and initialize the build directory

 wget -O cluster-glue.tar.bz2 http://hg.linux-ha.org/glue/archive/tip.tar.bz2
 tar jxvf cluster-glue.tar.bz2
 cd Reusable-Cluster-Components-*

Or, if you want to fetch Cluster Glue directly from the Mercurial repository:

 hg clone http://hg.linux-ha.org/glue
 cd glue

Teach Cluster Glue about the machine it will run on

 ./autogen.sh && ./configure --prefix=$PREFIX  --with-daemon-user=${CLUSTER_USER} --with-daemon-group=${CLUSTER_GROUP}

Once configure reports success, simply execute

 make
 sudo make install

 

Resource Agents

Obtain the latest sources:

  wget -O resource-agents.tar.bz2 http://hg.linux-ha.org/agents/archive/tip.tar.bz2

Create and initialize the build directory

 tar jxvf resource-agents.tar.bz2
 cd Cluster-Resource-Agents-*

Teach Agents about the machine it will run on

 ./autogen.sh && ./configure --prefix=$PREFIX

Once configure reports success, simply execute

 make
 sudo make install

 

Heartbeat*

* You can skip this step if you prefer to use the OpenAIS/Corosync cluster stack.

Obtain the latest Heartbeat sources:

  wget -O heartbeat.tar.bz2 http://hg.linux-ha.org/dev/archive/tip.tar.bz2

Create and initialize the build directory

 tar jxvf heartbeat.tar.bz2
 cd Heartbeat-*

Teach Heartbeat about the machine it will run on

 ./bootstrap && ./configure --prefix=$PREFIX

Once configure reports success, simply execute

 make
 sudo make install

 

CoroSync*

*You can skip this step if you prefer to use the Heartbeat cluster stack.

CoroSync contains the infrastructure (such as interprocess communication and network protocols) that used to be part of OpenAIS. See the CoroSync FAQ entry for more details.

For the majority of Pacemaker users, it is simplest to think of CoroSync as simply a new version of OpenAIS without a bunch of stuff you weren't using anyway.

Grab the latest code from the CoroSync project which has all the required patches to support Pacemaker

  svn co http://svn.fedorahosted.org/svn/corosync/branches/flatiron/
  cd flatiron

Teach CoroSync about the machine it will run on

 ./autogen.sh && ./configure --prefix=$PREFIX --with-lcrso-dir=$LCRSODIR

Once configure reports success, simply execute

 make
 sudo make install

 

OpenAIS*

*You can skip this step if you prefer to use the Heartbeat cluster stack or don't plan on using GFS2 or OCFS2.

Although Pacemaker doesn't require the full OpenAIS stack (just CoroSync is sufficient), some cluster services do. These include:

* OCFS2
* GFS2
* cLVM 

In order to use any of the above services in a Pacemaker cluster, you'll need to install OpenAIS.

Grab the latest code from the OpenAIS project

 svn co http://svn.fedorahosted.org/svn/openais/branches/wilson
 cd wilson

Teach OpenAIS about the machine it will run on
 ./autogen.sh && ./configure --prefix=$PREFIX --with-lcrso-dir=$LCRSODIR

Once configure reports success, simply execute

 make
 sudo make install

 

Pacemaker

Obtain the latest Pacemaker sources:

 wget -O pacemaker.tar.bz2 http://hg.clusterlabs.org/pacemaker/stable-1.0/archive/tip.tar.bz2

You can obtain a specific release by substituting tip with Pacemaker-{version}. eg.

 wget -O pacemaker.tar.bz2 http://hg.clusterlabs.org/pacemaker/stable-1.0/archive/Pacemaker-1.0.5.tar.bz2

Alternatively, for people that want to update regularly, clone the underlying Mercurial repository:

 hg clone http://hg.clusterlabs.org/pacemaker/stable-1.0
 cd stable-1.0
 hg update -C stable-1.0

Create and initialize the build directory

 tar jxvf pacemaker.tar.bz2
 cd Pacemaker-1-0-*

Teach Pacemaker about the machine it will run on

 ./autogen.sh && ./configure --prefix=$PREFIX --with-lcrso-dir=$LCRSODIR

Once configure reports success, simply execute

 make
 sudo make install

for some reason this also appears to be necessary

 sudo ldconfig -v

be sure to first update LD_LIBRARY_PATH if you installed Pacemaker (or anything else) into a non-standard location.

 

GUI

Although I personally dislike the current GUI, it does appear to be getting better and many people seem to get value from it.

Similar to Pacemaker, you can get the latest sources from:

 http://hg.clusterlabs.org/pacemaker/pygui/archive/tip.tar.bz2

 

 

update-rc.d heartbeat defaults

cd /usr/etc
tar -cvzf ha.d.tar.gz ha.d/
rm -rfv ha.d/
ln -vs /etc/ha.d ha.d