Principally it was driven by the community. There are a lot of features
corosync has over heartbeat. There was an effort started in 2008 to
merge the open source HA stacks and openais and heartbeat moved to
corosync, red hat's cluster suite is giving way to pacemaker. Those two
provide the best platform for long-term growth of open source clustering.
As for multi-DC support, watch the booth project. It's supposed to bring
stretch clustering to corosync + pacemaker.
digimer
On 08/07/13 19:37, David Lang wrote:
Why is corosync replacing heartbeat? it seems like there are a number of
things (like multi-datacenter operation) that have worked for heartbeat
for years that corosync lists as new or upcoming features.
David Lang
On Mon, 1 Jul 2013, Digimer wrote:
On 07/01/2013 07:06 AM, Parkirat wrote:
Hi,
What is the best and latest version of heartbeat + pacemaker tested
version.
Regards,
Parkirat Singh Bagga
Heartbeat 3+, however, it is no longer developed and there are no plans
to restart development in the future, though Linbit still maintains the
code base.
If you are starting a new project, you should use corosync + pacemaker.
As for what version is best, that depends on your needs and which distro
you are using.
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
--
Digimer
Papers and Projects: https://alteeve.ca/w/
What if the cure for cancer is trapped in the mind of a person without
access to education?
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
