[Pacemaker] OpenAIS vs. Corosync

[Ryan Steele]

As someone who is just getting acquainted with a world that is no longer 
just DRBD + Heartbeat, I find myself a bit confused on exactly what I 
should be using - CoroSync or OpenAIS?


I was using OpenAIS + Pacemaker in my first few days of testing, but I 
then upgraded only to find that the aisexec binary was no longer part of 
the openais package. and that the openais init scripts simply called 
/usr/sbin/corosync.  Should we just be calling /etc/init.d/corosync 
instead?

Concerning the main config file, there now appears to be a new 
configuration file location '/etc/corosync.conf' on the filesystem. 
Does this mean /etc/ais just used as a place to store the authkey and 
amf.conf?   To that end, should the 'aisexec' container (described on 
http://clusterlabs.org/wiki/Initial_Configuration) be changed to say 
'corosync' instead?


I'd be grateful to anyone who could give definitive answers for any or 
all of these questions, because the clusterlabs wiki makes almost zero 
mention of corosync, except for a brief blurb in the FAQ/TODO which 
indicate that it's the next version of OpenAIS.  If the future is truly 
OpenAIS (or CoroSync), and not Heartbeat, I'd feel a lot better if it 
were a better documented and/or less volatile target.



Regards,
Ryan
-- 
Ryan Steele
Systems Administrator