Re: [Pacemaker] recent stabilization changes to corosync and openais API/ABIs
On Sat, Apr 18, 2009 at 07:53, Steven Dake wrote: > Hello, > > Some people on these lists may be interested to know what is happening > with Corosync and OpenAIS ABIs as well as our schedules for 1.0. > > We are currently planning the following dates for our releases: > Corosync 1.0 - May 15, 2009 > OpenAIS 1.0 - June 1, 2009 > > We have made great progress and the code is seeing good stabilization. > Over the past few weeks, our community team has sanitized the corosync > ABI and APIs. Excellent. /me gets his compiler out... ___ Pacemaker mailing list Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Re: [Pacemaker] recent stabilization changes to corosync and openais API/ABIs
NOn Sat, 2009-04-18 at 09:04 +0300, Juha Heinanen wrote: > Steven Dake writes: > > > Some people on these lists may be interested to know what is happening > > with Corosync and OpenAIS ABIs as well as our schedules for 1.0. > > what is corosync and how is it related to openais? the figure on page > > http://www.clusterlabs.org/wiki/Main_Page > > does not contain a corosync box and the text has no reference to it. > > -- juha Many portions of openais were merged into Corosync including the parts that Pacemaker depends on. In the future, think of Pacemaker as running against the Corosync engine instead. Regards -steve ___ Pacemaker mailing list Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker
[Pacemaker] recent stabilization changes to corosync and openais API/ABIs
Steven Dake writes: > Some people on these lists may be interested to know what is happening > with Corosync and OpenAIS ABIs as well as our schedules for 1.0. what is corosync and how is it related to openais? the figure on page http://www.clusterlabs.org/wiki/Main_Page does not contain a corosync box and the text has no reference to it. -- juha ___ Pacemaker mailing list Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker
[Pacemaker] recent stabilization changes to corosync and openais API/ABIs
Hello, Some people on these lists may be interested to know what is happening with Corosync and OpenAIS ABIs as well as our schedules for 1.0. We are currently planning the following dates for our releases: Corosync 1.0 - May 15, 2009 OpenAIS 1.0 - June 1, 2009 We have made great progress and the code is seeing good stabilization. Over the past few weeks, our community team has sanitized the corosync ABI and APIs. Specifically the following types of changes were made to corosync: * A const qualifier was added to any parameter that was a constant buffer or struct * Any size parameter was changed from int/unsigned int, to size_t * Any buffer that was copied into in a calling function added a length parameter which has a size_t type. * All of the external headers had these changes applied as well as coroapi.h. No significant changes were made to the openais ABI, however, because of changes to internal apis, we are bumping the so major version requiring a recompile if you use the SA Forum APIs as dependencies or any corosync APIs. We are targeting a new release with these changes to be introduced into distributions that ship this software in early May. Regards -steve ___ Pacemaker mailing list Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker
