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. 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?). I also noticed there is heartbeat-ldirectord rpm and a libnet rpm. Would I need any of those? > > > > > > > > > > > 4) start heartbeat > > > 5) goto 1 > > > > > > :-) > > > > > > > > > > > I am upgrading from 2.0.8 to 2.1.3, Linux Red Hat 5 (production > > servers > > > > will be CentOS 5.1). Also, I've seen a lot of talk on the email lists > > of > > > > the various parts to Heartbeat, as separate items (like Pacemaker, > > etc). > > > > Will simply grabbing the heartbeat tar file be enough to upgrade > > > > everything? > > > > > > Not anymore... the crm code has been removed from the heartbeat project. > > > The easiest way is to grab the rpms from: > > > > > http://download.opensuse.org/repositories/server:/ha-clustering/RHEL_5/ > > > > Is there a well defined set of instructions to upgrade from a version of > > heartbeat prior to splitting it out into multiple packages (in this case > > 2.0.8) to the new organization of 2.1.3? > > A regular "rpm -Uvh" _should_ work. If it doesn't, please let me know Will do... > > > Do these various packages > > install to the same location that the single package heartbeat installed > > to? > > For the most part, yes. > All the binaries are in the regular places. > > > > The page below will show you what you need to install: > > > http://clusterlabs.org/mw/Install#Heartbeat-Only_Package_List > _______________________________________________ > Linux-HA mailing list > [email protected] > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems > _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
