ubccr / coldfront

HPC Resource Allocation System
https://coldfront.readthedocs.io
GNU General Public License v3.0
96 stars 76 forks source link

Feature: Display a list of slurm accounts a user has on their home page #572

Open matthew-kusz opened 9 months ago

matthew-kusz commented 9 months ago

Description

I wanted a place where users could quickly see all of the slurm accounts they have without having to look inside their projects and allocations. This list would also include an example of how to use them when submitting a job. I created this list on the users home page and included some additional information like project title and the resources the slurm accounts are for. If this would be a useful feature in ColdFront I can create a PR of the changes I made. It adds some additional code to the slurm plugin. Here's what it looks like with the test data for the cgray user: slurm_account_list

Component

Other

Additional information

No response

dsajdak commented 9 months ago

Hi @matthew-kusz! This would be GREAT to have, in my opinion. I've got a really old feature request that is similar - see #372.

matthew-kusz commented 8 months ago

Sorry for the delay, I've started adding the additional details in #372. We only require the slurm account from coldfront when a user submits a job so I need some additional examples that'll help me figure out how the information should be shown. I'm not sure how the linked resources should be handled and if the information I'm showing is correct for partitions. This is all still from the cgray test data. Here's an example of what I have right now.

From the home page: slurm_home_page

From an allocation detail page with the University Metered HPC resource: slurm_allocation_detail_page

Once I have those figured out I need to do some clean up and I'll get a PR set up.

dsajdak commented 7 months ago

@matthew-kusz this is amazing!!! You should not need to specify anything for the linked resources as Slurm handles all of that. The only thing I'd add is for the University HPC, if the user didn't want to use the cluster default partition and qos they'd have to specify those, like you do for the other clusters but that might be handled by what you already have going here. This is really great!