i see just standard textbox and the select widget is ignored.
Is there any good reason for that?
Isn’t that bug?
Indeed I’d prefer to use default attribute name because otherwise I’d be forced to use patched bc_desktop. This is indeed not un-doable but I like to be aligned with upstream and not letting every dnf update break my setup.
bc_queue is hard coded to be just a text field. We can change that so that you can override it (we just did it with bc_account because it was hard coded too).
That said - we’re also looking into auto populating partition information. Do you only have those 2 partitions?
I have more partitions at my cluster(s), but to bc_desktop users, only ‘gpu’ and ‘cpu’ partititions are relevant - other partitions are just defining different (worse) QoS.
Thanks, the trick there presented by @Micket with apps/dashboard/initializers/ood.rb is really nice.
It could be really useful to us to present eg. available Lmod/Easybuild software modules / conda environments, etc. to user in OOD gui. I have already one open request to implement conda/venv “bring-your-own” jupyterlab environment (conda+venv) so this can help me avoid hardcoding things into our Ansible.
Ah, sorry for possibly unclear wording.
I meant request of my user at my system, so it’s up to me to fix that and thanks to your hint above, I know how!