On Thu, Mar 1, 2012 at 12:11 AM, Andrew Beekhof <and...@beekhof.net> wrote: > On Thu, Mar 1, 2012 at 8:08 AM, Florian Haas <flor...@hastexo.com> wrote: >> Andrew, >> >> just a quick question out of curiosity: the ocf:pacemaker:o2cb resource >> and ocfs2_controld.pcmk require the OpenAIS CKPT service which is >> currently deprecated (as all of OpenAIS) and going away completely >> (IIUC) with Corosync 2.0. Does that mean that OCFS2 will be unsupported >> from Corosync 2.0 forward, as far as Pacemaker is concerned? > > Unless they rewrite their controld for corosync 2.0 (in a similar > manner to what GFS2 did), then you are correct. > Pacemaker itself doesn't actually care, those controld's are ways for > the FS to get membership data out of the cluster, not to put anything > pack in.
OK, so just to summarize: Current situation (Pacemaker with Corosync 1.x): - use ocfs2_controld.pcmk when _not_ running on cman (requires OpenAIS CKPT service); or - use ocfs2_controld.cman when running on cman. Future situation (Pacemaker with Corosync 2.x): - OpenAIS goes away, no CKPT service, ocfs2_controld.pcmk stops working; - cman goes away, ocfs2_controld.cman stops working. Is that summary correct? Do you happen to know whether the OCFS2 folks are informed about this? Cheers, Florian -- Need help with High Availability? http://www.hastexo.com/now _______________________________________________ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
