Feature #17249

Make costanalyzer aware of preemptable instances

Added by Ward Vandewege 8 days ago. Updated 8 days ago.

Status:
New
Priority:
Normal
Assigned To:
-
Category:
-
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Story points:
-

Description

When preemptible instances are used, the CR includes these values:

  "scheduling_parameters": {
    "preemptible": true
  },

At minimum, costanalyzer should include a 'preemptible' column in the CSV export.

The numbers it reports will be wrong when preemptible instances are used, because the cost data reported is the static unit cost for preemptable instances defined in the config file.

Perhaps it should even just refuse to report amounts for all preemptable instances?


Related issues

Related to Arvados - Feature #16106: [arvados-dispatch-cloud] Azure driver support for preemptible instancesResolved01/07/2021

History

#1 Updated by Ward Vandewege 8 days ago

  • Related to Feature #16106: [arvados-dispatch-cloud] Azure driver support for preemptible instances added

#2 Updated by Ward Vandewege 8 days ago

  • Description updated (diff)

Also available in: Atom PDF