Thanks Eric, the sorting worked well. I did the priority from 1 (highest) to 5 (lowest) so I have ascending order, but, it does not matter.
I have one more idea to implement, and would like to ask for opinion.
We have a lot of partitions (queues) and accounts associated with those partitions so it can be confusing for users to know what account/partition to use when. I wrote a small Python program called “myallocation” which prints the account/partition combinations available to user on each cluster, e.g.:
You have a general allocation on kingspeak. Account: chpc, Partition: kingspeak
You have a general allocation on kingspeak. Account: chpc, Partition: kingspeak-shared
You can use preemptable mode on kingspeak. Account: owner-guest, Partition: kingspeak-guest
You can use preemptable GPU mode on kingspeak. Account: owner-gpu-guest, Partition: kingspeak-gpu-guest
You have a GPU allocation on kingspeak. Account: kingspeak-gpu, Partition: kingspeak-gpu
I am debating how to present this information to the OOD users.
So, I am thinking about a workaround for now, putting that info at the bottom of each of the cluster status. That would make the page even more busy than it is, so, I am wondering if it would be possible to use a collapsible item. That is, the account/partition list would only expand by clicking on it. I see you have some mentions of that in the views/layout.erb, but I have never written an HTML like this so if it’s really possible like what I am thinking, do you have any reference on how that works?