public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Phillips <phillips@redhat.com>
To: linux-cluster@redhat.com
Cc: David Teigland <teigland@redhat.com>,
	linux-kernel@vger.kernel.org, ocfs2-devel@oss.oracle.com
Subject: Re: [Linux-cluster] [RFC] nodemanager, ocfs2, dlm
Date: Wed, 20 Jul 2005 03:19:50 +1000	[thread overview]
Message-ID: <200507200319.51000.phillips@redhat.com> (raw)
In-Reply-To: <20050718061553.GA9568@redhat.com>

On Monday 18 July 2005 16:15, David Teigland wrote:
> I've taken a stab at generalizing ocfs2_nodemanager so the dlm could use
> it (removing ocfs-specific stuff).  It still needs some work, but I'd
> like to know if this appeals to the ocfs group and to others who were
> interested in seeing some similarity in dlm/ocfs configuration.

Let me get this straight.  The proposal is to expose cluster membership as a 
virtual filesystem and use that as the primary membership interface?  So 
that, e.g., a server on the cluster does a getdents to find out what nodes 
are in the cluster or uses inotify to learn about membership changes, 
instead of subscribing for and receiving membership events directly from 
the cluster membership manager?

Or what is this about, just providing a nice friendly view of the cluster to 
the administrator, not intended to be used by cluster infrastructure 
components?

Regards,

Daniel

  parent reply	other threads:[~2005-07-19 17:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-18  6:15 [RFC] nodemanager, ocfs2, dlm David Teigland
2005-07-19 15:52 ` [Ocfs2-devel] " Lars Marowsky-Bree
2005-07-20  3:35   ` David Teigland
2005-07-20 16:26     ` Lars Marowsky-Bree
2005-07-19 17:19 ` Daniel Phillips [this message]
2005-07-20  0:48 ` [Linux-cluster] " Mark Fasheh
2005-07-20  4:16   ` David Teigland

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=200507200319.51000.phillips@redhat.com \
    --to=phillips@redhat.com \
    --cc=linux-cluster@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ocfs2-devel@oss.oracle.com \
    --cc=teigland@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