🤔 Problem

This is a followup of the Cumulative Resource Usage Limits pitch.

Now that we track the usage, we should enforce the limits.

🍴 Appetite

6 weeks

🎯 Solution

• Enforce the two limits we have created in the DB (See here)
• Show the remaining capacity in the ui
• Show when the weekly capacity limits reset - or indicate the period for which the remaining capacity is valid
• When the limits is reached, the UI should disable the launch button and show a message
• (potentially nice to have) Show the total usage from a specific running session
• The resource usage tracking can be disabled - we should handle this nicely.
• (potentially nice to have) Update the admin UI to allow setting the limits
• (potentially nice to have) Update the admin UI to show usage summary on resource pools and classes
• When the limit is reached we should we inform users how to contact the admins to request more?
• When the limit is reached and there are sessions still running we should immediately pause the session. We will need a background task that runs every x minutes in the backend to do this.
• How do we inform users of cases where we had to do things automatically (like pause a session) because they ran out of resource allocation.
• Handle capacity reservations