> how does this fit the release schedule? The short answer is that it doesn't. The community generally does a pretty good job, heartbeat2 was a dead end that was put out of its misery years ago[1] and openais 0.80 was something like 5 years old when pacemaker started supporting it. Pacemaker 1.0 itself is almost 3 years old now iirc.
But long term support will always be hole that enterprise vendors fill with products like sles, rhel and ubuntu LTS. With limited resources, projects need to choose their battles. We can't be everything to everyone, so we let the enterprise distress do what they do best while we concentrate on improving the core software. [1] there were also unique circumstances that necessitated killing hb2 early Sent from my iPad On 13 Oct 2010, at 13:37, Dan Frincu <dfri...@streamwide.ro> wrote: > Hi, > > Yes, it sometime needs to be killed manually because the process hangs and > the restart operation never seems to end. Yet another reason to upgrade. > > All, > > Question: given the fact that this type of software usually gets installed on > a platform once and then usually goes into service for many years, on servers > where downtime should be kept to a minimum (gee, that's why you use a cluster > :)), how does this fit the release schedule? > > I mean, there are plenty of users out there with question related to > Heartbeat 2, openais-0.8.0, and so on and so forth, some environments cannot > be changed lightly, others, not at all, so what is the response to "this > feature doesn't work on that version of software?", upgrade? If so, at what > interval (keeping in mind that you probably want the stable packages on your > system)? > > I'm asking this because when I started working with openais, the latest > version available was 0.8.0 on some SUSE repos that aren't available anymore. > > Regards, > > Dan > > jiaju liu wrote: >> >> Hi, >> >> Depending on the openais version (please mention it) >> >> Hi >> Thank you for your reply my openais version is openais-0.80.5-15.1 >> pacemaker version is pacemaker-1.0.5-4.1. >> I use restart but it does not work. I found it could not stop >> >> >> this behavior could >> happen, I've seen it as well, on openais-0.8.0. What I've done to fix it >> was to restart the openais process via /etc/init.d/openais restart. And >> then it worked, however, this was one of the reasons I updated the >> packages to the latest versions of corosync, pacemaker, etc. The tricky >> part was doing the migration procedure for upgrading production servers >> >> without service downtime, but that's another story. >> >> >> > > -- > Dan FRINCU > Systems Engineer > CCNA, RHCE > Streamwide Romania > _______________________________________________ > Pacemaker mailing list: Pacemaker@oss.clusterlabs.org > http://oss.clusterlabs.org/mailman/listinfo/pacemaker > > Project Home: http://www.clusterlabs.org > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > Bugs: > http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
_______________________________________________ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
