[gpfsug-discuss] Dry-Run functionality

[Sobey, Richard A]

IMO I’d want to see an explanation of what will happen in plain English. “This will create a policy that moves any file bigger than 10MB and older than 30 days to storage pool XYZ”.

You might be able to tell I’ve never used GPFS policies except for initial placement so the above example might not be possible anyway ☺

I’m very used to the Powershell switch “-whatif” which basically said “I am going to do the following:”

Cheers

Richard

From: gpfsug-discuss-bounces at spectrumscale.org [mailto:gpfsug-discuss-bounces at spectrumscale.org] On Behalf Of Jez Tucker
Sent: 09 June 2016 16:21
To: gpfsug main discussion list <gpfsug-discuss at gpfsug.org>
Subject: [gpfsug-discuss] Dry-Run functionality

Hello all,

  I wonder if you could have your take on your ideal dry-run functionality.

Post London User Group, we had much feedback regarding the need for dry-run functionality.
Therefore we have implemented dry-run functionality for our GPFS/Scale Python API across all calls.

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
Pixit Media & ArcaStream
www.pixitmedia.com<http://www.pixitmedia.com>
www.arcastream.com<http://www.arcastream.com>

[Image removed by sender.]
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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20160620/62938bbe/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ~WRD000.jpg
Type: image/jpeg
Size: 823 bytes
Desc: ~WRD000.jpg
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20160620/62938bbe/attachment.jpg>