Proposal for Quota Reporting and Management #12
Conversation
Sunandadadi
changed the title
Sunandadadi
force-pushed
the
quota_proposal
branch
from
9fcceab to
77a2d1d
Compare
Sunandadadi
changed the title
Sunandadadi
force-pushed
the
quota_proposal
branch
3 times, most recently
from
3d249e0 to
a3e6ee7
Compare
| This is depicted below: | ||
|  | ||
|
|
||
| ### Risks and Mitigations |
There was a problem hiding this comment.
A few caveats with doing the calculations on push vs a background worker: existing images will not have any usage data. This means that a backfill for all existing repositories will be required before the feature is enabled. This also means that this calculation becomes part of a push's critical path, otherwise the usage data could possibly drift.
There was a problem hiding this comment.
We should try and define how to reconcile different states of a Quay installation into one where quota reporting can be enabled. For example, what happens if a user enables quota reporting, disables it and reanables it, etc, ...
There was a problem hiding this comment.
The data required exists on all old data already. This new path does not become critical as the data comes from elsewhere the reporting can fall back upon slower methods of reporting if it becomes necessary
There was a problem hiding this comment.
Regarding enabling and disabling Quota: I am thinking in the terms of having a button on an organization say Sync Quota when Quota is enabled. When clicked, we calculate the Quota usage for the org and show. If user disables, Quota is not calculated after disabling, but when re-enabled again, they have the option to sync it back.
But, if hard limits are configured and user disables Quota, I am assuming that the limits should not hold true and the user can push images.
Sunandadadi
force-pushed
the
quota_proposal
branch
from
a3e6ee7 to
7cee773
Compare
No description provided.