Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Planned changes to allocations to allow for per-reservation and per-group modifications #3323

Closed
2 tasks
antgonza opened this issue Oct 30, 2023 · 1 comment · Fixed by #3331
Closed
2 tasks

Comments

@antgonza
Copy link
Member

Supersedes: #3322

  • For special circumstances, like a class, users will have the opportunity to add a specific reservation during the analysis creation via a GUI text entry box. This will allow that in special circumstances those jobs will go to that reservation, if it exists, if it doesn't, it will be ignored. This new parameter will be added to the submission as '--reservation name_entried'. To be clear, this will only be available for analysis, which are normally the main feature we use for classes and workshops, and that the reservation will need to be created in advance by Jeff.

  • Each user level group will be able to have database entries (vs. hard coded values) that will overwrite the specific submission; this can be extra "nice" values, different "queue", etc. This will allow the wet-lab users have a higher priority than anyone else in the system, then admins, then the rest.

charles-cowart pushed a commit that referenced this issue Nov 22, 2023
* adding fixes and GUI

* small fixes after deploy

* slurm_reservation[0]

* jobs special cases

* fix test
@antgonza antgonza linked a pull request Nov 22, 2023 that will close this issue
@antgonza
Copy link
Member Author

antgonza commented Jan 9, 2024

fixed on #3330

@antgonza antgonza closed this as completed Jan 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant