Actions
Story #18179
open
Better spot instance support
Status:
In Progress
Priority:
Normal
Assigned To:
-
Target version:
-
Start date:
03/01/2022
Due date:
04/30/2023 (about 20 months late)
% Done:
0%
Estimated time:
Story points:
-
Release:
Release relationship:
Auto
Description
- Currently sitewide on/off choice, can't choose per-workflow
- Have to duplicate instance types in the config (obnoxious) (see #18596)
- Records the wrong price (uses price from instance type config not actual information from the cloud)
- Scheduling choices are too narrow, should be able to request different node types when the node you want isn't available
- Could we query spot prices on the fly to make scheduling decisions
- Try bigger instance types but only bid the spot price for the smallest node type
- Should eventually escalate to an on-demand instance if spot instance isn't available
- User should be able to communicate cost tolerance
- Want to try other availability zones, but requires feature of Keepstore running on compute nodes (#16516)
- Need better way to handle spot instance shutdown
- Maybe just always retry on a regular cost node
- Consider shutting down spot instances after a job because there is a timer?
- Need to research this more
- Can the VM be frozen / restored?
Updated by Peter Amstutz about 3 years ago
- Due date set to 03/31/2022
- Start date set to 11/01/2021
Updated by Peter Amstutz about 3 years ago
- Related to Feature #18180: Ability to control use of spot instances on a per-workflow and step level added
Updated by Peter Amstutz about 3 years ago
- Related to Feature #18181: Ability to specify a % of compute instance price that user is willing to go over from cheapest added
Updated by Ward Vandewege about 3 years ago
- Related to Feature #17695: [costanalyzer] make an accurate report for spot instances on AWS added
Updated by Ward Vandewege about 3 years ago
- Blocked by Feature #18205: [api] [cloud] add compute instance price to container record added
Updated by Peter Amstutz about 3 years ago
- Start date changed from 11/01/2021 to 01/01/2022
Updated by Peter Amstutz about 3 years ago
- Due date changed from 03/31/2022 to 07/31/2022
- Start date changed from 01/01/2022 to 05/01/2022
Updated by Peter Amstutz about 3 years ago
- Related to Bug #18101: [a-d-c] [AWS] add option to spin up (spot) instances in more/all availability zones in the region added
Updated by Ward Vandewege almost 3 years ago
- Related to Feature #18596: Config option to enable preemptible variants of all instance types added
Updated by Ward Vandewege almost 3 years ago
- Related to Bug #18562: [api] should not change the preemptible flag across the board added
Updated by Peter Amstutz over 2 years ago
- Start date changed from 05/01/2022 to 03/01/2022
Updated by Peter Amstutz over 2 years ago
- Due date changed from 07/31/2022 to 08/31/2022
Updated by Peter Amstutz over 2 years ago
- Due date changed from 08/31/2022 to 09/30/2022
- Status changed from New to In Progress
Updated by Peter Amstutz over 2 years ago
- Due date changed from 09/30/2022 to 11/30/2022
Updated by Peter Amstutz over 2 years ago
- Due date changed from 11/30/2022 to 04/30/2023
- Start date changed from 03/01/2022 to 01/01/2023
Updated by Peter Amstutz almost 2 years ago
- Start date changed from 01/01/2023 to 09/01/2022
Updated by Peter Amstutz almost 2 years ago
- Start date changed from 09/01/2022 to 03/01/2022
Actions