From: Eric Barton <eeb@sun.com>
To: lustre-devel@lists.lustre.org
Subject: [Lustre-devel] Security configuration
Date: Tue, 17 Feb 2009 20:37:42 +0000 [thread overview]
Message-ID: <014901c9913f$94f0b560$bed22020$@com> (raw)
Nathan,
We'd like to be able to describe a set of nodes and say that
as far as security is concerned, they are all equivalent - i.e. if
an MDT authorizes eeb at node1 to perform a certain action, then
eeb at nodex is implicitly authorized provided node1 and nodex are in
the same set.
Leaving aside for now, the question of how the sets are described
(they could be whole LNETs or whole Kerberos realms, or NID lists),
is the MGS the right place to stash this config?
Cheers,
Eric
next reply other threads:[~2009-02-17 20:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-17 20:37 Eric Barton [this message]
2009-02-18 23:19 ` [Lustre-devel] Security configuration Nicolas Williams
2009-03-05 18:05 ` Nathaniel Rutman
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='014901c9913f$94f0b560$bed22020$@com' \
--to=eeb@sun.com \
--cc=lustre-devel@lists.lustre.org \
/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.