On 01/13/2011 08:03 AM, Lars Marowsky-Bree wrote: > On 2010-12-01T14:18:25, Steven Dake <[email protected]> wrote: > >> Corosync 1.3.0 is available for immediate download from our website. >> This version brings many enhancements to the software. The two most >> visible enhancements are UDPU transport mode and the >> cpg_model_initialize api call. The UDPU transport omde allows Corosync >> to run over basic UDP transport without the need for multicast support >> in the cluster switching environment. The API addition allows for >> correct operation of cluster file systems such as gfs2 and ocfs2. >> > > Hi Steven, > > can you elaborate please - how are current cluster file system > implementations not "correct", or is this a mere API enhancement? >
Dave has more details, but we needed to add an API to give ring id information to fenced to prevent fenced from entering a stuck state. The conditions leading up to the problem are difficult for me to recall, but it did happen in community testing as well as internal validation. I recommend pinging dct offline if you need more information. (There is a fenced patch that goes with this, and perhaps something else). > UDPU git comment says "This file should be copied to each node > in the cluster and IP addresses changed as appropriate." - does this > mean the configuration needs to differ across the nodes, or just that, > obviously, the example has to be customized once? (I hope the latter ;-) > > The configuration file should be the same on all nodes (so the latter). Must have been a 24 hr coding session prior to git commit :) Regards -steve > Regards, > Lars > _______________________________________________ Openais mailing list [email protected] https://lists.linux-foundation.org/mailman/listinfo/openais
