Actions
Bug #18075
open
arvados-dispatch-cloud should respect Containers.MaxComputeVMs
Start date:
Due date:
% Done:
0%
Estimated time:
(Total: 0.00 h)
Story points:
1.0
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.
Updated by Peter Amstutz about 2 years ago
- Description updated (diff)
- Target version deleted (
To be groomed)
Updated by Tom Clegg about 2 years ago
- Description updated (diff)
- Assigned To set to Tom Clegg
- Target version changed from To be groomed to To be scheduled
- Story points set to 1.0
Updated by Peter Amstutz about 2 years ago
- Target version changed from To be scheduled to 2023-02-01 sprint
Actions