Ticket 3652

Summary:	How can we control which user gets access to special QOS?
Product:	Slurm	Reporter:	HMS Research Computing <rc>
Component:	Configuration	Assignee:	Moe Jette <jette>
Status:	RESOLVED INFOGIVEN	QA Contact:
Severity:	4 - Minor Issue
Priority:	---	CC:	tim
Version:	16.05.4
Hardware:	Linux
OS:	Linux
Site:	Harvard Medical School	Alineos Sites:	---
Atos/Eviden Sites:	---	Confidential Site:	---
Coreweave sites:	---	Cray Sites:	---
DS9 clusters:	---	HPCnow Sites:	---
HPE Sites:	---	IBM Sites:	---
NOAA SIte:	---	OCF Sites:	---
Recursion Pharma Sites:	---	SFW Sites:	---
SNIC sites:	---	Linux Distro:	---
Machine Name:		CLE Version:
Version Fixed:		Target Release:	---
DevPrio:	---	Emory-Cloud Sites:	---

Description HMS Research Computing 2017-03-31 12:54:35 MDT

Hello,

Currently on our cluster, it looks like a special QOS can be used by any user without any sort of privilege being assigned. 

For example, we have a QOS named testbump that can be used by every user simply by adding --qos=testbump to their submission line. How can we control which user gets access to a special QOS?

Thanks!
Kathleen

Comment 1 Tim Wickberg 2017-03-31 13:10:48 MDT

(Apologies for brevity, on my phone at the moment.)

Take a look at the AccountingStorageEnforce option in the slurm.conf man page (online at https://slurm.schedmd.com/slurm.conf.html).

AccountingStorageEnforce=safe,qos

is our usual recommendation.

Moe should be covering that as part of your training session next week. Let me know if you have any further questions.

- Tim

Comment 2 Moe Jette 2017-04-07 07:14:27 MDT

Do you have any more questions related to this?

Comment 3 HMS Research Computing 2017-04-07 08:21:16 MDT

Not right now, this ticket can be closed.

Thank you for the help

Raffaele

Comment 4 Moe Jette 2017-04-07 08:21:51 MDT

Thanks for the update.