You would have to do such syncing with your own scripts. There is no way
slurm would be able to tell which users should have access and what
access without the slurmdb and such info is not contained in AD.
At our site, we iterate through the group(s) that are slurm user groups
and add the users if they do not exist. We also delete users when they
are removed from AD. This does have the effect of losing job info
produced by said users, but since we export that into a larger historic
repository, we don't worry about it.
So simple case is to iterate through an AD group which your slurm users
belong to and add them to slurmdbd. Once they are in there, you can set
defaults with exceptions for specific users.
If you are only looking to have settings apply to all users, you don't
have to import the users. Set the QoS for the partition.
Brian Andrus
On 11/20/2023 1:45 PM, ego...@posteo.me wrote:
Hello,
I'd like to configure some sort of partition QoS so that the number of
jobs or cpus is limited for a single user.
So far my testing always depends on creating users within the
accounting database however I'd like to avoid managing each user and
having to create or sync _all_ LDAP users also within Sturm.
Or - are there solutions to sync LDAP or AzureAD users to the Slurm
accounting database?
Thanks for any input.
Best - Eg.
