<div class="socmaildefaultfont" dir="ltr" style="font-family:Arial, Helvetica, sans-serif;font-size:10.5pt" ><div dir="ltr" >That's right. Anyone using the ReST API needs to have the credentials and could use those to do other queries as well. The ReST API follows a role authorization model, so you can restrict what a user might do. But the least powerful role "Monitor" still allows read access to all URLs while restricting all POST, PUT, DELETE ops. We have an item somewhere on our roadmap to allow for a more granular definition of what a user might read, but no real schedule for that today.</div>
<div dir="ltr" > </div>
<div dir="ltr" ><div class="socmaildefaultfont" dir="ltr" style="font-family:Arial, Helvetica, sans-serif;font-size:10.5pt" ><div class="socmaildefaultfont" dir="ltr" style="font-family:Arial, Helvetica, sans-serif;font-size:10.5pt" ><div class="socmaildefaultfont" dir="ltr" style="font-family:Arial, Helvetica, sans-serif;font-size:10.5pt" ><div class="socmaildefaultfont" dir="ltr" style="font-family:Arial, Helvetica, sans-serif;font-size:10.5pt" ><div class="socmaildefaultfont" dir="ltr" style="font-family:Arial;font-size:10.5pt" ><div class="socmaildefaultfont" dir="ltr" style="font-family:Arial;font-size:10.5pt" ><div dir="ltr" ><font face="Default Sans Serif,Verdana,Arial,Helvetica,sans-serif" size="2" ><font face="Default Sans Serif,Verdana,Arial,Helvetica,sans-serif" size="2" ><font face="Arial" size="2" >Mit freundlichen Grüßen / Kind regards</font> </font> </font>
<p><font face="Default Sans Serif,Verdana,Arial,Helvetica,sans-serif" size="2" ><font face="Default Sans Serif,Verdana,Arial,Helvetica,sans-serif" size="2" ><img height="23" src="cid:15481420128480" width="605" ></font></font></p><font face="Default Sans Serif,Verdana,Arial,Helvetica,sans-serif" size="2" > <font face="Default Sans Serif,Verdana,Arial,Helvetica,sans-serif" size="2" > </font> </font>
<table border="0" cellpadding="0" cellspacing="0" > <tbody> <tr valign="top" > <td valign="middle" width="202" ><font face="Default Sans Serif,Verdana,Arial,Helvetica,sans-serif" size="2" ><font face="Default Sans Serif,Verdana,Arial,Helvetica,sans-serif" size="2" ><img align="bottom" alt="IBM Spectrum Scale" height="51" src="cid:15481420128481" width="201" > </font> </font>
<ul style="padding-left: 0pt; margin-left: 0px; list-style-type: none;" > <li><font face="Default Sans Serif,Verdana,Arial,Helvetica,sans-serif" size="2" > </font></li> </ul> <font face="Default Sans Serif,Verdana,Arial,Helvetica,sans-serif" size="2" > <font face="Default Sans Serif,Verdana,Arial,Helvetica,sans-serif" size="2" > </font></font></td> <td valign="middle" width="31" > <ul style="padding-left: 0pt; margin-left: 0px; list-style-type: none;" > <li><font face="Default Sans Serif,Verdana,Arial,Helvetica,sans-serif" size="2" ><font face="Default Sans Serif,Verdana,Arial,Helvetica,sans-serif" size="2" ><font size="3" > </font></font></font></li> </ul> </td> <td valign="middle" width="464" > <ul style="padding-left: 0pt; margin-left: 0px; list-style-type: none;" > <li><font face="Default Sans Serif,Verdana,Arial,Helvetica,sans-serif" size="2" ><font face="Default Sans Serif,Verdana,Arial,Helvetica,sans-serif" size="2" ><b><font face="Arial" size="3" >Dr. Alexander Wolf-Reber</font></b><br> <font face="Arial" size="1" >Spectrum Scale Release Lead Architect<br> Department M069 / Spectrum Scale Software Development<br> <br> +49-7034-2745404<br> a.wolf-reber@de.ibm.com</font></font></font></li> </ul> </td> </tr> </tbody></table><font face="Default Sans Serif,Verdana,Arial,Helvetica,sans-serif" size="2" > <font face="Default Sans Serif,Verdana,Arial,Helvetica,sans-serif" size="2" > <img height="23" src="cid:15481420128482" width="605" > </font> </font>
<p><font face="Default Sans Serif,Verdana,Arial,Helvetica,sans-serif" size="2" ><font face="Default Sans Serif,Verdana,Arial,Helvetica,sans-serif" size="2" ><font color="#999999" face="Arial" size="1" >IBM Deutschland Research & Development GmbH / Vorsitzende des Aufsichtsrats: Matthias Hartmann / Geschäftsführung: Dirk Wittkopp<br>Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, HRB 243294</font></font></font></p><font face="Default Sans Serif,Verdana,Arial,Helvetica,sans-serif" size="2" > <font face="Default Sans Serif,Verdana,Arial,Helvetica,sans-serif" size="2" > </font></font></div></div></div></div></div></div></div></div>
<div dir="ltr" > </div>
<div dir="ltr" > </div>
<blockquote data-history-content-modified="1" dir="ltr" style="border-left:solid #aaaaaa 2px; margin-left:5px; padding-left:5px; direction:ltr; margin-right:0px" >----- Original message -----<br>From: "Buterbaugh, Kevin L" <Kevin.Buterbaugh@Vanderbilt.Edu><br>Sent by: gpfsug-discuss-bounces@spectrumscale.org<br>To: gpfsug main discussion list <gpfsug-discuss@spectrumscale.org><br>Cc:<br>Subject: Re: [gpfsug-discuss] Get list of filesets_without_runningmmlsfileset?<br>Date: Mon, Jan 21, 2019 5:36 PM<br> <br><!--Notes ACF
<meta http-equiv="Content-Type" content="text/html; charset=utf8" >--> Hi All,
<div> </div>
<div>I just wanted to follow up on this thread … the only way I have found to obtain a list of filesets and their associated junction paths as a non-root user is via the REST API (and thanks to those who suggested that). However, AFAICT querying the REST API via a script would expose the username / password used to do so to anyone who bothered to look at the code, which would in turn allow a knowledgeable and curious user to query the REST API themselves for other information we do not necessarily want to expose to them. Therefore, it is not an acceptable solution to us.</div>
<div> </div>
<div>Therefore, unless someone responds with a way to allow a non-root user to obtain fileset junction paths that doesn’t involve the REST API, I’m afraid I’m at a dead end in terms of making our quota usage Python script something that I can share with the broader community. It just has too much site-specific code in it. Sorry…</div>
<div> </div>
<div>Kevin</div>
<div> </div>
<div>P.S. In case you’re curious about how the quota script is obtaining those junction paths … we have a cron job that runs once per hour on the cluster manager that dumps the output of mmlsfileset to a text file, which the script then reads. The cron job used to just run once per day and used to just run mmlsfileset. I have modified it to be a shell script which checks for the load average on the cluster manager being less than 10 and that there are no waiters of more than 10 seconds duration. If both of those conditions are true, it runs mmlsfileset. If either are not, it simply exits … the idea being that one or both of those would likely be true if something were going on with the cluster manager that would cause the mmlsfileset to hang.</div>
<div> </div>
<div>I have also modified the quota script itself so that it checks that the junction path for a fileset actually exists before attempting to stat it (duh - should’ve done that from the start), which handles the case where a user would run the quota script and it would bomb off with an exception because the fileset was deleted and the cron job hadn’t run yet. If a new fileset is created, well, it just won’t get checked by the quota script until the cron job runs successfully. We have decided that this is an acceptable compromise.
<div>
<blockquote type="cite" ><div>On Jan 15, 2019, at 8:46 AM, Marc A Kaplan <<a href="mailto:makaplan@us.ibm.com" target="_blank">makaplan@us.ibm.com</a>> wrote:</div>
<div><span style=" font-size:10pt;font-family:sans-serif" >Personally, I agree that there ought to be a way in the product.</span><br><br><span style=" font-size:10pt;font-family:sans-serif" >In the meawhile, you no doubt already have some ways to tell your users where to find their filesets as pathnames.</span><br><span style=" font-size:10pt;font-family:sans-serif" >Otherwise, how are they accessing their files?</span><br><br><span style=" font-size:10pt;font-family:sans-serif" >And to keep things somewhat sane, I'd bet filesets are all linked to one or small number of well known paths in the filesystem.</span><br><span style=" font-size:10pt;font-family:sans-serif" >Like /AGpfsFilesystem/filesets/... Plus you could add symlinks and/or as has been suggested post info extracted from mmlsfileset and/or mmlsquota.</span><br><br><span style=" font-size:10pt;font-family:sans-serif" >So as a practical matter, is this an urgent problem...? Why? How?</span><br>_______________________________________________<br>gpfsug-discuss mailing list<br>gpfsug-discuss at <a href="http://spectrumscale.org" target="_blank">spectrumscale.org</a></div></blockquote></div></div>
<div><div><div>—</div>
<div>Kevin Buterbaugh - Senior System Administrator</div>
<div>Vanderbilt University - Advanced Computing Center for Research and Education</div>
<div><a href="mailto:Kevin.Buterbaugh@vanderbilt.edu" target="_blank">Kevin.Buterbaugh@vanderbilt.edu</a> - (615)875-9633</div></div></div>
<div><font face="Default Monospace,Courier New,Courier,monospace" size="2" >_______________________________________________<br>gpfsug-discuss mailing list<br>gpfsug-discuss at spectrumscale.org<br><a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss" target="_blank">http://gpfsug.org/mailman/listinfo/gpfsug-discuss</a></font></div></blockquote>
<div dir="ltr" > </div></div>
<BR>