On 18-08-2020 17:36, Jason Simms wrote:
Hello everyone! We have a script that queries our LDAP server for any
users that have an entitlement to use the cluster, and if they don't
already have an account on the cluster, one is created for them. In
addition, they need to be added to the Slurm
Script. Not doing manual anything if it can at all be avoided, way to
error prone.
We have a cron job that does all of that. Checks if there are users or
groups in LDAP that aren't in SLURM yet, and adds them - that's adding
accounts, adding users, I think it also removed users/accounts
Without preemption there is no way in your scenario to ensure all nodes
won't be used by "high priority" jobs merely because it is
(theoretically) possible for all jobs to be high priority until the
cluster is full before the first low priority job is submitted. You
would need to decide how to
The PowerShell script I use to provision new users adds them to an Active
Directory group for HPC, ssh-es to the management node to do the sacctmgr
changes, and emails the user. Never had it fail, and I've looped over entire
class sections in PowerShell. Granted, there are some inherent delays
We manage this via our job_submit.lua script. At submission time the
script looks to see if they already have an account or not and if they
don't it adds them. To lower impact on the database we have it cache
the lookups.
I think the real concern is continually beating on the database. So
Hello everyone! We have a script that queries our LDAP server for any users
that have an entitlement to use the cluster, and if they don't already have
an account on the cluster, one is created for them. In addition, they need
to be added to the Slurm database (in order to track usage, FairShare,
Brian Andrus wrote:
> Most likely, but the specific approach depends on how you define what
> you want.
My idea was "high prio job is next unless are are too many of them".
> For example, what if there are no jobs in high pri queue but many in
> low? Should all the low ones run?
Yes.
> What
Prentice Bisbal wrote:
>> I'm wondering if it's possible to have slurm 19 run two partitions (low
>> and high prio) that share all the nodes and limit the high prio
>> partition in number of nodes used simultaneously without requiring to
>> manage the users in the database.
> Yes, you can do this
