Re: [Pacemaker] Recommended versions for the cluster stack?

2009-10-13 Thread Andrew Beekhof
Feel like adding that to the wiki?

On Tue, Oct 13, 2009 at 7:04 PM, Jonathan  wrote:
> Thomas Georgiou wrote:
>> I do not know what the recommended versions are, but I wrote ebuilds
>> for the pacemaker/corosync cluster stack with the latest versions that
>> were available at the time.  They are located here
>> http://code.tjhsst.edu/vm-overlay/vm-overlay.
> Unfortunately, I was not aware that those existed. However, I am going
> to take the recommendation NOT to use corosync yet (which sucks, as I'm
> not sure the rest of my stack will compile without it yet)
>>   I believe there might
>> be a small bug in the permissions in the pacemaker ebuild, but I do
>> not remember if I fixed it.  We are currently using the ebuilds in a
>> testing environment running semi-production services (secondary
>> mailserver, nameserver).  However, we do not have need of dlm, drbd,
>> or ocfs2 yet.  If you do use ebuilds, please respond with what you
>> used, or if you modify mine, how you modified them.
>>
>> Thomas Georgiou
>>
>> P.S. Now I see you already have things installed.  Did you install
>> them by hand, or through ebuilds?
>>
>>
> I built them all by hand. I'm not that handy with making ebuilds yet,
> and the packages in the standard tree are ancient.
>
> I used some instructions I found on the net as a starting point, but had
> to go on my own from there.
> Needless to say, it was a bit of a challenge, trying to get everything
> latest and greatest to build together.
>
> The bigest problems were with dlm (needed for ocfs2) and ocfs2, in
> particular getting them to build their pacemaker agents. (dlm_controld
> and ocfs2_controld)
>
> I have attached my notes. I was going to put together a HOWTO when I was
> done (or maybe some ebuilds), but I want to get the setup stable first.
>
> Some of the steps in my notes may no longer be relevant, as newer
> versions are available for some packages  (eg: ocfs2-tools)
>
> Thanks!
>
> Jonathan
>
> --
> J. deBoer Computer Consulting.
> 42 Birchmont Dr.
> Leduc, AB.
> T9E-8S4
> cell: 780-717-0669
>
>
> echo "dev-libs/nss" >> /etc/portage/package.keywords
> echo "dev-libs/nss utils" >> /etc/portage/package.use
> emerge dev-libs/nss
>
> Heartbeat/Corosync/OpenAIS/Pacemaker
> export PREFIX=/usr/local
> export LCRSODIR=$PREFIX/libexec/lcrso
> export STACKS_SUPPORTED="--with-ais --without-heartbeat"
>
> Heartbeat:
> archive at http://hg.linux-ha.org/dev/archive/tip.tar.bz2
> ./ConfigureMe bootstrap --prefix=$PREFIX
> make
> make install
>
> Corosync (>=1.0.0, only needed if using OpenAIS >= 1.0.0) :
> Get the latest corosync from SVN or pacemaker won't compile
> svn checkout http://svn.fedorahosted.org/svn/corosync/trunk corosync
> ./autogen.sh --prefix=$PREFIX
> ./configure --prefix=$PREFIX --with-lcrso-dir=$LCRSODIR
> make
> make install
> #cp init/generic /etc/init.d/corosync
>
> ln -s /usr/local/etc/corosync /etc/corosync
> echo "PKG_CONFIG_PATH=/usr/local/lib/pkgconfig" >> /etc/env.d/05pkg-config
> env-update
> source /etc/profile
>
>
> #OpenAIS (< 1.0.0) :
> #make PREFIX=$PREFIX LCRSODIR=$LCRSODIR
> #make install PREFIX=$PREFIX LCRSODIR=$LCRSODIR STATICLIBS=NO
>
> OpenAIS (>=1.0.0) :
> svn checkout http://svn.fedorahosted.org/svn/openais/trunk openais
> ./autogen.sh --prefix=$PREFIX
> ./configure --prefix=$PREFIX --with-lcrso-dir=$LCRSODIR
> make
> make install
> cp init/generic /etc/init.d/openais
> edit /etc/init.d/openais
>        between lines 50 and 51 (before prog is executed), add a line:
>        export 
> COROSYNC_DEFAULT_CONFIG_IFACE="openaisserviceenable:openaisparser"
>
> add 21openais file to /etc/env.d:
> echo "LDPATH=\"/usr/local/lib/openais\"" >> /etc/env.d/21openais
>
> env-update
> source /etc/profile
>
> Pacemaker :
> wget http://hg.clusterlabs.org/pacemaker/stable-1.0/archive/tip.tar.bz2
> ./ConfigureMe bootstrap --prefix=$PREFIX --with-lcrso-dir=$LCRSODIR 
> $STACKS_SUPPORTED
> make
> make install
>
> LibLogThread from Cluster:
> wget https://fedorahosted.org/releases/c/l/cluster/cluster-3.0.0.tar.gz
> #./configure --openaisincdir=/usr/local/include 
> --openaislibdir=/usr/local/lib/openais --enable_pacemaker
> ./configure --openaisincdir=/usr/local/include 
> --openaislibdir=/usr/local/lib/openais --corosyncincdir=/usr/local/include 
> --corosynclibdir=/usr/local/lib/corosync --enable_pacemaker
> cd common/liblogthread
> make
> make install
>
> DLM and friends: (after openais) :
> Download from http://sources.redhat.com/cluster/wiki/
> download the latest DLM from GIT
> ./autogen.sh --prefix=/usr/local
> If the command does not work, you may need to modify configure.ac
>        change AC_PREREQ([[2.63b]) to be AC_PREREQ([2.63])
>        comment out LT_PREREQ and LT_INIT
> ./configure --prefix=/usr/local --enable-pacemaker --disable-cman
> change line 68 of group/dlm_controld/pacemaker.c to be:
>        log_error("Connection to our AIS plugin (%d) failed", PCMK_SERVICE_ID);
> make
> make install
>
> Setup LSB init scripts
> mkdir -p /lib/lsb
> cp init-fu

Re: [Pacemaker] Recommended versions for the cluster stack?

2009-10-13 Thread Andrew Beekhof
On Tue, Oct 13, 2009 at 7:49 PM, Jonathan  wrote:
>> There shouldn't be any dependency between ocfs2 and openais.
>>
> It was a while ago. The project has been on hold for a month or so, but
> IIRC, the problem was that the control deamons (dlm_controld.pcmk and
> ocfs2_controld.pcmk) had some dependancies on openais, and wouldn't compile.

oh, i think the "master" branch assumes corosync.

>>
>>> I will try downgrading, and see if I can get it working again.
>>>
>>> Do we know how long it will be before  Pacemaker is stable on openais 1.0+ ?
>>>
>>
>> A few weeks.
>> The patches that make it work at all exist, but they're not in any
>> released version.
>> Nor has the combined stack been tested thoroughly.
>>
> Do you think it would be worthwhile waiting for the new version? It's my

If you can hold out, it might be easier (rather than learning and unlearning).

> understanding that I should be able to upgrade a running cluster from
> openais 0.80.5 to 1.0.0+. How difficult is that likely to be?

Its allegedly quite easy. Never done it myself though.

___
Pacemaker mailing list
Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker


Re: [Pacemaker] Recommended versions for the cluster stack?

2009-10-13 Thread Jonathan
Andrew Beekhof wrote:
> On Tue, Oct 13, 2009 at 6:39 PM, Jonathan  wrote:
>   
>> Andrew Beekhof wrote:
>> 
 openais

 
>>> 0.80.5
>>> definitely do NOT use 1.x at this point.
>>>
>>>   
>> This is likely the source of my problems. I am currently using 1.0.x+
>> and corosync.
>> 
>
> Yep. You can't shut down cluster nodes at all with that version.
>
>   
>> It was a while ago that I had to switch, but IIRC, I needed to upgrade
>> to get ocfs2 (1.4.2) working properly.
>> 
>
> There shouldn't be any dependency between ocfs2 and openais.
>   
It was a while ago. The project has been on hold for a month or so, but
IIRC, the problem was that the control deamons (dlm_controld.pcmk and
ocfs2_controld.pcmk) had some dependancies on openais, and wouldn't compile.
>   
>> I will try downgrading, and see if I can get it working again.
>>
>> Do we know how long it will be before  Pacemaker is stable on openais 1.0+ ?
>> 
>
> A few weeks.
> The patches that make it work at all exist, but they're not in any
> released version.
> Nor has the combined stack been tested thoroughly.
>   
Do you think it would be worthwhile waiting for the new version? It's my
understanding that I should be able to upgrade a running cluster from
openais 0.80.5 to 1.0.0+. How difficult is that likely to be?

Thanks

-- 
J. deBoer Computer Consulting.
42 Birchmont Dr.
Leduc, AB.
T9E-8S4
cell: 780-717-0669 


___
Pacemaker mailing list
Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker


Re: [Pacemaker] Recommended versions for the cluster stack?

2009-10-13 Thread Jonathan
Thomas Georgiou wrote:
> I do not know what the recommended versions are, but I wrote ebuilds
> for the pacemaker/corosync cluster stack with the latest versions that
> were available at the time.  They are located here
> http://code.tjhsst.edu/vm-overlay/vm-overlay.
Unfortunately, I was not aware that those existed. However, I am going
to take the recommendation NOT to use corosync yet (which sucks, as I'm
not sure the rest of my stack will compile without it yet)
>   I believe there might
> be a small bug in the permissions in the pacemaker ebuild, but I do
> not remember if I fixed it.  We are currently using the ebuilds in a
> testing environment running semi-production services (secondary
> mailserver, nameserver).  However, we do not have need of dlm, drbd,
> or ocfs2 yet.  If you do use ebuilds, please respond with what you
> used, or if you modify mine, how you modified them.
>
> Thomas Georgiou
>
> P.S. Now I see you already have things installed.  Did you install
> them by hand, or through ebuilds?
>
>   
I built them all by hand. I'm not that handy with making ebuilds yet,
and the packages in the standard tree are ancient.

I used some instructions I found on the net as a starting point, but had
to go on my own from there.
Needless to say, it was a bit of a challenge, trying to get everything
latest and greatest to build together.

The bigest problems were with dlm (needed for ocfs2) and ocfs2, in
particular getting them to build their pacemaker agents. (dlm_controld
and ocfs2_controld)

I have attached my notes. I was going to put together a HOWTO when I was
done (or maybe some ebuilds), but I want to get the setup stable first.

Some of the steps in my notes may no longer be relevant, as newer
versions are available for some packages  (eg: ocfs2-tools)

Thanks!

Jonathan

-- 
J. deBoer Computer Consulting.
42 Birchmont Dr.
Leduc, AB.
T9E-8S4
cell: 780-717-0669 

echo "dev-libs/nss" >> /etc/portage/package.keywords
echo "dev-libs/nss utils" >> /etc/portage/package.use
emerge dev-libs/nss

Heartbeat/Corosync/OpenAIS/Pacemaker
export PREFIX=/usr/local
export LCRSODIR=$PREFIX/libexec/lcrso 
export STACKS_SUPPORTED="--with-ais --without-heartbeat"

Heartbeat:
archive at http://hg.linux-ha.org/dev/archive/tip.tar.bz2
./ConfigureMe bootstrap --prefix=$PREFIX
make
make install

Corosync (>=1.0.0, only needed if using OpenAIS >= 1.0.0) :
Get the latest corosync from SVN or pacemaker won't compile
svn checkout http://svn.fedorahosted.org/svn/corosync/trunk corosync
./autogen.sh --prefix=$PREFIX
./configure --prefix=$PREFIX --with-lcrso-dir=$LCRSODIR
make
make install
#cp init/generic /etc/init.d/corosync

ln -s /usr/local/etc/corosync /etc/corosync
echo "PKG_CONFIG_PATH=/usr/local/lib/pkgconfig" >> /etc/env.d/05pkg-config
env-update
source /etc/profile


#OpenAIS (< 1.0.0) :
#make PREFIX=$PREFIX LCRSODIR=$LCRSODIR
#make install PREFIX=$PREFIX LCRSODIR=$LCRSODIR STATICLIBS=NO 

OpenAIS (>=1.0.0) :
svn checkout http://svn.fedorahosted.org/svn/openais/trunk openais
./autogen.sh --prefix=$PREFIX
./configure --prefix=$PREFIX --with-lcrso-dir=$LCRSODIR
make
make install
cp init/generic /etc/init.d/openais
edit /etc/init.d/openais
between lines 50 and 51 (before prog is executed), add a line:
export 
COROSYNC_DEFAULT_CONFIG_IFACE="openaisserviceenable:openaisparser"

add 21openais file to /etc/env.d: 
echo "LDPATH=\"/usr/local/lib/openais\"" >> /etc/env.d/21openais

env-update
source /etc/profile

Pacemaker :
wget http://hg.clusterlabs.org/pacemaker/stable-1.0/archive/tip.tar.bz2
./ConfigureMe bootstrap --prefix=$PREFIX --with-lcrso-dir=$LCRSODIR 
$STACKS_SUPPORTED
make
make install

LibLogThread from Cluster:
wget https://fedorahosted.org/releases/c/l/cluster/cluster-3.0.0.tar.gz
#./configure --openaisincdir=/usr/local/include 
--openaislibdir=/usr/local/lib/openais --enable_pacemaker
./configure --openaisincdir=/usr/local/include 
--openaislibdir=/usr/local/lib/openais --corosyncincdir=/usr/local/include 
--corosynclibdir=/usr/local/lib/corosync --enable_pacemaker
cd common/liblogthread
make
make install

DLM and friends: (after openais) :
Download from http://sources.redhat.com/cluster/wiki/
download the latest DLM from GIT
./autogen.sh --prefix=/usr/local
If the command does not work, you may need to modify configure.ac
change AC_PREREQ([[2.63b]) to be AC_PREREQ([2.63])
comment out LT_PREREQ and LT_INIT
./configure --prefix=/usr/local --enable-pacemaker --disable-cman
change line 68 of group/dlm_controld/pacemaker.c to be:
log_error("Connection to our AIS plugin (%d) failed", PCMK_SERVICE_ID);
make
make install

Setup LSB init scripts
mkdir -p /lib/lsb
cp init-functions  /lib/lsb/
cp rc.status /lib/lsb

ocfs2-tools 1.4.2+
./autogen.sh --prefix=/usr/local
in Config.make
add -lpthread to COM_ERR_LIBS
modify ./ocfs2_controld/Makefile
set line:
PCMK_INCLUDES = -I/usr/local/include/pacemaker 
-I/usr/local/include/heartbeat -I/usr/include/li

Re: [Pacemaker] Recommended versions for the cluster stack?

2009-10-13 Thread Andrew Beekhof
On Tue, Oct 13, 2009 at 6:39 PM, Jonathan  wrote:
> Andrew Beekhof wrote:
>>> openais
>>>
>>
>> 0.80.5
>> definitely do NOT use 1.x at this point.
>>
> This is likely the source of my problems. I am currently using 1.0.x+
> and corosync.

Yep. You can't shut down cluster nodes at all with that version.

> It was a while ago that I had to switch, but IIRC, I needed to upgrade
> to get ocfs2 (1.4.2) working properly.

There shouldn't be any dependency between ocfs2 and openais.

>
> I will try downgrading, and see if I can get it working again.
>
> Do we know how long it will be before  Pacemaker is stable on openais 1.0+ ?

A few weeks.
The patches that make it work at all exist, but they're not in any
released version.
Nor has the combined stack been tested thoroughly.

___
Pacemaker mailing list
Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker


Re: [Pacemaker] Recommended versions for the cluster stack?

2009-10-13 Thread Jonathan
Andrew Beekhof wrote:
> On Sat, Oct 10, 2009 at 1:13 AM, Jonathan  wrote:
>   
>> Hello:
>>
>> I'm trying to set up a pacemaker/openais cluster on Gentoo, which
>> requires building the entire stack from source.
>> I have everything running, but the stack has some strange stability
>> issues, (in particular during a reboot), that I'm sure are due to some
>> version incompatibilities.
>>
>> What software versions comprise the recommended stack for Pacemaker?
>> (I.E. what versions are currently tested and/or in production?)
>>
>> In particular, I  am interested in the version numbers of:
>>
>> pacemaker
>> 
>
> latest and greatest :-)
> or 1.0.5
>   
I am using 1.0.4+ right now, I will look at upgrading.
>   
>> openais
>> 
>
> 0.80.5
> definitely do NOT use 1.x at this point.
>   
This is likely the source of my problems. I am currently using 1.0.x+
and corosync.
It was a while ago that I had to switch, but IIRC, I needed to upgrade
to get ocfs2 (1.4.2) working properly.

I will try downgrading, and see if I can get it working again.

Do we know how long it will be before  Pacemaker is stable on openais 1.0+ ?
>   
>> libdlm
>> 
>
> the very latest from http://git.fedorahosted.org/git/?p=dlm.git;a=summary
>
>   
Thanks, glad to hear the latest is stable.
>> drbd
>> 
>
> whatever linbit is recommending probably the latest release.
>
>   
Thought so.
>> and ocfs2
>> 
>
> you'd have to ask the oracle guys
>
>   
I see there is a newer version of their tools package available. I will
upgrade.

Thanks!

Jonathan


-- 
J. deBoer Computer Consulting.
42 Birchmont Dr.
Leduc, AB.
T9E-8S4
cell: 780-717-0669 


___
Pacemaker mailing list
Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker


Re: [Pacemaker] Recommended versions for the cluster stack?

2009-10-11 Thread Andrew Beekhof
On Sat, Oct 10, 2009 at 1:13 AM, Jonathan  wrote:
> Hello:
>
> I'm trying to set up a pacemaker/openais cluster on Gentoo, which
> requires building the entire stack from source.
> I have everything running, but the stack has some strange stability
> issues, (in particular during a reboot), that I'm sure are due to some
> version incompatibilities.
>
> What software versions comprise the recommended stack for Pacemaker?
> (I.E. what versions are currently tested and/or in production?)
>
> In particular, I  am interested in the version numbers of:
>
> pacemaker

latest and greatest :-)
or 1.0.5

