From: Lars Marowsky-Bree <lmb@suse.de>
To: "Walker, Bruce J (HP-Labs)" <bruce.walker@hp.com>,
linux clustering <linux-cluster@redhat.com>,
David Teigland <teigland@redhat.com>
Cc: linux-kernel@vger.kernel.org, ocfs2-devel@oss.oracle.com,
clusters_sig@lists.osdl.org
Subject: Re: [Clusters_sig] RE: [Linux-cluster] Re: [Ocfs2-devel] [RFC] nodemanager, ocfs2, dlm
Date: Wed, 20 Jul 2005 20:09:18 +0200 [thread overview]
Message-ID: <20050720180918.GU5416@marowsky-bree.de> (raw)
In-Reply-To: <3689AF909D816446BA505D21F1461AE404167CFB@cacexc04.americas.cpqcorp.net>
On 2005-07-20T09:55:31, "Walker, Bruce J (HP-Labs)" <bruce.walker@hp.com> wrote:
> Like Lars, I too was under the wrong impression about this configfs
> "nodemanager" kernel component. Our discussions in the cluster
> meeting Monday and Tuesday were assuming it was a general service that
> other kernel components could/would utilize and possibly also
> something that could send uevents to non-kernel components wanting a
> std. way to see membership information/events.
Let me clarify that this was something we briefly touched on in
Walldorf: The node manager would (re-)export the current data via sysfs
(which would result in uevents being sent, too), and not something we
dreamed up just Monday ;-)
> As to kernel components without corresponding user-level "managers",
> look no farther than OpenSSI. Our hope was that we could adapt to a
> user-land membership service and this interface thru configfs would
> drive all our kernel subsystems.
Well, node manager still can provide you the input as to which nodes are
configured, which in a way translates to "membership". The thing it
doesn't seem to provide yet is the supsend/modify/resume cycle which for
example the RHAT DLM seems to require.
Sincerely,
Lars Marowsky-Brée <lmb@suse.de>
--
High Availability & Clustering
SUSE Labs, Research and Development
SUSE LINUX Products GmbH - A Novell Business -- Charles Darwin
"Ignorance more frequently begets confidence than does knowledge"
next prev parent reply other threads:[~2005-07-20 18:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-20 16:55 [Linux-cluster] Re: [Ocfs2-devel] [RFC] nodemanager, ocfs2, dlm Walker, Bruce J (HP-Labs)
2005-07-20 18:09 ` Lars Marowsky-Bree [this message]
2005-07-20 18:39 ` [Clusters_sig] " Joel Becker
2005-07-21 23:22 ` Lars Marowsky-Bree
2005-07-22 3:22 ` Daniel Phillips
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=20050720180918.GU5416@marowsky-bree.de \
--to=lmb@suse.de \
--cc=bruce.walker@hp.com \
--cc=clusters_sig@lists.osdl.org \
--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