[External Email] This email originated outside of Trinity College Dublin. Do not click links or open attachments unless you recognise the sender and know the content is safe.

Hi,
I'm going to have the following situation on my hands and I would like to ask for some suggestions how to solve this in slurm. We're talking about a cluster that is not yet operational so there are no real legacy configs that one needs to take into account.

I have two sets of physical nodes:
1. node01 - nodeXX: General Purpose Nodes. Everybody can use them
2. project_A_01 - project_A_XX: These nodes come with some restrictions regarding who can and who must not run jobs on them.

Users are organized into accounts, pseudohierarchically representing workgroups / projects etc within the university. For instance, there is going to be a "physics" account with "project_blackhole", "workgroup_miller" as children. Users are associated with one or more accounts.

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.

In the future, there might be more project specific nodes for other projects.

I would be grateful for any alternative solution or hints, how this could be solved optimally.

Thanks a lot!
Thomas

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