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

Define Monthly process to Calculate cloud costs for dedicated clusters on Google Cloud #498

Closed
Tracked by #519 ...
choldgraf opened this issue Aug 29, 2022 · 1 comment
Assignees

Comments

@choldgraf
Copy link
Member

choldgraf commented Aug 29, 2022

Context

For some communities, we pay the cloud costs directly, with the intent of passing through those costs to the communities we work with each month.

Currently, we do not have a defined way to incorporate cloud costs into our monthly invoicing process. This makes it difficult for @colliand to generate the necessary information that Page @ CSS needs to send the right invoice.

As a start, we should define a manual process by which we should generate costs for monthly invoices. I recently figured out how to define the cloud costs incurred by each cluster in google cloud. Here's a quick rundown for reference by the @2i2c-org/partnerships-and-community-guidance team.

On Google Cloud

For communities with dedicated clusters

Here's a way to get monthly costs, broken down by the project. Assuming that projects are unique for each community, we can easily determine how much cloud spend they have.

Go to the billing page for Google cloud (https://console.cloud.google.com/billing). This will least all of our billing accounts. Each one is attached to a credit card or to an allotment of credits.

The two-eye-two-see billing account is the one we use for communities with dedicated clusters where we pay the cloud bill. Select it like so:

image

(note that there's also an account called two-eye-two-see, which is a dedicated billing account for the m2lines project that we need to migrate over, see 2i2c-org/infrastructure#1651)

you'll be taken to a page that describes the costs / billing for this billing account, it looks like this:

image

For a quick overview of the cloud costs being drawn for each of our projects, click on Reports. Below is an example showing a few projects, the two most important are:

  • (in blue) The two-eye-two-see project is the collection of hubs that are running on our shared 2i2c cluster. Calculating billing for them is a bit more complicated.
  • (in red) The AWI cluster project.

chrome_iJPCR0ZZhG

To calculate the exact costs, go to Cost Breakdown. This will give us a more detailed breakdown of costs by project. You can choose an invoice month and download a CSV of the billing data broken down by project:

image

@choldgraf choldgraf changed the title Incorporate cloud costs into our monthly invoicing process Incorporate cloud costs into our monthly invoicing process for Google Cloud Aug 29, 2022
@choldgraf choldgraf changed the title Incorporate cloud costs into our monthly invoicing process for Google Cloud Calculate cloud costs for dedicated clusters on Google Cloud Aug 29, 2022
@damianavila damianavila moved this to Needs Shaping / Refinement in DEPRECATED Engineering and Product Backlog Sep 13, 2022
@pnasrat pnasrat self-assigned this Apr 7, 2023
@pnasrat pnasrat changed the title Calculate cloud costs for dedicated clusters on Google Cloud Define Monthly process to Calculate cloud costs for dedicated clusters on Google Cloud Apr 10, 2023
@pnasrat
Copy link
Contributor

pnasrat commented Jul 19, 2023

The billing automation written by @yuvipanda and built upon in the billing deployer module handles dedicated and shared GCP billing

https://github.com/2i2c-org/infrastructure/tree/master/deployer/billing

@pnasrat pnasrat closed this as completed Jul 19, 2023
@github-project-automation github-project-automation bot moved this from Needs Shaping / Refinement to Complete in DEPRECATED Engineering and Product Backlog Jul 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
Development

No branches or pull requests

2 participants