Skip to content
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

Based on the measured data set the user/namespace/project limits #2052

Open
Tracked by #2108
lbarcziova opened this issue May 11, 2023 · 0 comments
Open
Tracked by #2108

Based on the measured data set the user/namespace/project limits #2052

lbarcziova opened this issue May 11, 2023 · 0 comments
Labels
area/general Related to whole service, not a specific part/integration. complexity/single-task Regular task, should be done within days. gain/high This brings a lot of value to (not strictly a lot of) users. impact/high This issue impacts multiple/lot of users. kind/internal Doesn't affect users directly, may be e.g. infrastructure, DB related.

Comments

@lbarcziova
Copy link
Member

lbarcziova commented May 11, 2023

To avoid overusing Packit, we will implement a system of limits. Here are the rules:

  • Let's start with the hourly base for the limits.
  • Specific limit numbers should be determined from real usage.
  • Be prepared for manual enhancements of limits (e.g. a known important project with high traffic that uses the resources legitimately).
  • Be prepared for integrating with Implement blocklisting mechanism #1964 (later)
  • If the limit is reached, no action is done by Packit.
  • Can we inform user about this situation so it's realised by a legitimate user? (One-time action, two levels of limits,...)

Followup of #1990

@lbarcziova lbarcziova changed the title (follow-up) Based on the measured data set the limits/quota Based on the measured data set the user/namespace/project limits May 11, 2023
@csomh csomh moved this from new to backlog in Packit Kanban Board May 15, 2023
@csomh csomh added impact/high This issue impacts multiple/lot of users. area/general Related to whole service, not a specific part/integration. complexity/single-task Regular task, should be done within days. gain/high This brings a lot of value to (not strictly a lot of) users. kind/internal Doesn't affect users directly, may be e.g. infrastructure, DB related. labels May 15, 2023
@lbarcziova lbarcziova mentioned this issue Jun 29, 2023
2 tasks
@lachmanfrantisek lachmanfrantisek moved this from backlog to priority-backlog in Packit Kanban Board Jan 25, 2024
@lachmanfrantisek lachmanfrantisek moved this from priority-backlog to backlog in Packit Kanban Board Feb 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/general Related to whole service, not a specific part/integration. complexity/single-task Regular task, should be done within days. gain/high This brings a lot of value to (not strictly a lot of) users. impact/high This issue impacts multiple/lot of users. kind/internal Doesn't affect users directly, may be e.g. infrastructure, DB related.
Projects
Status: backlog
Development

No branches or pull requests

2 participants