From: Jonathan E Brassow <jbrassow@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] clvmd interface question
Date: Fri, 18 Nov 2005 11:54:33 -0600 [thread overview]
Message-ID: <ff57449f1c9444ba3e70a4c6cde5cea8@redhat.com> (raw)
In-Reply-To: <437D8D72.4050909@redhat.com>
Also, there is a package called 'magma' that lives in the cluster tree.
This is an abstraction layer to different cluster managers and lock
managers. It has the ability to accept plugins for different cluster
managers. I wonder if it would be useful for clvm to use magma, then
writing plugins is easy and you never have to touch code that makes use
of the cluster managers.
Patrick would know if this is a worthwhile goal.
brassow
On Nov 18, 2005, at 2:14 AM, Patrick Caulfield wrote:
> John DeFranco wrote:
>> Hi, I'm looking for some information. I'm interested in learning more
>> about the clvmd daemon. I've search and found various pieces of info
>> in
>> addition to looking at the code. Specifically I looking to for
>> information (a spec) on how one might be able to add a new cluster
>> manager plugin if you will (if that is even possible). I know that
>> clvmd
>> interfaces with a couple of different cluster managers now but I'd
>> like
>> to expland this if possible.
>
> clvmd supports cman and gulm, it has it's own internal function switch
> that
> determines what to do for each cluster manager.
>
> To be honest it's not a good API as it was originally only designed to
> work with
> cman and the gulm support was bolted on later - so adding a new
> cluster manager
> might be a bit of work.
>
> Have a look at the bottom of LVM2/daemons/clvmd/clvmd-cman for the
> function switch.
>
> You'll also need to be aware that CMAN provides its own messaging
> system, which
> gulm does not. If your cluster manager provides a messaging system
> then I
> recommend you use it - otherwise you should be able to use the
> tcp-comms.c file
> with clvmd (that gulm support uses).
>
> Another way, that might be easier, is to patch clvmd with the libcman
> patch in
> head of cluster CVS (cluster/cman/lib/clvmd-libcman.diff) and write a
> library
> for your cluster manager that emulates libcman - that one is a nice
> simple API
> and it will be supported by future versions of cman too.
>
> --
>
> patrick
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
>
next prev parent reply other threads:[~2005-11-18 17:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-17 17:46 [linux-lvm] clvmd interface question John DeFranco
2005-11-18 8:14 ` Patrick Caulfield
2005-11-18 17:54 ` Jonathan E Brassow [this message]
2005-11-21 8:46 ` Patrick Caulfield
2005-12-02 0:15 ` John DeFranco
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ff57449f1c9444ba3e70a4c6cde5cea8@redhat.com \
--to=jbrassow@redhat.com \
--cc=linux-lvm@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).