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
Currently, SCR records the resource manager that was selected at configure time in config.py, which is what AutoResourceManager defaults to. To enable a single SCR install to support multiple systems having different resource managers and/or job launchers, we could improve the AutoResourceManager and AutoJobLauncher methods to try to guess the correct values based on their current environment.
For the resource manager, when running within an allocation, we could check for environment variables set by the host resource manager. For example, we could guess SLURM if SLURM_JOBID is defined. Since some users run Flux within an allocation of another resource manager, perhaps check for Flux first.
For the job launcher, since many resource managers include a job launcher, we could use the resource manager to guess the job launcher. For SLURM assume srun, for LSF assume jsrun, for Flux assume flux run, etc.
And we'll need a way for the user to declare the exact values to override any guesses.
The text was updated successfully, but these errors were encountered:
Currently, SCR records the resource manager that was selected at configure time in
config.py
, which is whatAutoResourceManager
defaults to. To enable a single SCR install to support multiple systems having different resource managers and/or job launchers, we could improve theAutoResourceManager
andAutoJobLauncher
methods to try to guess the correct values based on their current environment.For the resource manager, when running within an allocation, we could check for environment variables set by the host resource manager. For example, we could guess SLURM if
SLURM_JOBID
is defined. Since some users run Flux within an allocation of another resource manager, perhaps check for Flux first.For the job launcher, since many resource managers include a job launcher, we could use the resource manager to guess the job launcher. For SLURM assume
srun
, for LSF assumejsrun
, for Flux assumeflux run
, etc.And we'll need a way for the user to declare the exact values to override any guesses.
The text was updated successfully, but these errors were encountered: