From: Eric Barton <eeb@sun.com>
To: lustre-devel@lists.lustre.org
Subject: [Lustre-devel] security: MGS connection
Date: Fri, 06 Jun 2008 01:20:55 +0100 [thread overview]
Message-ID: <056d01c8c76b$2fb35890$0281a8c0@ebpc> (raw)
In-Reply-To: <48481218.9010703@sun.com>
> > It's OK if the MGS will reject any connection attempt with insufficient
> > security. In that case, you could put the security in the mount option
> > and it should probably be an error to specify different levels of security
> > when talking to the same MGS.
>
> I guess there's misunderstanding. The problem is not on MGS, it's on
> MGC. Each node have only one MGC, thus only one ptlrpc connection to
> MGS, which is shared by _all_ Lustre components live on this node. So in
> case of mounting 2 OSTs on a single node, only one security flavor could
> be used.
Yes - I didn't make myself clear enough. I grok there is only 1 MGC and I
suggest we report an error if the MGC has already established a connection
with insufficient security for a subsequent mount because this reveals an
inconsistency.
Cheers,
Eric
next prev parent reply other threads:[~2008-06-06 0:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <C46C26CE.574E%peter.braam@sun.com>
[not found] ` <4846C394.1020801@sun.com>
2008-06-04 17:47 ` [Lustre-devel] security: MGS connection Eric Barton
2008-06-04 18:07 ` Spencer Shepler
2008-06-04 19:07 ` Eric Mei
2008-06-04 18:38 ` Eric Mei
2008-06-04 18:49 ` Peter Braam
2008-06-04 19:24 ` Eric Barton
2008-06-05 16:19 ` Eric Mei
2008-06-06 0:20 ` Eric Barton [this message]
2008-06-05 16:54 ` Eric Mei
2008-06-06 0:36 ` Eric Barton
2008-06-06 1:39 ` Eric Mei
2008-06-06 3:16 ` Peter Braam
2008-06-06 15:16 ` Eric Mei
2008-06-06 3:30 ` Peter Braam
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='056d01c8c76b$2fb35890$0281a8c0@ebpc' \
--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.