Actions
Feature #17695
open
[costanalyzer] make an accurate report for spot instances on AWS
Status:
In Progress
Priority:
Normal
Assigned To:
-
Category:
-
Target version:
-
Start date:
Due date:
% Done:
0%
Estimated time:
Story points:
-
Release:
Release relationship:
Auto
Description
It looks like AWS has a "DescribeSpotPriceHistory" API:
https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_DescribeSpotPriceHistory.html
https://docs.aws.amazon.com/cli/latest/reference/ec2/describe-spot-price-history.htmlThat could be used to calculate the actual spot price for a container marked as run on an "Preemptible" node. We'd have to make sure to only use this code if we're on AWS.
Related issues
Updated by Ward Vandewege over 2 years ago
- Related to Story #18179: Better spot instance support added
Updated by Ward Vandewege over 2 years ago
- Status changed from New to In Progress
I have a proof of concept that works, however:
- AWS credentials are required to get results
- the region/az needs to be specified, and we don't keep that information (it's not in node.json, the az is not even in our config, it's derived from the SubnetID)
- the spot price history only goes back 2 months (established empirically, I have not found this in any docs yet)
What this means is that we should add this functionality (calculating the cost of the job) to a-d-c or crunch-run, and that it should be added to the node.json file in the log collection. Costanalyzer can then just report that cost number directly, without having to do AWS api calls. And perhaps more importantly, we could also display it in Workbench2. Should we record it in the container record?
Update: we wrote this up in #18205
Updated by Ward Vandewege over 2 years ago
- Blocked by Feature #18205: [api] [cloud] add compute instance price to container record added
Updated by
Actions