Hi: The below might be a starting point. There could be syntax or core concept errors :).
- Make two partitions. Both of them contain all nodes of interest: bigger_p smaller_p - Make two reservations, like scontrol create reservationname=20core_res Partition=bigger_p CoreCnt=20 scontrol create reservationname=16core_res Partition=smaller_p CoreCnt=16 - Tell the users, or job_submit.lua, to have 'bigger_p' jobs request '20core_res', and 'smaller_p' jobs request '16core_res' For ACL and/or granular resource limit control, you could make bigger_qos and smaller_qos, and define those as 'QOS' in the matching PartitionName entries. Then add whatever ACL or limits you want to those QOSes. Or use the PartitionName entries if the available options suffice. -- Paul Brunk, system administrator Georgia Advanced Resource Computing Center Enterprise IT Svcs, the University of Georgia On 2/11/22, 10:48 AM, "slurm-users" <slurm-users-boun...@lists.schedmd.com> wrote: [EXTERNAL SENDER - PROCEED CAUTIOUSLY] I see at https://slurm.schedmd.com/cons_res_share.html that there are some ways to share a node between partitions but I don't see how to specify a set number of cores to each partition. Is this possible? If I have some nodes with 36 cores, is there a way to make 16 of them be in one partition and 20 be in the other? Thanks, Steve
