Skip to content

Apply usage quotas#4150

Open
ciyer wants to merge 5 commits into
mainfrom
feat/usage-quotas
Open

Apply usage quotas#4150
ciyer wants to merge 5 commits into
mainfrom
feat/usage-quotas

Conversation

@ciyer
Copy link
Copy Markdown
Contributor

@ciyer ciyer commented Apr 23, 2026

Description

  • feat: present usage quota information at session launch time
  • feat: show usage quota information when viewing session launcher details
  • feat: show usage quota for running or paused sessions
  • feat: show usage quota during session start
  • feat: prevent resume if usage quota is used

Use the following deploy string when ready

/deploy renku-data-services=main #extra-values=dataService.dataTasks.enableResourceRequestTracking=true

Screenshots

image image image image

@ciyer ciyer requested a review from a team as a code owner April 23, 2026 12:46
@olevski
Copy link
Copy Markdown
Member

olevski commented Apr 27, 2026

@ciyer I hope you dont mind that I edited the description so that this is deployed for the demo tomorrow. I will check if it is in a state that is demoable. If not we can skip the demo.

@RenkuBot
Copy link
Copy Markdown
Contributor

You can access the deployment of this PR at https://renku-ci-ui-4150.dev.renku.ch

@ciyer ciyer force-pushed the feat/usage-quotas branch 3 times, most recently from 24d585f to 71d1664 Compare May 8, 2026 12:59
@ciyer ciyer force-pushed the feat/usage-quotas branch 4 times, most recently from bc86f9f to 2c417bc Compare May 12, 2026 09:49
ciyer added 5 commits May 12, 2026 12:02
* build: update computeResources api
* feat: present usage quota information at session launch time
* feat: show usage quota information when viewing session launcher details
* feat: show usage quota for running or paused sessions
* feat: show usage quota during session start
* feat: prevent resume if usage quota is used
@ciyer ciyer force-pushed the feat/usage-quotas branch from 2c417bc to 0b0637d Compare May 12, 2026 10:03
Copy link
Copy Markdown
Member

@lorenzo-cavazzi lorenzo-cavazzi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks very nice! 👏
Does this require tagging again data-services? I see it points to main.


I have a couple of minor comments; it's likely too late to change now and they can be something for the cooldown, but I wonder if they were discussed with the build group.

  • The "remaining quota" information shows up when starting the sessions. It might raise some questions, especially from users who have been using sessions for a while and now see that prominent message. Should we add a link to the documentation? Some like "Learn more about usage quota"?
  • A session reaching the quota won't immediately shut down. I'm not sure about the delay, but users might see the message for some time and be able to close it and keep working. Should we phrase it closer to "the session will be paused soon" so that people won't think it's potentially a stale message and realize it might (will?) go down soon? Image

@ciyer
Copy link
Copy Markdown
Contributor Author

ciyer commented May 12, 2026

This looks very nice! 👏 Does this require tagging again data-services? I see it points to main.

Probably. :)

I have a couple of minor comments; it's likely too late to change now and they can be something for the cooldown, but I wonder if they were discussed with the build group.

  • The "remaining quota" information shows up when starting the sessions. It might raise some questions, especially from users who have been using sessions for a while and now see that prominent message. Should we add a link to the documentation? Some like "Learn more about usage quota"?

There was a decision to introduce usage quota, but not yet enforce them. There is supposed to be some communication about this, but it probably would be nice to also include some links to documentation in the UI, as you suggest.

  • A session reaching the quota won't immediately shut down. I'm not sure about the delay, but users might see the message for some time and be able to close it and keep working. Should we phrase it closer to "the session will be paused soon" so that people won't think it's potentially a stale message and realize it might (will?) go down soon?

That message text is specified in the backend. It should be fixed there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants