"thomas.hartmann--- via slurm-users" <slurm-users@lists.schedmd.com> writes:
> I have three sets of accounts (each can have child accounts): > 1. "General" accounts: These are allowed to use all physical nodes. > 2. "ForProfit" accounts: These absolutely must not use the project_A_* nodes > 3. "Project_A" accounts: Their jobs should run first and foremost on the > project_A_* nodes but they are also allowed to run on the node* nodes. > > My first idea would be to create two partitions, one with all nodes in > there and a second one with only those nodes that the "ForProfit" are > allowed to use. Using "AllowAccounts" or "DenyAccounts" would > implement the restriction I need. That will work, but will not ensure that Project_A jobs first land on the projectt_A_* nodes (unless you give these nodes a lower weight - but then the General jobs will also start there first). You could add a third partition with the project_A_* nodes, and only give Project_A access to it. You can then give this partition a higher PriorityTier than the other partitions, meaning that jobs asking for that partitions will be scheduled first. Users of project_A should then submit jobs with -p project_A_part,General_part, or you could add some logic in your job_submit.lua that makes sure this happens. -- Regards, Bjørn-Helge Mevik, dr. scient, Department for Research Computing, University of Oslo
signature.asc
Description: PGP signature
-- slurm-users mailing list -- slurm-users@lists.schedmd.com To unsubscribe send an email to slurm-users-le...@lists.schedmd.com
