Configuration, prefixing, or wrappers for Slurm commands

[rcthomas]

We have multiple Slurm clusters accessible from the main system: The main system itself, one for GPU satellites, others for other satellites. Slurm commands in our setup are "selected" via module load esslurm though other centers may implement this another way (or not at all, and require you to ssh somewhere, whatever).

We handled this in JupyterHub with BatchSpawner by creating wrappers that include whatever it is you need to execute the right command. For instance, a wrapper script just loads the module/adjusts the environment and then passes through the command.

module load esslurm
exec "$@"

This could be a configurable, which may need to be a Callable so that the plug-in can determine what the right environment to wrapper looks like dynamically. I think this would also enable easy remote (e.g. ssh-based) actions.

Related: #43