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>
--
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.
_______________________________________________
gpfsug-discuss mailing list
gpfsug-discuss at spectrumscale.org
http://gpfsug.org/mailman/listinfo/gpfsug-discuss
