remove qos
attribute from QueueInfo
#892
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The definition for
QueueInfo.qos
is "The QoSes associated with this queue", which is a little vague. In Slurm, Partition QOS is a rather niche feature:AccountInfo.qos
shows which QOSes the user can use to schedule jobs via that account.JobInfo.qos
shows which QOS a job is using.QueueInfo.qos
pertains only to the resource limits being enforced by slurm, and is completely opaque to the user even in the Slurm command line. If OOD is to be a "rosetta stone" and maintain a model of resource management with maximum compatibility, I don't think this should be part of that model.I can't find any usage of this attribute. Please strike down this PR if I'm just not understanding or if this attribute is important.
note: it's assumed to be a list, but slurm documentation implies that it should be just one QOS. I tried to make slurm barf with
SLURM_CONF=/tmp/slurm.conf.test scontrol show partition foobar
, with multiple QOS for thefoobar
partition in/tmp/slurm.conf.test
, but it semeed to ignore my file and just print the partition information from production. I don't currently have a containerized slurmctld that I can break, so I'm not sure if multiple partition QOS is an error or not.