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

Feature request: spot price, flexible CUD #55

Open
Jonathanliu92251 opened this issue Feb 1, 2023 · 6 comments
Open

Feature request: spot price, flexible CUD #55

Jonathanliu92251 opened this issue Feb 1, 2023 · 6 comments
Assignees
Labels
enhancement New feature or request

Comments

@Jonathanliu92251
Copy link

Currently, the calculator can't provide compute offerings' spot and flexible CUD price which are important price types besides hour, month, cud-1y, cud-3y.

@Jonathanliu92251 Jonathanliu92251 added the enhancement New feature or request label Feb 1, 2023
@samlhuillier
Copy link

I would love this as well!

@Jonathanliu92251

This comment was marked as off-topic.

@Cyclenerd
Copy link
Owner

Spot VMs are now supported: https://github.com/Cyclenerd/google-cloud-pricing-cost-calculator/tree/master/usage#resources

Can you map the flexible CUDs with the discount?

@Cyclenerd Cyclenerd self-assigned this May 8, 2023
@Jonathanliu92251

This comment was marked as off-topic.

@Jonathanliu92251
Copy link
Author

The Flexible CUDs, I've not found the SKU mapping, but it seems like this:

  • A 28% discount over your committed hourly spend amount for a 1-year commitment
  • A 46% discount over your committed hourly spend amount for a 3-year commitment

Source: https://cloud.google.com/compute/docs/instances/committed-use-discounts-overview#spend_based

@Cyclenerd
Copy link
Owner

If it is simply a discount add it as a discount in the YAML.

Repository owner deleted a comment from Jonathanliu92251 Nov 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants