Feature #17249
Make costanalyzer aware of preemptable instances
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
History
#1
Updated by Ward Vandewege 8 days ago
Updated by - 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)
