On Wed, Apr 16, 2008 at 7:37 PM, Doug Knight <[EMAIL PROTECTED]> wrote: > Comments below... > > > > On Wed, 2008-04-16 at 19:05 +0200, Andrew Beekhof wrote: > > > On Wed, Apr 16, 2008 at 5:39 PM, Doug Knight <[EMAIL PROTECTED]> wrote: > > > Could you clarify some things? See below: > > > > > > > > > On Wed, 2008-04-16 at 17:06 +0200, Andrew Beekhof wrote: > > > > > > > On Wed, Apr 16, 2008 at 4:22 PM, Doug Knight <[EMAIL PROTECTED]> > wrote: > > > > > List, > > > > > I am in the process of planning heartbeat upgrades for our > prototype > > > > > servers, in preparation for configuring our new production > systems. As > > > > > part of upgrading heartbeat, I wanted to plan out a process for > > > > > upgrading production systems with little or no impact to services > > > > > availability. I found the following Rolling Upgrade page on the > Linux-HA > > > > > website: > > > > > > > > > > http://www.linux-ha.org/RollingUpgrade > > > > > > > > > > But there are no instructions. There is a link to the Transparent > > > > > Upgrade page, which has instructions for that method (and which > may be a > > > > > more viable route for my upgrades anyway). However, I'd really > like to > > > > > see the instructions for doing a Rolling Upgrade, before I make my > > > > > decision which one to implement. Does anyone have the instructions > (or > > > > > could point me to them) for a Rolling Upgrade? > > > > > > > > 1) pick a node > > > > 2) stop heartbeat > > > > 3) upgrade heartbeat (and/or OS) software > > > > > > Upgrade heartbeat, install pacemaker? Does the heartbeat src.rpm include > > > the heartbeat-common and heartbeat-resources packages, or do I need to > > > get them elsewhere? > > > > Why not use the pre-built ones? > > In previous experience I had to build from source.
RHEL/CentOS support in the build service is reasonably new > We were using RHEL5 > Beta, under the 64 bit arch. In the future we plan on using CentOS 32 > bit, since we ran into a lot of compatibility issues with various > applications, and I don't like having some things in 32 bit directories > and some in 64 bit ones (e.g. /usr/lib vs /usr/lib64). With that said, I > believe I will try your suggestion and use the binary RPMs first. > > I pulled down: > heartbeat-2.1.3-21.1.i386.rpm > heartbeat-common-2.1.3-21.1.i386.rpm > heartbeat-resources-2.1.3-21.1.i386.rpm > pacemaker-heartbeat-0.6.2-14.1.i386.rpm > pacemaker-pygui-1.2-6.6.i386.rpm > > Based on the dependencies I'll install them in this order: > heartbeat-resources, heartbeat-common, pacemaker-heartbeat, heartbeat, > pacemaker-pygui (is this the GUI packaged with the original heartbeat?). no - it needs pacemaker librbaries to build and so is provided by pacemaker-pygui > I also noticed there is heartbeat-ldirectord rpm and a libnet rpm. Would > I need any of those? libnet "probably", heartbeat-ldirectord is optional _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
