The execute module provides the dry run functionality. Dry run allows users to see what GPFS commands would be run by a piece of code without executing them.
Commands are added to a command cache that can be retrieved using the
When dry run mode is activated, commands are added to the cache
until dry run mode is de-activated. Each time dry run mode is activated, the command cache is cleared.
Dry run may cause some unexpected or undefined behaviour within the API, or may cause API methods to fail. In particular, when the API expects some response from the command call, an error will likely be raised.
The decorator or context manager will attempt to catch these dry run side-effect errors and write them to logging. Be aware that this may also catch errors that are not side effects of dry run, and that would otherwise be raised during normal execution. It is good practice to check logging for errors before re-running code outside of dry run mode.
Changing objects in dry run mode may result in those objects being changed within the API, but these chages will not be reflected on the Filesystem. E.G.
>>> setDryRun(True) >>> >>> fs.snapshots.new('test-snap') >>> >>> 'test-snap' in fs.snapshots True >>> fs = Filesystem('mmfs1') # reload Filesystem object >>> 'test-snap' in fs.snapshots False
When the commands returned by dry run are actually executed on the Filesystem they may raise errors which aren’t presented by the dry run. E.G. In the decorator example below, attempting to delete the root fileset would raise an error outside of dry run.
In practice the returned commands would be run as sudo, however this is ommitted from the returned commands.
Dry run functionality is meant to be used with commands that don’t already provide test run functionality -
E.G. when running a
you should use the
action='test' option rather than using dry run.
Dry run will only return the
mmapplypolicy command that would be run on GPFS.
Be aware that decorators and context managers automatically deactivate dry run mode on exit - even if
setDryRun(True) has been used.
Sets dry run mode, which will stop non-readonly commands from executing on the filesystem.
Any ‘caught’ commands will be printed.
The commands are also stored in a command cache which can be retrieved using the
Clear the command cache
Returns the cache of commands which were caught and not executed during a dry run.
Return type: list
Set whether the commands, which are captured by dry run, are shown on screen. E.G.
>>> setShowDryRunCmds(True) >>> >>> fs.snapshots['global-snapshot1'].delete() INFO:arcapix.dryrun:mmdelsnapshot mmfs1 global-snapshot1
Special class that can be used as a context manager or a decorator to run certain pieces of code as dry run.
Set Dry Run globally¶
>>> from arcapix.fs.gpfs.execute import setDryRun, getCmdCache >>> from arcapix.fs.gpfs import Filesystem >>> >>> setDryRun(True) >>> >>> fs = Filesystem('mmfs1') >>> >>> for s in fs.snapshots.values(): ... s.delete() ... >>> print getCmdCache() ['mmdelsnapshot mmfs1 global-snapshot1', 'mmdelsnapshot mmfs1 snap_test']
Dry Run decorator¶
>>> from arcapix.fs.gpfs.execute import dryrun, getCmdCache >>> from arcapix.fs.gpfs import Filesystem >>> >>> fs = Filesystem('mmfs1') >>> >>> @dryrun ... def delete_filesets(): ... for f in fs.filesets.values(): ... f.delete(True, True, True) ... >>> delete_filesets() >>> >>> print getCmdCache() ['mmunlinkfileset mmfs1 root -f', 'mmdelfileset mmfs1 root -f', 'mmdelfileset mmfs1 sata1-cg-projects -f']
Dry Run a single method¶
>>> from arcapix.fs.gpfs.execute import dryrun, getCmdCache >>> from arcapix.fs.gpfs import Filesystem >>> >>> fs = Filesystem('mmfs1') >>> >>> dryrun(fs.change)(manager='sn02') >>> >>> print getCmdCache() ['mmchmgr mmfs1 sn02']
Dry Run context manager¶
>>> from arcapix.fs.gpfs.execute import dryrun, getCmdCache >>> from arcapix.fs.gpfs import Filesystem >>> >>> fs = Filesystem('mmfs1') >>> >>> with dryrun(): ... fs.snapshots.new('snaptest') ... >>> print getCmdCache() ['mmcrsnapshot mmfs1 snaptest']