[slurm-users] Dummy Slurm jobs?

[Grigory Shamov via slurm-users]

HI All,

Is it possible, or have it been done, to create dummy Slurm jobs that would start, block the resource, execute prologue and epilogue, but never execute the batch script body?

The idea is to start something in prologue, like a user/job/credential-specific instance of a proxy (say, nginx) controlled/scheduled by Slurm, but without giving users ability to run an arbitrary script in the job's script body.

Thanks!

--
Grigory Shamov
Site Lead / HPC Specialist
University of Manitoba and DRI Alliance Canada







--
slurm-users mailing list -- slurm...@lists.schedmd.com
To unsubscribe send an email to slurm-us...@lists.schedmd.com

[Davide DelVento via slurm-users]

Hi Grigory,

None of these are answers to your questions, but perhaps they might give you alternative ideas.

When I have this sort of needs I simply put something like "sleep 3600" in the body of the script and be done with it. Now, hinted in this message it seems like your users are not so well behaved and you want THEM to submit a job of their choice, potentially one that they should not have, but YOU want to stop it from ever executing, then I have not attempted to achieve it with Slurm. If Slurm does not support such a thing, you may consider other ways to create a "jail" for the users for example with cgroup, container or other means so that they simply could not do anything.

Alternatively, if this is more about avoiding mistakes and adding convenience, you could create a script carefully crafted in the way you want/need (say "startnginx"), put it in everybody's path and let them run that command instead of dealing with slurm for this purpose.

Have a great weekend!

[John Hearns via slurm-users]

Surely an interactive job would do what you want?  What is the exact requirement?

Long time ago I managed systems with PBS, including a big SGI Ultraviolet.
We had engineers log in and submit interactive jobs to reserve cores and RAM for visualisation jobs.