Hey folks, We use the agreed messaging mode of spread for coordinating nodes in our cluster, and I've just discovered corosync. We have a love-hate relationship with the spread software, and the possibility of moving to another system with similar facilities is appealing to us (but at the same time, we're not going to blindly leap!)
The evs_overview(8) docs suggest that EVS is not currently ready for prime time, so I'm wondering which aspects of it need work? We make use of the spread SP_join, SP_leave APIs, (analagous to evs_join, evs_leave?) and SP_scat_multicast, SP_scat_receive (evs_mcast_joined/evs_mcast_groups and the deliver_fn callback specified in evs_initialize). Are my assumptions about the mapping of APIs from spread to corosync accurate? Are there specific nuances that should be taken into account when migrating from spread? Another capability that we use in spread is the ability to run the spread daemon on two different networks (often in different datacenters) and let spread route the messages to the appropriate groups. We tend to use broadcast rather than multicast. I didn't see specific documentation on this (I did notice the "broadcast" option in corosync.conf), so I'm wondering if the features are on par with spread or if there are some differences that we'd need to take into account. Thanks in advance for any information you can provide, --Wez. _______________________________________________ Openais mailing list [email protected] https://lists.linux-foundation.org/mailman/listinfo/openais
