Skip to content

Deploy usage in self-hosted #14129

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
easyCZ opened this issue Oct 24, 2022 · 5 comments
Closed

Deploy usage in self-hosted #14129

easyCZ opened this issue Oct 24, 2022 · 5 comments
Assignees
Labels
meta: stale This issue/PR is stale and will be closed soon team: webapp Issue belongs to the WebApp team

Comments

@easyCZ
Copy link
Member

easyCZ commented Oct 24, 2022

We need to deploy the usage component in self-hosted installations. This is needed to ensure that a GetBalance call is reachable in the latest self-hosted release.

@easyCZ easyCZ moved this from Scheduled to In Progress in 🍎 WebApp Team Oct 24, 2022
@easyCZ easyCZ self-assigned this Oct 24, 2022
@easyCZ
Copy link
Member Author

easyCZ commented Oct 24, 2022

Open questions:

  • What values do we set for creditsPerMinuteByWorkspaceClass in self-hosted?
  • How often do we run the Usage Controller schedule in self-hosted? - 15 minutes like SaaS seems appropriate.

This change will first need to move the usage component configuration out of the experimental config and into standard config. In this, we'll need to pick sensible values to avoid the need to configure it explicitly by self-hosted.

@easyCZ
Copy link
Member Author

easyCZ commented Oct 25, 2022

Pausing this work. For now, we'll only focus on not using the usage component in self-hosted. See more details.

@easyCZ easyCZ removed their assignment Oct 25, 2022
@easyCZ easyCZ moved this from In Progress to Scheduled in 🍎 WebApp Team Oct 25, 2022
@geropl geropl self-assigned this Oct 25, 2022
@geropl geropl moved this from Scheduled to In Progress in 🍎 WebApp Team Oct 25, 2022
@geropl
Copy link
Member

geropl commented Oct 26, 2022

It turns out we really need to deploy the usage service, soon. #14173 introduced a work around to unblock the release, but we should look into deploying usage next week, to make sure it's in for the next release.
Once that's in, we should revert 6da8a9f.

@geropl geropl moved this from In Progress to Scheduled in 🍎 WebApp Team Oct 26, 2022
@geropl geropl removed their assignment Oct 26, 2022
@easyCZ easyCZ moved this from Scheduled to In Progress in 🍎 WebApp Team Nov 14, 2022
@easyCZ easyCZ self-assigned this Nov 14, 2022
@easyCZ easyCZ moved this from In Progress to In Validation in 🍎 WebApp Team Nov 14, 2022
@easyCZ easyCZ moved this from In Validation to In Progress in 🍎 WebApp Team Nov 21, 2022
@easyCZ
Copy link
Member Author

easyCZ commented Nov 21, 2022

The change was reverted in #14751, will need to be re-added.

@stale
Copy link

stale bot commented Feb 20, 2023

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the meta: stale This issue/PR is stale and will be closed soon label Feb 20, 2023
@stale stale bot closed this as completed Mar 19, 2023
@github-project-automation github-project-automation bot moved this from In Progress to In Validation in 🍎 WebApp Team Mar 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
meta: stale This issue/PR is stale and will be closed soon team: webapp Issue belongs to the WebApp team
Projects
Status: In Validation
Development

No branches or pull requests

2 participants