On Fri, Nov 21, 2008 at 10:24:25AM +0100, Jeremy Lainé wrote:
> As stated in my previous email I am trying to revive the Debian packaging for
> ocfs2-tools.
> One of the things I noticed while building ocfs2-tools is that the configure
> script
> complains about these missing dependencies:
>
> checking for cman_replyto_shutdown in -lcman... no
> configure: WARNING: libcman not found, cman support will not be built
> no
> configure: WARNING: libcpg not found, cman support will not be built
> checking libdlm.h usability... no
> checking libdlm.h presence... no
> checking for libdlm.h... no
> configure: WARNING: libdlm.h not found, fsdlm support will not be built
>
> I can add libcman-dev and libdlm-dev to the Build-Depends, but could you
> please describe
> what additional features we'll gain?
[Short answer]
Don't do it yet.
[Longer answer]
Support for the cman and pacemaker cluster stacks. The reason I say
don't do it yet is that 1.4.1 doesn't have the full support in the code.
[Full answer]
ocfs2 has always supported its internal cluster stack (o2cb) and DLM
(o2dlm). ocfs2 in mainline has added support for userspace cluster
stacks that support the generic DLM in fs/dlm.ko. Today, that means Red
Hat's CMan and SuSE's PaceMaker. That's all there in 2.6.26 and later.
The ocfs2 tools also need to understand a userspace cluster stack. The
libo2cb and libo2dlm libraries need updating, and the o2cb.init script
needs to do the right thing.
To have the userspace stack interact with the ocfs2 kernel driver, we
provide a daemon called "ocfs2_controld.<stack_name>". Right now, the
master branch of ocfs2-tools has both ocfs2_controld.cman and
ocfs2_controld.pcmk.
While the 1.4.1 release has some of the ocfs2_controld code, it's not
usable. Which is why I say "don't do it yet".
The master branch has working code. If configure.in detects the
appropriate pieces for cman, pacemaker, or both, it will build the
support in.
When it comes to packaging, we've designed it so that the core
ocfs2-tools package has no additional dependencies. The
ocfs2_controld.cman daemon will be packaged as 'ocfs2-tools-cman', and
the ocfs2_controld.pcmk daemon will be packaged as
'ocfs2-tools-pacemaker'. Those sub-packages will depend on cman and
pacemaker respectively. Thus, a user who wants to use o2cb does not
need to install cman or pacemaker. A user who wants to use pacemaker does
not need to install cman. And a user can even install support for all
three stacks, switching between them to try them out. o2cb.init starts
the appropriate daemon based on a variable in /etc/default/o2cb.
When we release a version with these packages, the build requirements
will be modified to include corosync/openais, libdlm, cman, and
pacemaker. But we haven't gotten there yet, on any platform.
I hope this answered your question :-)
Joel
--
Life's Little Instruction Book #356
"Be there when people need you."
Joel Becker
Principal Software Developer
Oracle
E-mail: [EMAIL PROTECTED]
Phone: (650) 506-8127
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
