Sub-issues
#6861 - Group costs: Update groups-exporter to handle one-to-many user <-> group relationships
#6856 - Group costs: Cost backend can understand user group memberships
#6857 - Group costs: Cost logic for group rollups
#6859 - Group costs: Create Group cloud costs Grafana dashboard
#7016 - Group costs: Rollout prototype to test hubs
#6858 - Group costs: Write tests and document
#7097 - Group costs: Validate home storage metrics
#6860 - Group costs: Rollout and blog post
Participate in the issue: github
Context¶
Aggregate per-user cloud costs by JupyterHub group so that hub administrators can transparently see cost attribution by organizational team/department/etc. This builds on per-user cost reporting (#6315) and provides cost rollups where users in multiple groups may be double-counted.
Once 2i2c
Proposal¶
The main obstacle is to decide how to account for costs when a user is a member of more than one group. We therefore provide cost rollups, so that users who are members of multiple groups may be double-counted. A hub admin can then transparently see that the summed costs across all groups may exceed the total cost. If summed costs across all groups == total cost is desired, then it’s up to the hub admin to manage users and groups to preserve a 1:1 relationship.
Status: P&S Initiatives in flight
Back to: All Initiatives