[lustre-discuss] Nodemap, ssk and mutiple fileset from one client

Jeremy Filizetti jeremy.filizetti at gmail.com
Mon Dec 30 19:21:51 PST 2019

It doesn't look like this would be possible due to nodemap or SSK
limitations.  As you pointed out, nodemap must associate a NID with a
single nodemap.  SSK was intentionally tied to nodemap by design.  It does
a lookup on the nodemap of a NID to verify it matches what is found in the
server key.  I think even if you used multiple NIDs for a client like
o2ib(ib0),o2ib1(ib0) you would still run into issues due to LNet, but I'm
not certain on that.


On Mon, Dec 30, 2019 at 9:30 PM Hans Henrik Happe <happe at nbi.dk> wrote:

> Hi,
> Is it possible to have one client mount multiple fileset's with
> different ssk keys.
> Basically, we would just like to hand out a key to clients that should
> be allowed to mount a specific fileset (subdir). First, it looks like
> the nodemap must contain the client NID for it to be able to mount. The
> key is not enough. Secondly, nodemaps are not allowed hold the same
> NIDs, so it seems impossible to have multiple ssk protected filesets
> mounted from one client, unless multiple NIDs are used?
> Example: For nodes A and B and filesets f0 (key0) and f1 (key1).
> A: Should be allowed to mount f0 (key0).
> B: Should be allowed to mount f0 (key0) and f1 (key1).
> Cheers,
> Hans Henrik
> _______________________________________________
> lustre-discuss mailing list
> lustre-discuss at lists.lustre.org
> http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lustre.org/pipermail/lustre-discuss-lustre.org/attachments/20191230/39ea81a5/attachment.html>

More information about the lustre-discuss mailing list