Skip to content

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

@antgonza

Description

@antgonza

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions