search

2i2c-org / infrastructure

Infrastructure for configuring and deploying our community JupyterHubs.
https://infrastructure.2i2c.org
BSD 3-Clause "New" or "Revised" License
105 stars 64 forks source link

Q2 billing data collection - shared clusters (Deadline July 9th) #4287

Closed consideRatio closed 4 months ago

consideRatio commented 4 months ago

Definition of done

The shared clusters are 2i2c and 2i2c-aws-us, and the Q2 months are April, May, June.

consideRatio commented 4 months ago

@yuvipanda proposed this is worked by @sgibson91 and me during the upcoming sprint starting June 27 -- to be decided during iteration planning.

sgibson91 commented 4 months ago

The quality of the video linked in the instructions is quite poor, so I couldn't see which saved billing reports in AWS console were being clicked. I had trouble finding it because the video doesn't show which AWS account you are signed into when you launch that page (because you were already authenticated) - I realise now it's probably the two-eye-two-see account, but my instinct was first to go for 2i2c-sandbox as I know that's a centralised management account, but realised that is only relevant for dedicated clusters (i.e. collecting billing data from across different accounts).

I'm not blocked, this is just a note about where I had to "figure stuff out for myself" because the info wasn't provided in the guide.

sgibson91 commented 4 months ago

May 2024 for AWS and GCP is done. I shall do June on Tuesday 2nd July.

sgibson91 commented 4 months ago

It may also be nice to have a video showing the process of adding/removing a hub and how to calculate the month fraction if needed - I made a pass for some hubs that changed May -> June, but not sure if my guess was within the expected norms of these processes.