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

Create a process for tracking and invoicing cloud infrastructure costs #519

Open
2 of 6 tasks
Tracked by #355 ...
choldgraf opened this issue Sep 16, 2022 · 3 comments
Open
2 of 6 tasks
Tracked by #355 ...
Assignees
Labels
Enhancement An improvement to something or creating something new. Finance Accounting and financial information. Partnerships Creating and fostering new collaborations with external groups

Comments

@choldgraf
Copy link
Member

choldgraf commented Sep 16, 2022

Context

There are several communities for which we are paying their cloud costs on their behalf. We are hand wavy about calculating cloud costs and do not have a system in place for rigorously tracking their cloud usage, conveying this information to CS&S, and invoicing them for it. This means that we are paying for cloud infrastructure without recovering the cost of doing so.

Proposal

We need to define a process for tracking and invoicing cloud infrastructure. This is going to require input from all of our teams, and I'll try to break this down by the issues that I think are team-specific. There are three things that we need to do:

Define how we calculate "usage" for a JupyterHub in order to calculate cloud costs. This is broken down by "shared clusters" and "dedicated clusters".

shared clusters

dedicated clusters will be much simpler

Then we must automate this process:

  • Build a script / tool that calculates this statistic for each hub on a cluster, and turns that into a $ amount
  • Figure out what kind of form CS&S wants the data in

And send it to CSS to try out:

  • Run this script, give CS&S the data, and see how it goes

Updates and actions

We have an Engineering related companion issue at 2i2c-org/infrastructure#1853.

@choldgraf choldgraf added Enhancement An improvement to something or creating something new. Partnerships Creating and fostering new collaborations with external groups Finance Accounting and financial information. labels Sep 16, 2022
@damianavila damianavila moved this to Needs Shaping / Refinement in DEPRECATED Engineering and Product Backlog Sep 20, 2022
@damianavila
Copy link
Contributor

This is super important (and why I prioritize it as critical), otherwise, we are effectively losing revenue that will impact our sustainability.

@choldgraf
Copy link
Member Author

Considering how important this one is, I think that we should find somebody that is responsible for championing this and make progress on it relatively quickly. @damianavila can you find somebody on engineering that can put some cycles into this? Or can you champion this and set a checkpoint time + goal to accomplish so that we can make progress?

@choldgraf
Copy link
Member Author

Update: James will spearhead this one

In a slack message, @jmunroe mentioned that he will spearhead this issue so that we can make progress. I've assigned him and added it to our backlog. @jmunroe maybe we should discuss this in our community content meeting tomorrow?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement An improvement to something or creating something new. Finance Accounting and financial information. Partnerships Creating and fostering new collaborations with external groups
Projects
Status: No status
Status: No status
Development

No branches or pull requests

3 participants