On 04/25/2010 11:39 AM, Smaïne Kahlouch wrote: > Hi everyone, > > I know the question has already been asked. > see http://lists.linux-ha.org/pipermail/linux-ha/2009-March/036725.html > The answer is however not clear for me and i would like to have other > opinions. > > Do we have to move from Heartbeat to OpenAIS ? Now or in the future ?
You definitely don't have to, i.e. there is no obligation. Both messaging layers are supported both by the Pacemaker project, and commercially (to varying degrees, of course, depending on who you buy support from) and will remain so for the foreseeable future. There are, however, features in Pacemaker that require OpenAIS which will work only with Corosync, not Heartbeat. Those features are concerned with the distributed lock managers used by cLVM (but not regular LVM), GFS/GFS2, and OCFS2. If you need that functionality, you must select OpenAIS/Corosync. If you do not, you're free to choose. > What are the differences between these two project ? Too many to mention, in terms of history, participation, and corporate sponsorship. Please peruse the documentation at www.corosync.org and www.linux-ha.org. > Will the project heartbeat continue or will be replaced by > OpenAIS/Corosync. Yes and yes. :) Heartbeat will continue in maintenance mode for several years, and from what Andrew has said up to this point, he has no plans to drop Heartbeat support in Pacemaker in the foreseeable future. So Pacemaker can be expected to support both stacks. Once Corosync has either exceeded Heartbeat's functionality by leaps and bounds or has completely displaced Heartbeat (that's a decision that the community makes), Heartbeat maintenance will be discontinued. In other words: as long as it makes sense to continue Heartbeat, it will. The timeframe we are talking about is definitely years, not months. Hope this helps. Cheers, Florian
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
