[slurm-users] Accounting: set default account with no access
Brian Andrus
toomuchit at gmail.com
Tue Nov 6 07:55:21 MST 2018
But isn't that a user association setting and not an account setting? So
I would have to set it for every user/default account association, no?
Technically doable, but definitely more difficult to manage.
Brian Andrus
On 11/6/2018 3:58 AM, Yair Yarom wrote:
> Hi,
>
> You can set the maxsubmitjob=0 on that default account. That should
> prevent anyone from using it, but it won't have a specific message
> like with the lua plugin. E.g.
> sacctmgr update account default set maxsubmitjob=0
>
> Regards,
> Yair.
>
>
> On Tue, Nov 6, 2018 at 12:58 AM Renfro, Michael <Renfro at tntech.edu
> <mailto:Renfro at tntech.edu>> wrote:
>
> From https://stackoverflow.com/a/46176694:
>
> >> I had the same requirement to force users to specify accounts
> and, after finding several ways to fulfill it with slurm, I
> decided to revive this post with the shortest/easiest solution.
> >>
> >> The slurm lua submit plugin sees the job description before the
> default account is applied. Hence, you can install the slurm-lua
> package, add "JobSubmitPlugins=lua" to the slurm.conf, restart the
> slurmctld, and directly test against whether the account was
> defined via the job_submit.lua script (create the script wherever
> you keep your slurm.conf; typically in /etc/slurm/):
> >>
> >> -- /etc/slurm/job_submit.lua to reject jobs with no account
> specified
> >>
> >> function slurm_job_submit(job_desc, part_list, submit_uid)
> >> if job_desc.account == nil then
> >> slurm.log_error("User %s did not specify an
> account.", job_desc.user_id)
> >> slurm.log_user("You must specify an account!")
> >> return slurm.ERROR
> >> end
> >> return slurm.SUCCESS
> >> end
> >>
> >> function slurm_job_modify(job_desc, job_rec, part_list, modify_uid)
> >> return slurm.SUCCESS
> >> end
> >>
> >> return slurm.SUCCESS
>
> > On Nov 5, 2018, at 4:09 PM, Brian Andrus <toomuchit at gmail.com
> <mailto:toomuchit at gmail.com>> wrote:
> >
> > All,
> >
> > I am trying to figure the best way to require users to
> explicitly specify an account when submitting jobs (--account= )
> >
> > What I was thinking was to create a default account for the
> users that has no ability to submit any jobs, so if they don't
> specify, any submission would fail.
> >
> > What I'm not seeing is how to set such an option on an account.
> I was hoping to do something like cluster=none for it's access,
> but that is not allowed.
> >
> >
> > Is there a way to set an account to not have access to submit jobs?
> > Alternatively is there an easier way to require the --account=
> option for jobs?
> >
> >
> > Brian Andrus
> >
> >
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.schedmd.com/pipermail/slurm-users/attachments/20181106/dba7834b/attachment-0001.html>
More information about the slurm-users
mailing list