We've got a cluster set up based on the condo model.
We are using QOS to carve out chunks of the cluster for use by specific
customers.
Each group of customers owns a QOS. Each member of this group belongs to the
"normal" QOS and also to one of these
privileged QOS's.
What we discovered today is that users are not limited to using their own QOS,
but can in fact specify another QOS in their
sbatch scripts etc.
Now before anyone asks, the account for each user is configured to only have
access to the normal QOS and a specifica privileged QOS.
sacctmgr show association format=user,account,qos,defaultqos
User Account QOS Def QOS
---------- ---------- -------------------- ---------
mkatic arazdan arazdan,normal arazdan
According to my understanding of the above, this user should only have access
to the normal and arazdan QOS's.
Yet if I "su" to this account, I can launch jobs under other QOS's
Is there some configuration gotcha that I'm unaware of?
Thanks,
Lee Reynolds
Systems Analyst Principal
ASU Advanced Computing Center
a2c2.asu.edu
GWC-558
480.965.9460 (Office)
480.458.7434 (Mobile)
Have an A2C2 related question or problem?
Just send an email to the following address detailing
the nature of the question or problem and a service request
will be created automatically:
supp...@hpchelp.asu.edu
