From: "Bill Rugolsky Jr." <brugolsky@telemetry-investments.com>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: nfs@lists.sourceforge.net, lmb@suse.de
Subject: Re: High Availability NFS Proposal
Date: Sun, 25 Aug 2002 01:28:16 -0400 [thread overview]
Message-ID: <20020825012816.A7902@ti19> (raw)
In-Reply-To: <200208242216.g7OMG3802286@localhost.localdomain>; from James.Bottomley@SteelEye.com on Sat, Aug 24, 2002 at 06:16:03PM -0400
On Sat, Aug 24, 2002 at 06:16:03PM -0400, James Bottomley wrote:
> Unfortunately, our product, LifeKeeper, is more complex than just a simple two
> node active passive cluster, so the usual just share /var/lib/nfs solution
> won't work for us. What I'd like to propose instead is to place hooks inside
> mountd and statd that would allow them to propagate the necessary state
> information into a cluster. The best way I can think of is to designate two
> executable hooks (say /var/lib/nfs/mountd-hook and /var/lib/nfs/statd-hook).
> If mountd and statd don't find these on start up, they proceed normally.
> However, if they exist, mountd and statd will execute them with certain
> arguments to allow the clustering software to keep track of the client
> machines correctly.
James,
Neil Brown has said that he is working on the NFS authentication infrastructure,
which apparently includes some userland notification infrastructure for mountd.
You will probably want to take note of his work when deciding on the format
of those "certain arguments" to the notification hooks.
Back in 2.2.x, David Woodhouse wrote code (never merged) that added
mountd upcalls to knfsd. The code was modified by Elvis Pftzenreuter
<epx@conectiva.com.br>, then updated by Luis Claudio R. Goncalves
<lclaudio@conectiva.com.br>. IIRC, the original impetus was to handle
re-authentication in the presence of wildcard (netgroup, etc.) exports
in a sane way.
You can find Elvis's original patchset here:
http://marc.theaimsgroup.com/?l=linux-nfs&m=87941837303295&w=2
Some of Neil Brown's early comments on how to improve and generalize the
infrastructure can be found here:
http://marc.theaimsgroup.com/?l=linux-nfs&m=87941837303307&w=2
I expect that that details of Neil's work on this has evolved in light of the
direction that NFSv4 has taken, but remains largely the same in broad outline.
Best to ask Neil about that, of course. :-)
Regards,
Bill Rugolsky
-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone? Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2002-08-25 5:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-24 22:16 High Availability NFS Proposal James Bottomley
2002-08-25 5:28 ` Bill Rugolsky Jr. [this message]
2002-08-26 4:46 ` James Bottomley
2002-08-26 17:54 ` Spencer Shepler
2002-08-26 19:04 ` James Bottomley
2002-08-26 22:01 ` Spencer Shepler
2002-09-15 10:18 ` Neil Brown
2002-08-26 4:36 ` Bryan O'Sullivan
2002-08-26 4:51 ` James Bottomley
2002-08-26 19:41 ` Bryan O'Sullivan
2002-09-15 10:12 ` Neil Brown
2002-09-23 13:53 ` James Bottomley
2002-09-24 4:17 ` Neil Brown
2002-09-26 16:13 ` James Bottomley
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=20020825012816.A7902@ti19 \
--to=brugolsky@telemetry-investments.com \
--cc=James.Bottomley@SteelEye.com \
--cc=lmb@suse.de \
--cc=nfs@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.