Actions
Feature #17249
closed
Make costanalyzer aware of preemptable instances
Start date:
02/04/2021
Due date:
% Done:
100%
Estimated time:
(Total: 0.00 h)
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?
Updated by 
Updated by
Actions