Create a process for tracking and invoicing cloud infrastructure costs #519
Open
2 of 6 tasks
Labels
Enhancement
An improvement to something or creating something new.
Finance
Accounting and financial information.
Partnerships
Creating and fostering new collaborations with external groups
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:
And send it to CSS to try out:
Updates and actions
We have an Engineering related companion issue at 2i2c-org/infrastructure#1853.
The text was updated successfully, but these errors were encountered: