Hello there, we have three different clusters two of them currently federated, we want to consider the following scenarios we need your input on how to handle them: - clusterA and clusterB federated - clusterA and clusterC federated - clusterB and clusterC federated - three clusters federated Are there excluding options or can we have all of them on a single configuration? Please advise. Thanks, -Hugo
Hello Hugo, A cluster can only be a member of one federation at a time. So, your listed federation configurations are all mutually exclusive with each other. Please refer to (https://slurm.schedmd.com/federation.html) for more information. Any follow up questions? Thanks, Skyler
Skyler, if this is the case, then the option for the three clusters federated is a valid one, right? If this is true, then can I do something like this: - user can submit a job to land on any of the three clusters as they are federated - user can submit a job to land only in two of the three clusters in the federation excluding the third cluster Is this the case? Thanks, -Hugo
Hugo, > user can submit a job to land on any of the three clusters as > they are federated Submit normally. > user can submit a job to land only in two of the three clusters > in the federation excluding the third cluster Submit with flag `-M` or `--clusters=<string>` For example, I have clusters fed[0-2] in federation and I run the below command. This submits a job that will be sent to fed0 and fed2 but not fed1. > sbatch --clusters=fed0,fed2 --wrap "sleep 1m" Regards, Skyler
Got it. Thank you!
Skyler, one more question. Let's say we have the three-clusters federation. How it should look their configuration if we want X users from account Y to have high priority access to clusterA and low priority access to clusterB & clusterC, is this doable? Thanks, -Hugo
Hi Hugo, (In reply to NASA JSC Aerolab from comment #5) > Skyler, one more question. Let's say we have the three-clusters federation. > How it should look their configuration if we want X users from account Y to > have high priority access to clusterA and low priority access to clusterB & > clusterC, is this doable? Yes this is doable. Just adjust account priority on each cluster as needed. For your example case, run the following commands depending on use case: [case a] Intention: I want to just limit the entire account. > sacctmgr modify account set Priority=100 where account=acctY cluster=clusterA > sacctmgr modify account set Priority=1 where account=acctY cluster=clusterB,clusterC [case b] Intention: I want to just limit a subset of users on an account. Assuming that acctY contains users "user[A,B,C]" and I want to limit "user[A,B]". > sacctmgr modify user set Priority=100 where user=userA,userB account=acctY cluster=clusterA > sacctmgr modify user set Priority=1 where user=userA,userB account=acctY cluster=clusterB,clusterC Note: `Priority=100` and `Priority=1` are arbitrary values. Please use values that make sense for your site(s). You can also use both methods together. Does this method work for you? Is that the priority access you mean? Regards, Skyler
Great! This is what we are looking for. I will try this on emulated clusters.
It seems like the information was sufficient. Closing ticket. If you have more questions, please re-open the ticket and I will be more than happy to answer them. Regards, Skyler
