You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
An item that comes up often when the team is making changes to the Slurm configuration is how submit jobs afterwards to test that the desired policy has taken effect.
We rely predominantly on users and their usage patterns to illustrate the downstream effects of a change. It would be nice to have a preview of these effects before the changes end up on the production cluster.
How difficult would it be to enable this in the Slurm Test Environment context as a first pass on running a set of test jobs against a desired config change that we'll ultimately make in the production environment?
The text was updated successfully, but these errors were encountered:
An item that comes up often when the team is making changes to the Slurm configuration is how submit jobs afterwards to test that the desired policy has taken effect.
We rely predominantly on users and their usage patterns to illustrate the downstream effects of a change. It would be nice to have a preview of these effects before the changes end up on the production cluster.
How difficult would it be to enable this in the Slurm Test Environment context as a first pass on running a set of test jobs against a desired config change that we'll ultimately make in the production environment?
The text was updated successfully, but these errors were encountered: