On Thu, May 19, 2011 at 12:36 PM, Lars Ellenberg <[email protected]> wrote: > On Wed, May 18, 2011 at 05:21:35PM -0700, Vinay Nagrik wrote: >> Hello everybody, >> >> I am running Centos 5.2 with heartbeat 2.1.3 and we as a group run it on >> appliances and *it is readily not possible to suddenly upgrade heartbeat to >> a later version which runs pacemaker*. > > Oh yes you can. If you want to use the "cib" based "crmd" style > configuration, you will have to. Why do you think you can not? > > You cannot change the facts by asking the same question again. > > But if it helps to get the message across, please, anyone that wants to, > feel free to add > "Confirmed by"
The guy that wrote most of the stuff being discussed. Seriously, are we still having this conversation? Its two years since I wrote: http://www.mail-archive.com/[email protected]/msg12684.html and its even more true now. > to this thread. > > ;-) > > >> My requirement as a developer to explore possibilities to manage resource >> especially Apache web server in such a fashion that on a two node cluster if >> *on the active node the Apache service goes down then* the heartbeat should >> shut down that active node and transfer the control to other node, which has >> the Apache serviceable.. >> >> Could someone please tell me the literature, where I can get some >> configuration parameters. >> >> I know it can be done in a cib.xml file, which is part of heartbeat 2.1.3 >> and also some other utilities like cibadmin. > > If you, for what ever (non technical) reason you think you are stuck > with heartbeat 2.1.x, stay with haresources, possibly add "mon" into > your setup, and hope for the best. > > If you want to go "cib" and "crm", you absolutely have to use Pacemaker. > Whether you then use Pacemaker on top of heartbeat (3.0.x) or corosync > is an other decision, and unaffected by this. > > But please accept that Pacemaker is the very same CRMD (cluster resource > manager daemon) that came with heartbeat 2.1.x, only four (4!) years of > bug fixing and development later. > > So if you insist on using some known to be buggy 4 year old piece of > software, just because one component of it now goes by a different name, > I'm sorry, but you should not expect much help. > > I think we told you that already? > > > Still, you asked to be pointed to documentation. > > There is the section "Documentation For Older Releases" > http://www.clusterlabs.org/wiki/Documentation > > Which links to some relevant docs about 2.1.x. > > Just in case you absolutely love to hurt yourself > > ;-) > > -- > : 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 > [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
