Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Convert spot-az column to availability-zone #4

Open
bra-fsn opened this issue Oct 1, 2020 · 0 comments
Open

Convert spot-az column to availability-zone #4

bra-fsn opened this issue Oct 1, 2020 · 0 comments

Comments

@bra-fsn
Copy link
Owner

bra-fsn commented Oct 1, 2020

As #3 has pointed out, the current naming scheme is bad.
We should list US West (Los Angeles) in the us-west-2 region, as API endpoints are there.
Maybe the best solution for this would be to rename spot-az to availability-zone and handle the rest.
We should find mappings for other parameters, like the output of aws ec2 describe-availability-zones --all-availability-zones
gives:

{
            "State": "available",
            "OptInStatus": "not-opted-in",
            "Messages": [],
            "RegionName": "us-west-2",
            "ZoneName": "us-west-2-wl1-sfo-wlz-1",
            "ZoneId": "usw2-wl1-sfo-wlz1",
            "GroupName": "us-west-2-wl1",
            "NetworkBorderGroup": "us-west-2-wl1-sfo-wlz-1"
}

Other problems related to this include describe_spot_price_history doesn't seem to return spot prices for not-opted-in zones, so currently in order to fetch pricing data for them, we should opt-in for all, which may have other consequences.
Maybe we should use https://website.spot.ec2.aws.a2z.com/spotblocks-generic.js for fetching all prices, instead of relying on the API.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant