<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi Marc,<br>
<br>
Quite. We have had coverage of (1) and (2) in the API for some
time.<br>
<br>
My overriding thought is that (QoS aside) if one executes an
mmapplypolicy, for whatever reason, then a certain amount of
resource is consumed.<br>
This may not be preferred.<br>
<br>
So let me rephrase to the users: in your real-world working
environment, would you prefer:<br>
<br>
a) <font size="3">Return what would be called. E.G. mmapplypolicy
-P mypol.pol --flag1
--flag2 --etc which is a sanity check, but not a policy run,
hence no load</font><br>
<font size="3">b) </font><big><font size="2"><big>mmapplypolicy
/gpfs-path -P policy-rules-file
-I test -L 2 [other options]` will do a dry run and
show what actions would be performed on each file.<br>
<br>
To be clear; you can currently achieve either launch with the
API as it stands.<br>
However we'd like to know what the general concensus would
prefer to be the norm in such an implementation.<br>
<br>
Regarding dry run functionality this can be achieved globally
as follows:<br>
<br>
setDryRun(True)<br>
<API commands to delete filesets><br>
<API commands to delete snapshots><br>
<API commands to migrate data><br>
<br>
or as a more granular decorator:<br>
<br>
@dryrun<br>
... def delete_filesets(): <br>
</big></font></big><big><font size="2"><big><big><font size="2"><big>
<API commands to delete filesets><br>
<br>
Jez<br>
<br>
<br>
</big></font></big></big></font></big>
<div class="moz-cite-prefix">On 20/06/16 16:03, Marc A Kaplan wrote:<br>
</div>
<blockquote
cite="mid:OF82EC559A.9BCAF63A-ON85257FD8.0050D07C-85257FD8.0052BF24@notes.na.collabserv.com"
type="cite"><font face="sans-serif" size="2"><b>Jez,</b></font><br>
<br>
<font face="sans-serif" size="2"> Regarding your recent post. Do
the mmchpolicy and mmapplypolicy commands have sufficient
functionality
for your purposes? </font><br>
<font face="sans-serif" size="2">Are you suggesting some
improvements?
If so, what? Please provide examples and/or specific
suggestions.</font><br>
<br>
<font face="sans-serif" size="2">WRT your numbered items:</font><br>
<br>
<font face="sans-serif" size="2">(1) `mmchpolicy fsname -I
policy-rules-file test` does a complete syntax check on
policy-rules-file
and some other sanity checking.</font><br>
<br>
<font face="sans-serif" size="2">(2) `mmapplypolicy
/gpfs-path/empty-directory
-P policy-rules-file -I test -L 0` is another way to validate
policy-rules-file.
Rules like MIGRATE and LIST that are interpreted by
mmapplypolicy
will be scrutinized. For example check that each named pool is
defined
either within the file system or by an EXTERNAL POOL rules.</font><br>
<br>
<font face="sans-serif" size="2">(3) `mmapplypolicy /gpfs-path -P
policy-rules-file
-I test -L 2 [other options]` will do a dry run and
show what actions would be performed on each file.<br>
</font><br>
<br>
<font face="sans-serif" size="2">--marc</font><br>
<br>
<font face="sans-serif" size="2">-----------</font><br>
<br>
<font face="Times New Roman" size="3">API calls for Policies have
the
ability to run in 'test' or 'run' mode. (ref: man
mmapplypolicy)<br>
<br>
How would you expect to use dry-run functionality on a policy?<br>
We have our own opinion, but we'd like to hear yours.<br>
<br>
1) Validate the policy and print the policy content to
stdout/other. No
mmapplypolicy is performed.<br>
2) Validate the policy and enforce mmapplypolicy with -I test<br>
3) Return what would be called. E.G. mmapplypolicy -P mypol.pol
--flag1
--flag2 --etc<br>
4) Other<br>
<br>
Best regards,<br>
<br>
Jez</font><br>
<font face="Times New Roman" size="3">-- </font><br>
<font face="Arial" size="3">Jez Tucker<br>
Head of Research & Development</font><font face="Arial"
color="red" size="3"><br>
</font><br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
gpfsug-discuss mailing list
gpfsug-discuss at spectrumscale.org
<a class="moz-txt-link-freetext" href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss">http://gpfsug.org/mailman/listinfo/gpfsug-discuss</a>
</pre>
</blockquote>
<br>
<br>
<div class="moz-signature">-- <br>
<div>
<font face="arial" color="#000000">
Jez Tucker<br>
Head of Research & Development<br>
<font color="#FF0000">Pixit Media</font><br>
<a href="http://www.pixitmedia.com">www.pixitmedia.com</a><br>
</font>
</div>
</div>
</body>
</html>
<br>
<div><img src="http://pixitmedia.com/sig/sig-cio.jpg"></div><div>This email is confidential in that it is intended for the exclusive attention of the addressee(s) indicated. If you are not the intended recipient, this email should not be read or disclosed to any other person. Please notify the sender immediately and delete this email from your computer system. Any opinions expressed are not necessarily those of the company from which this email was sent and, whilst to the best of our knowledge no viruses or defects exist, no responsibility can be accepted for any loss or damage arising from its receipt or subsequent use of this email.</div>