cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Wendy Cheng <wcheng@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Re: [NFS] [PATCH 3/4 Revised] NLM - kernel lockd-statd changes
Date: Tue, 10 Apr 2007 14:16:59 -0400	[thread overview]
Message-ID: <461BD49B.7090503@redhat.com> (raw)
In-Reply-To: <200704101109.44333.okir@lst.de>

Olaf Kirch wrote:
> But - why do you need to record the address on which the request was
> received. at all? Don't you know beforehand on which IP addresses you
> will be servicing NFS requests, and which will need to be migrated?
>
>   

Sorry, somehow I missed this question ...

The intent is to avoid sending notifications to *all* clients.  The 
cluster user mode scripts will have to associate the floating IP(s) with 
fsid(s) and relies heavily on the information passed by rpc.statd's 
ha-callout program. My test ha-callout user mode program shows the 
following:

/mnt/lockd/ha-pg/hatest is invoked with 3 arguments.
    add-client
    192.168.24.146
    192.168.24.149
/mnt/lockd/ha-pg/hatest is invoked with 3 arguments.
    del-client
    192.168.24.145
    192.168.24.149

These info(s) will be used to construct the notification list when 
notification actually take places.

-- Wendy



  parent reply	other threads:[~2007-04-10 18:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-05 21:52 [Cluster-devel] [PATCH 3/4 Revised] NLM - kernel lockd-statd changes Wendy Cheng
2007-04-10  9:10 ` [Cluster-devel] Re: [NFS] " Olaf Kirch
2007-04-10 14:41   ` Lon Hohberger
2007-04-10 15:00   ` Wendy Cheng
2007-04-10 18:16   ` Wendy Cheng [this message]
     [not found]   ` <message from Olaf Kirch on Tuesday April 10>
2007-04-11  4:50     ` Neil Brown
2007-04-13 19:16       ` Lon Hohberger
2007-04-13 19:31         ` Wendy Cheng
2007-04-17 11:52         ` Olaf Kirch
2007-04-17 13:24           ` Wendy Cheng
2007-04-17 14:51             ` Olaf Kirch
2007-04-17 15:09               ` Wendy Cheng

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=461BD49B.7090503@redhat.com \
    --to=wcheng@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).