Project

General

Profile

Actions

Idea #18179

open

Better spot instance support

Added by Peter Amstutz about 3 years ago. Updated 7 months ago.

Status:
In Progress
Priority:
Normal
Assigned To:
-
Target version:
Start date:
03/01/2022
Due date:
06/30/2024 (about 4 months late)
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/2022Actions
Related to Arvados - Feature #18181: Ability to specify a % of compute instance price that user is willing to go over from cheapestNewActions
Related to Arvados - Feature #17695: [costanalyzer] make an accurate report for spot instances on AWSNewActions
Related to Arvados - Bug #18101: [a-d-c] [AWS] add option to spin up (spot) instances in more/all availability zones in the regionResolvedActions
Related to Arvados - Feature #18596: Config option to enable preemptible variants of all instance typesResolvedTom Clegg03/21/2022Actions
Related to Arvados - Bug #18562: [api] should not change the preemptible flag across the boardResolvedTom Clegg12/23/2021Actions
Related to Arvados - Feature #19961: Detect and log spot instance interruption noticesResolvedTom Clegg02/16/2023Actions
Related to Arvados - Feature #19320: Get actual instance price information by calling AWS APIsResolvedTom Clegg01/23/2023Actions
Related to Arvados - Feature #19982: Ability to know when a container died because of spot instance reclamation and option to resubmitResolvedPeter AmstutzActions
Related to Arvados - Feature #16316: a-c-r handles resource range requests (especially CPU) and adjusts requests based on what is in InstanceTypes listIn ProgressActions
Related to Arvados - Feature #19675: Panel that lists configured instance typesResolvedStephen Smith12/05/2023Actions
Related to Arvados - Feature #20979: Research spot instance retry strategiesNewSarah ZaranekActions
Related to Arvados - Feature #20978: Support multiple candidate instance types to assign containersResolvedTom Clegg10/31/2023Actions
Related to Arvados - Feature #21460: spot instance reclamation is triggers "at capacity" cooloffNewActions
Blocked by Arvados - Feature #18205: [api] [cloud] add compute instance price to container recordResolvedTom Clegg08/08/2022Actions
Actions

Also available in: Atom PDF