[gpfsug-discuss] Dry-Run functionality ?

[Marc A Kaplan]

Jez,

  Regarding your recent post.  Do the mmchpolicy and mmapplypolicy 
commands have sufficient functionality for your purposes? 
Are you suggesting some improvements?  If so, what?  Please provide 
examples and/or specific suggestions.

WRT your numbered items:

(1)  `mmchpolicy fsname  -I  policy-rules-file test`   does a complete 
syntax check on policy-rules-file and some other sanity checking.

(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.

(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.


--marc

-----------

API calls for Policies have the ability to run in 'test' or 'run' mode. 
(ref: man mmapplypolicy)

How would you expect to use dry-run functionality on a policy?
We have our own opinion, but we'd like to hear yours.

1) Validate the policy and print the policy content to stdout/other.  No 
mmapplypolicy is performed.
2) Validate the policy and enforce mmapplypolicy with -I test
3) Return what would be called.  E.G. mmapplypolicy -P mypol.pol --flag1 
--flag2 --etc
4) Other

Best regards,

Jez
-- 
Jez Tucker
Head of Research & Development


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20160620/ce640efd/attachment-0001.htm>