[slurm-users] GrpTRESMins and GrpTRESRaw usage

[gerard.gil at cines.fr]

Hi Miguel,

> Why not? You can have multiple QoSs and you have other techniques to change
> priorities according to your policies.

Is this answer my question ?

"If all configured QOS use NoDecay, we can take advantage of the FairShare priority with Decay and  all jobs GrpTRESRaw with NoDecay ?"

Thanks

Best,
Gérard 


----- Mail original -----
> De: "Miguel Oliveira" <miguel.oliveira at uc.pt>
> À: "Slurm-users" <slurm-users at lists.schedmd.com>
> Cc: "slurm-users" <slurm-users at schedmd.com>
> Envoyé: Vendredi 24 Juin 2022 13:09:47
> Objet: Re: [slurm-users] GrpTRESMins and GrpTRESRaw usage

> Hi Bjørn-Helge,
> 
> Long time!
> 
> Why not? You can have multiple QoSs and you have other techniques to change
> priorities according to your policies.
> 
> Best,
> 
> MAO
> 
>> On 24 Jun 2022, at 11:53, Bjørn-Helge Mevik <b.h.mevik at usit.uio.no> wrote:
>> 
>> Miguel Oliveira <miguel.oliveira at uc.pt> writes:
>> 
>>> It is not exactly true that you have no solution to limit projects. If
>>> you implement each project as an account then you can create an
>>> account qos with the NoDecay flags.
>>> This will not affect associations so priority and fair share are not impacted.
>> 
>> Yes, that will work.  But it has the drawback that you cannot use QoS'es
>> for *anything else*, like a QoS for development jobs or similar.  So
>> either way it is a trade-off.
>> 
>> --
>> Regards,
>> Bjørn-Helge Mevik, dr. scient,
>> Department for Research Computing, University of Oslo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2065 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.schedmd.com/pipermail/slurm-users/attachments/20220624/47c14be2/attachment-0002.bin>