[Linux-HA] Instructions for Rolling Upgrade missing?

[Andrew Beekhof]

On Thu, Apr 17, 2008 at 2:15 PM, Doug Knight <dknight at wsi.com> wrote:
> On Wed, 2008-04-16 at 12:15 -0500, btinsley wrote:
>
>  > >
>  > > >  > >  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
>  > >
>  >
>  > I upgraded from 2.0.7 on SLES10 with the pre-built 2.1.3 packages and the
>  > old heartbeat, heartbeat-stonith and heartbeat-pils packages were
>  > upgraded/removed without issue. I did have to sort out several dependencies
>  > on Python modules and a few other libraries I did not have installed (cairo,
>  > glade2, svg, etc).
>
>  Did you install the older versions via RPMs or from source? My original
>  installation is from source, no RPMs involved, so I wonder how
>  installing the latest from RPMs would react to that.

"should work"

you _might_ have some old CLI binaries floating around, buts thats not
related to the project split (the locations changed prior to that)