> openais

0.80.5
definitely do NOT use 1.x at this point.

> libdlm

the very latest from http://git.fedorahosted.org/git/?p=dlm.git;a=summary

> drbd

whatever linbit is recommending probably the latest release.

> and ocfs2

you'd have to ask the oracle guys

>
> If my software versions aren't too far off, I'll post my logs after the
> weekend. It's been a frustrating afternoon trying to get my cluster back up.
>
> Thanks!
>
> Jonathan
>
> --
> J. deBoer Computer Consulting.
> 42 Birchmont Dr.
> Leduc, AB.
> T9E-8S4
> cell: 780-717-0669
>
>
> ___
> Pacemaker mailing list
> Pacemaker@oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>

___
Pacemaker mailing list
Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker


Re: [Pacemaker] Recommended versions for the cluster stack?

2009-10-09 Thread Thomas Georgiou
I do not know what the recommended versions are, but I wrote ebuilds
for the pacemaker/corosync cluster stack with the latest versions that
were available at the time.  They are located here
http://code.tjhsst.edu/vm-overlay/vm-overlay.  I believe there might
be a small bug in the permissions in the pacemaker ebuild, but I do
not remember if I fixed it.  We are currently using the ebuilds in a
testing environment running semi-production services (secondary
mailserver, nameserver).  However, we do not have need of dlm, drbd,
or ocfs2 yet.  If you do use ebuilds, please respond with what you
used, or if you modify mine, how you modified them.

