On Mon, Jun 02, 2014 at 06:31:09PM -0400, Digimer wrote:
> On 02/06/14 06:30 PM, Lars Marowsky-Bree wrote:
> >On 2014-06-02T12:04:23, Digimer <lists@alteeve.ca> wrote:
> >
> >>You should email Linbit (http://linbit.com) as they're the company that
> >>still supports the heartbeat package.
> >
> >For completeness, I doubt Linbit will support this version, since 2.1.4
> >from SLES 10 contains a number of backports from the pacemaker 0.7/1.0
> >series. While source code is obviously available, I'd not suggest to
> >inflict this on Linbit ;-)
> >
> >
> >Regards,
> > Lars
>
> I didn't think they would support it, but I wanted to leave that for
> Linbit to say (I've been wrong enough times before...)
Thanks, both of you ;-)
Yes, we maintain heartbeat.
We still occasionally bugfix (or even enhance) it if necessary.
That does not mean we support each and every legacy version of it
that happend to be bundled with some distribution at some point.
That's probably a matter of time and money,
and "political constraints" ...
If you really have to stay with whatever platform you have right now,
but need it to be "supported" for "a very long term":
as that is a SuSE platform, ask SuSE what they can offer.
If you are basically happy with what you have,
but need "just this one snag fixed",
describe your problem, and maybe someone will be able to
tell you what to do (but that won't go without metioning
in every second sentence that you should probably upgrade).
If you are about to set up a new cluster,
go with current software.
Heartbeat itself is currently 3.something,
in fact pending a new release tag since ages...
Appart from few but important bugfixes
and some minor improvements to the inner workings of it,
the main difference from heartbeat 2. to heartbeat 3 is,
that the "crm" (cluster resource manager) part of it
was split out (years ago) and became Pacemaker.
Depending on what you have now, what you are used to do,
what you feel most comfortable with, and what you want to achieve,
I see several options.
* you are used to haresources, and in fact want to still use that
-=> use current heartbeat 3.x packages,
and keep doing whatever you did until now
* you have been using "crm" with heartbeat 2.x
or at least you now want to start using it
-=> you should upgrade to "Pacemaker", which is "just"
the natural evolution of the heartbeat "crm" component,
even with the same lead developer still.
*several years* of evolution and improvements, in fact.
You have further options now:
* Keep the cluster communication and membership layer:
"heartbeat" (3.x) + pacemaker
* Change the cluster communication and membership layer:
"corosync" (2.x) + pacemaker
(and more, like cman and corosync 1.x...)
Recommendation for new clusters:
go with pacemaker (1.1.12 will be release soon)
and corosync (2.3.3 is it now?).
That's also about what you will get with current distributions
(rhel7, sles12).
(Though we at Linbit are still happy
with heartbeat + pacemaker as well).
--
: Lars Ellenberg
: LINBIT | Your Way to High Availability
: DRBD/HA support and consulting http://www.linbit.com
DRBD® and LINBIT® are registered trademarks of LINBIT, Austria.
_______________________________________________
Linux-HA mailing list
Linux-HA@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha See also:
http://linux-ha.org/ReportingProblems