Story #18179

Better spot instance support

Added by Peter Amstutz 8 months ago. Updated about 2 months ago.

Status:
New
Priority:
Normal
Assigned To:
-
Target version:
-
Start date:
03/01/2022
Due date:
07/31/2022
% Done:

0%

Estimated time:
Story points:
-
Release:
Epics
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?

Related issues

Related to Arvados - Feature #18180: Ability to control use of spot instances on a per-workflow and step levelResolved03/17/2022

Related to Arvados - Feature #18181: Ability to specify a % of compute instance price that user is willing to go over from cheapestNew

Related to Arvados - Feature #17695: [costanalyzer] make an accurate report for spot instances on AWSIn Progress

Related to Arvados - Bug #18101: [a-d-c] [AWS] add option to spin up (spot) instances in more/all availability zones in the regionNew

Related to Arvados - Feature #18596: Config option to enable preemptible variants of all instance typesResolved03/21/2022

Related to Arvados - Bug #18562: [api] should not change the preemptible flag across the boardResolved12/23/2021

Blocked by Arvados - Feature #18205: [api] [cloud] add live compute instance price to container recordNew

History

#1 Updated by Peter Amstutz 8 months ago

  • Start date set to 11/01/2021
  • Due date set to 03/31/2022

#2 Updated by Peter Amstutz 8 months ago

  • Description updated (diff)

#3 Updated by Peter Amstutz 8 months ago

  • Related to Feature #18180: Ability to control use of spot instances on a per-workflow and step level added

#4 Updated by Peter Amstutz 8 months ago

  • Related to Feature #18181: Ability to specify a % of compute instance price that user is willing to go over from cheapest added

#5 Updated by Ward Vandewege 8 months ago

  • Description updated (diff)

#6 Updated by Ward Vandewege 8 months ago

  • Related to Feature #17695: [costanalyzer] make an accurate report for spot instances on AWS added

#7 Updated by Ward Vandewege 8 months ago

  • Blocked by Feature #18205: [api] [cloud] add live compute instance price to container record added

#8 Updated by Peter Amstutz 7 months ago

  • Start date changed from 11/01/2021 to 01/01/2022

#9 Updated by Peter Amstutz 6 months ago

  • Start date changed from 01/01/2022 to 05/01/2022
  • Due date changed from 03/31/2022 to 07/31/2022

#10 Updated by Peter Amstutz 5 months 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

#11 Updated by Ward Vandewege 4 months ago

  • Related to Feature #18596: Config option to enable preemptible variants of all instance types added

#12 Updated by Ward Vandewege 4 months ago

  • Related to Bug #18562: [api] should not change the preemptible flag across the board added

#13 Updated by Ward Vandewege 4 months ago

  • Description updated (diff)

#14 Updated by Peter Amstutz about 2 months ago

  • Start date changed from 05/01/2022 to 03/01/2022

Also available in: Atom PDF