Thomas Georgiou

P.S. Now I see you already have things installed.  Did you install
them by hand, or through ebuilds?

On Fri, Oct 9, 2009 at 7:13 PM, Jonathan  wrote:
> Hello:
>
> I'm trying to set up a pacemaker/openais cluster on Gentoo, which
> requires building the entire stack from source.
> I have everything running, but the stack has some strange stability
> issues, (in particular during a reboot), that I'm sure are due to some
> version incompatibilities.
>
> What software versions comprise the recommended stack for Pacemaker?
> (I.E. what versions are currently tested and/or in production?)
>
> In particular, I  am interested in the version numbers of:
>
> pacemaker
> openais
> libdlm
> drbd
> and ocfs2
>
> If my software versions aren't too far off, I'll post my logs after the
> weekend. It's been a frustrating afternoon trying to get my cluster back up.
>
> Thanks!
>
> Jonathan
>
> --
> J. deBoer Computer Consulting.
> 42 Birchmont Dr.
> Leduc, AB.
> T9E-8S4
> cell: 780-717-0669
>
>
> ___
> Pacemaker mailing list
> Pacemaker@oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>

___
Pacemaker mailing list
Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker


[Pacemaker] Recommended versions for the cluster stack?

2009-10-09 Thread Jonathan
Hello:

I'm trying to set up a pacemaker/openais cluster on Gentoo, which
requires building the entire stack from source.
I have everything running, but the stack has some strange stability
issues, (in particular during a reboot), that I'm sure are due to some
version incompatibilities.

What software versions comprise the recommended stack for Pacemaker?
(I.E. what versions are currently tested and/or in production?)

In particular, I  am interested in the version numbers of:

pacemaker
openais
libdlm
drbd
and ocfs2

If my software versions aren't too far off, I'll post my logs after the
weekend. It's been a frustrating afternoon trying to get my cluster back up.

Thanks!

Jonathan

-- 
J. deBoer Computer Consulting.
42 Birchmont Dr.
Leduc, AB.
T9E-8S4
cell: 780-717-0669 


___
Pacemaker mailing list
Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker