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

Exposes job.PriorityClass.value as modifiable value #451

Merged

Conversation

mapk-amazon
Copy link
Contributor

Addresses this issue.
#450

Updated description according to afgane's input.

Co-authored-by: Enis Afgan <afgane@gmail.com>
galaxy/templates/priorityclass-job.yaml Outdated Show resolved Hide resolved
preemptionPolicy: Never
globalDefault: false
description: "Galaxy jobs will run when cluster resources are available and will not preempt existing workloads."
description: "By default, Galaxy jobs will not preempt existing workloads but will run when cluster resources are available. Depending on the cluster setup, the preemption value can be modified to prompt scaling of the cluster for the computation."
Copy link
Member

@nuwang nuwang Feb 15, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think some guidance on what values would elicit the desired behaviour in the autoscaler case would also be helpful. That is to say, at what priority value would the autoscaler scale up and schedule nodes?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you, sounds great!

Simplifying if/else by default as suggested by nuwang.

Co-authored-by: Nuwan Goonasekera <2070605+nuwang@users.noreply.github.com>
Fixing last line chomp.

Co-authored-by: Nuwan Goonasekera <2070605+nuwang@users.noreply.github.com>
@nuwang nuwang merged commit adfda49 into galaxyproject:master Feb 16, 2024
2 checks passed
@nuwang
Copy link
Member

nuwang commented Feb 16, 2024

@mapk-amazon Thanks for this! Looks good.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants