Actions
Feature #17249
closed
Make costanalyzer aware of preemptable instances
Story points:
-
Release:
Release relationship:
Auto
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
Updated by Ward Vandewege over 3 years ago
- Related to Feature #16106: [arvados-dispatch-cloud] Azure driver support for preemptible instances added
Updated by Peter Amstutz about 3 years ago
- Target version changed from To Be Groomed to 2021-02-17 sprint
Updated by Ward Vandewege about 3 years ago
- Status changed from New to In Progress
Updated by Ward Vandewege about 3 years ago
Ready for review in dfa749b3eacff1da33fe470a2a4af3e291defdcf on branch 17249-costanalyzer-preemptible
Updated by Peter Amstutz about 3 years ago
Ward Vandewege wrote:
Ready for review in dfa749b3eacff1da33fe470a2a4af3e291defdcf on branch 17249-costanalyzer-preemptible
LGTM.
Updated by Ward Vandewege about 3 years ago
- Status changed from In Progress to Resolved
Applied in changeset arvados|9135120ba24f505aa47655b6f3f6dca3450215d5.
Actions