Bug #18075
closed
arvados-dispatch-cloud should respect Containers.MaxComputeVMs
Added by Peter Amstutz over 2 years ago.
Updated about 1 year ago.
Release relationship:
Auto
Description
While researching a customer question, I noticed that we have a config setting Containers.MaxComputeVMs which is not respected by arvados-dispatch-cloud. (It appears that it was previously used by the legacy "nodes" table and NodeManager). We should rename it to MaxInstances in the CloudVMs section and support it so users have a way to avoid blowing up their Arvados cluster by accident when they queue a really large workflow.
- Description updated (diff)
- Target version set to Future
- Target version deleted (
Future)
- Description updated (diff)
- Target version set to Future
- Story points set to 1.0
- Target version changed from Future to To be scheduled
- Assigned To set to Tom Clegg
- Description updated (diff)
- Target version changed from To be scheduled to 2023-02-01 sprint
- Status changed from New to In Progress
The code LGTM, just a couple of comments on documentation:
- The code comment for
AtQuota() might need some update to reflect the new behavior.
- The upgrade notes could also mention the deprecated config knob.
- Target version changed from 2023-02-01 sprint to 2023-02-15 sprint
- Status changed from In Progress to Resolved
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by