<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
Thanks, for the input. WRT to one LNET per fileset, is there some
technical reason for this design?<br>
<br>
Cheers,<br>
Hans Henrik<br>
<br>
<div class="moz-cite-prefix">On 06.01.2020 09.41, Moreno Diego (ID
SIS) wrote:<br>
</div>
<blockquote type="cite"
cite="mid:00A32A31-B8D3-419A-AA54-B0E5421E77DA@id.ethz.ch">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style>
<div class="WordSection1">
<p class="MsoNormal">I’m not sure about the SSK limitations but
I know for sure that you can have multiple filesets belonging
to the same filesystem on a client. As you already said,
you’ll basically need to have one LNET per fileset (o2ib0,
o2ib1, o2ib2), then mount each fileset with the option ‘-o
network=<filesets_lnet>’.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I gave a talk on our setup during last LAD
(<a href="https://bit.ly/35oaPl7" moz-do-not-send="true">https://bit.ly/35oaPl7</a>),
slide 24 contains a few details on this. It’s for a routed
configuration but we also had it working without LNET routers.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><span style="color:black">Diego</span><o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-top:solid #B5C4DF
1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal" style="margin-left:36.0pt"><b><span
style="font-size:12.0pt;color:black">From:
</span></b><span style="font-size:12.0pt;color:black">lustre-discuss
<a class="moz-txt-link-rfc2396E" href="mailto:lustre-discuss-bounces@lists.lustre.org"><lustre-discuss-bounces@lists.lustre.org></a> on behalf
of Jeremy Filizetti <a class="moz-txt-link-rfc2396E" href="mailto:jeremy.filizetti@gmail.com"><jeremy.filizetti@gmail.com></a><br>
<b>Date: </b>Tuesday, 31 December 2019 at 04:22<br>
<b>To: </b>Hans Henrik Happe <a class="moz-txt-link-rfc2396E" href="mailto:happe@nbi.dk"><happe@nbi.dk></a><br>
<b>Cc: </b><a class="moz-txt-link-rfc2396E" href="mailto:lustre-discuss@lists.lustre.org">"lustre-discuss@lists.lustre.org"</a>
<a class="moz-txt-link-rfc2396E" href="mailto:lustre-discuss@lists.lustre.org"><lustre-discuss@lists.lustre.org></a><br>
<b>Subject: </b>Re: [lustre-discuss] Nodemap, ssk and
mutiple fileset from one client<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><o:p> </o:p></p>
</div>
<div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt">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.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt">Jeremy<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal" style="margin-left:36.0pt"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt">On Mon, Dec
30, 2019 at 9:30 PM Hans Henrik Happe <<a
href="mailto:happe@nbi.dk" moz-do-not-send="true">happe@nbi.dk</a>>
wrote:<o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC
1.0pt;padding:0cm 0cm 0cm
6.0pt;margin-left:4.8pt;margin-right:0cm">
<p class="MsoNormal" style="margin-left:36.0pt">Hi,<br>
<br>
Is it possible to have one client mount multiple fileset's
with<br>
different ssk keys.<br>
<br>
Basically, we would just like to hand out a key to clients
that should<br>
be allowed to mount a specific fileset (subdir). First, it
looks like<br>
the nodemap must contain the client NID for it to be able
to mount. The<br>
key is not enough. Secondly, nodemaps are not allowed hold
the same<br>
NIDs, so it seems impossible to have multiple ssk
protected filesets<br>
mounted from one client, unless multiple NIDs are used?<br>
<br>
Example: For nodes A and B and filesets f0 (key0) and f1
(key1).<br>
<br>
A: Should be allowed to mount f0 (key0).<br>
B: Should be allowed to mount f0 (key0) and f1 (key1).<br>
<br>
Cheers,<br>
Hans Henrik<br>
_______________________________________________<br>
lustre-discuss mailing list<br>
<a href="mailto:lustre-discuss@lists.lustre.org"
target="_blank" moz-do-not-send="true">lustre-discuss@lists.lustre.org</a><br>
<a
href="http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org"
target="_blank" moz-do-not-send="true">http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org</a><o:p></o:p></p>
</blockquote>
</div>
</div>
</blockquote>
<br>
</body>
</html>