[ClusterLabs] Corosync 3 release plans?

[Christine Caulfield]

On 24/09/18 13:12, Ferenc Wágner wrote:
> Jan Friesse <jfriesse at redhat.com> writes:
> 
>> Have you had a time to play with packaging current alpha to find out
>> if there are no issues? I had no problems with Fedora, but Debian has
>> a lot of patches, and I would be really grateful if we could reduce
>> them a lot - so please let me know if there is patch which you've sent
>> PR for and it's not merged yet.
> 
> Hi Honza,
> 
> Sorry for the delay.  You've already merged my PR for two simple typos,
> thanks!  Beyond that, there really isn't much in our patch queue
> anymore.  As far as I can see, current master even has a patch for error
> propagation in notifyd, which will let us drop one more!  And we arrive
> at the example configs.  We prefer syslog for several reasons
> (copytruncate rotation isn't pretty, decoupling possible I/O stalls) and
> we haven't got the /var/log/cluster legacy.  But more importantly, the
> knet default transport requires a nodelist instead of interfaces, unlike
> mcast udp.  The "ring" terminology might need a change as well,
> especially ring0_addr.  So I'd welcome an overhaul of the (now knet)
> example config, but I'm not personally qualified for doing that. :)
> 
> Finally, something totally unrelated: the libtotem_pg shared object
> isn't standalone anymore, it has several undefined symbols (icmap_get_*,
> stats_knet_add_member, etc) which are defined in the corosync binary.
> Why is it still a separate object then?
> 

I argued a while back for making it a static library or just building it
straight into corosync. It makes little sense to me having it as a
shared library any more - if it ever did. All it really achieves (IMHO)
is to make debugging more complicated than it ought to be.

Chrissie