Thomas, There was a need for me to run the latest cluster stuff on Debian 7. So I created a document for myself to use. I don't claim this doc to be the best way to go, but it works for me. I hope it will work for you as well.
Here is the doc's content: Software - libqb 0.17.0 - corosync 2.3.3 - cluster-glue 1.0.12 - resource-agents 3.9.5 - pacemaker 1.1.12 - crmsh 2.1.0 IMPORTANT: do this installation step-by-step as here, the order is significant. Pre-Configuration $ sudo apt-get install build-essential $ sudo apt-get install automake autoconf $ sudo apt-get install libtool $ sudo apt-get install pkg-config LIBQB (needed by Corosync) https://github.com/ClusterLabs/libqb/releases $ echo "0.17.0" > .tarball-version $ ./autogen.sh $ ./configure $ make $ sudo make install COROSYNC https://github.com/corosync/corosync/releases $ sudo apt-get install libnss3-dev $ echo "2.3.3" > .tarball-version $ ./autogen.sh $ ./configure $ make $ sudo make install CLUSTER-GLUE (node fencing plugins, an error reporting utility, and other reusable cluster components from the Linux HA project) http://hg.linux-ha.org/glue/archive/glue-1.0.12.tar.bz2 $ sudo apt-get install libaio-dev (!) install dependencies for pacemaker (below) before proceed $ ./autogen.sh $ ./configure --enable-fatal-warnings=no $ make $ sudo make install RESOURCE-AGENTS (Combined repository of OCF agents from the RHCS and Linux-HA projects) https://github.com/ClusterLabs/resource-agents/releases $ echo "3.9.5" > .tarball-version $ ./autogen.sh $ ./configure $ make $ sudo make install PACEMAKER https://github.com/ClusterLabs/pacemaker/releases $ sudo apt-get install uuid-dev $ sudo apt-get install libglib2.0-dev $ sudo apt-get install libxml2-dev $ sudo apt-get install libxslt1-dev $ sudo apt-get install libbz2-dev $ sudo apt-get install libncurses5-dev $ sudo addgroup --system haclient $ sudo adduser --system --no-create-home --ingroup haclient hacluster $ ./autogen.sh $ ./configure $ make $ sudo make install CRMSH https://github.com/crmsh/crmsh/releases $ sudo apt-get install python-lxml $ ./autogen.sh $ ./configure $ make $ sudo make install Thank you, Kostya On Thu, Jan 15, 2015 at 5:44 PM, Thomas Manninger <dbgtmas...@gmx.at> wrote: > Hi, > > i also compiled the pacemaker_mgmt. I can start the hb_gui, but i have no > server daemon? > I used git://github.com/ClusterLabs/pacemaker-mgmt.git as source. > > Is the server in another repo?? > > I used: > ./ConfigureMe configure > ./ConfigureMe make > checkinstall --fstrans=no ./ConfigureMe install > > regards > thomas > > *Gesendet:* Donnerstag, 15. Januar 2015 um 15:16 Uhr > *Von:* "Ken Gaillot" <kgail...@redhat.com> > *An:* pacemaker@oss.clusterlabs.org > *Betreff:* Re: [Pacemaker] pacemaker-remote debian wheezy > On 01/15/2015 08:18 AM, Kristoffer Grönlund wrote: > > Thomas Manninger <dbgtmas...@gmx.at> writes: > > > >> Hi, > >> I compiled the latest libqb, corosync and pacemaker from source. > >> Now there is no crm command available? Is there another standard > >> shell? > >> Should i use crmadmin? > >> Thanks! > >> Regards > >> Thomas > > > > You can get crmsh and build from source at crmsh.github.io, or try the > > .rpm packages for various distributions here: > > > > > https://build.opensuse.org/package/show/network:ha-clustering:Stable/crmsh > > Congratulations on getting that far, that's probably the hardest part :-) > > The crm shell was part of the pacemaker packages in Debian squeeze. It > was going to be separated into its own package for jessie, but that > hasn't made it out of sid/unstable yet, so it might not make it into the > final release. > > Since you've built everything else from source, that's probably easiest, > but if you want to try ... > > For the rpm mentioned above, have a look at alien > (https://wiki.debian.org/Alien). crmsh is a standalone package so > hopefully it would work; I wouldn't try alien for something as > complicated as all the rpm's that go into a pacemaker install. > > You could try backporting the sid package > https://packages.debian.org/source/sid/crmsh but I suspect the > dependencies would get you. > > In theory the crm binary from the squeeze packages should work with the > newer pacemaker, if you can straighten out the library dependencies. > > Or you can use the crm*/cib* command-line tools that come with pacemaker > if you don't mind the lower-level approach. > > _______________________________________________ > Pacemaker mailing list: Pacemaker@oss.clusterlabs.org > http://oss.clusterlabs.org/mailman/listinfo/pacemaker > > Project Home: http://www.clusterlabs.org > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > Bugs: http://bugs.clusterlabs.org > > _______________________________________________ > Pacemaker mailing list: Pacemaker@oss.clusterlabs.org > http://oss.clusterlabs.org/mailman/listinfo/pacemaker > > Project Home: http://www.clusterlabs.org > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > Bugs: http://bugs.clusterlabs.org > >
_______________________________________________ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
