The simplest solution currently available is to write a job submit script to set the QOS based on the partition name. This means a single QOS per partition and requires a QOS be created for each partition. Or a very complicated job submit script.
But the previous message with this subject said that is changing in an upcoming release and available now for testing in a pre-release version. Carl > On Feb 19, 2015, at 3:01 PM, Chris Read <[email protected]> wrote: > > Greetings... > > We currently rely heavily on QOS based time and resource limits, but up until > recently have been running in a single partition. Now that we have multiple > partitions we've seen the need for some of these limits (for example GrpCPUs) > to be limited per partition. > > I see no easy way to do that right now other than creating new partitions, > which I don't want to do. Are there any plans to make this easy to do? > > Anyone else interested in such a feature? > > Thanks, > > Chris >
