-
Notifications
You must be signed in to change notification settings - Fork 39
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
Exposes job.PriorityClass.value as modifiable value #451
Conversation
Updated description according to afgane's input. Co-authored-by: Enis Afgan <afgane@gmail.com>
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." |
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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>
@mapk-amazon Thanks for this! Looks good. |
Addresses this issue.
#450