Project

General

Profile

Actions

Story #18179

open

Better spot instance support

Added by Peter Amstutz about 1 year ago. Updated 10 days ago.

Status:
In Progress
Priority:
Normal
Assigned To:
-
Target version:
-
Start date:
01/01/2023
Due date:
04/30/2023 (Due in about 7 months)
% 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?

Related issues

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

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

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

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

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

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

Actions
Blocked by Arvados - Feature #18205: [api] [cloud] add compute instance price to container recordResolvedTom Clegg08/08/2022

Actions
Actions #1

Updated by Peter Amstutz about 1 year ago

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

Updated by Peter Amstutz about 1 year ago

  • Description updated (diff)
Actions #3

Updated by Peter Amstutz about 1 year ago

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

Updated by Peter Amstutz about 1 year ago

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

Updated by Ward Vandewege about 1 year ago

  • Description updated (diff)
Actions #6

Updated by Ward Vandewege about 1 year ago

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

Updated by Ward Vandewege about 1 year ago

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

Updated by Peter Amstutz 11 months ago

  • Start date changed from 11/01/2021 to 01/01/2022
Actions #9

Updated by Peter Amstutz 11 months ago

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

Updated by Peter Amstutz 10 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
Actions #11

Updated by Ward Vandewege 9 months ago

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

Updated by Ward Vandewege 9 months ago

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

Updated by Ward Vandewege 9 months ago

  • Description updated (diff)
Actions #14

Updated by Peter Amstutz 6 months ago

  • Start date changed from 05/01/2022 to 03/01/2022
Actions #15

Updated by Peter Amstutz about 2 months ago

  • Due date changed from 07/31/2022 to 08/31/2022
Actions #16

Updated by Peter Amstutz 24 days ago

  • Status changed from New to In Progress
  • Due date changed from 08/31/2022 to 09/30/2022
Actions #17

Updated by Peter Amstutz 10 days ago

  • Due date changed from 09/30/2022 to 11/30/2022
Actions #18

Updated by Peter Amstutz 10 days ago

  • Start date changed from 03/01/2022 to 01/01/2023
  • Due date changed from 11/30/2022 to 04/30/2023
Actions

Also available in: Atom PDF