Status of storage quota #876
Labels
No labels
ci
ci
license
ci
private
meta
request
local-user
request
username
resources
limit
resources
private
resources
storage
stickers
No milestone
No assignees
5 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Codeberg-e.V./requests#876
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Hey everyone,
to avoid confusion, I'm trying to use this as the canonical place for the current status of our storage limits roll-out on Codeberg. I chose this place, because this issue tracker is probably the place where most people will ask about it, and where we should generally send users to.
Please be patient with us. The roll-out is happening very slowly, and coordinated with technical changes that simplify the management, both for users and admins.
For discussion and management of the technical aspects, there is another issue at Codeberg-Infrastructure/meta#38. We aim to keep this issue low-noise, so that you can subscribe for announcements if you want.
Status
Expected next steps (can be subject to change)
@fnetX
Is the "double counting" bug fixed?
We should enable this very strictly on codeberg-test.org so we can see how it behaves.
We have a patch at
Codeberg-Infrastructure/forgejo@aa93903454that might be slightly wrong. The original issue with Forgejo has not seen much progress forgejo/forgejo#7860We just posted an announcement in the changelog.
tl;dr: The storage granted during the grace period was now reduced from "unlimited" to actual limits. We checked the storage usage of legitimate projects and chose a limit that should still work for everyone, but still limits the impact of storage abuse.
If you use very large amounts of storage (see definition in the changelog linked above), please proceed with requesting an exception now.
Hi, I hope this is the right place to ask about this. If not, I apologize - please refer me to where I should ask.
Anyways, I'm confused about something with this change. The storage quota page lists two quotas: One called "Default (Snowflake)" (750 MiB of Git repos/1.5 GiB of other assets), and another called "Grace period" (85 GiB of Git repos/200 GiB of other assets). What is the "Grace period" quota about?
(To be clear, I'm nowhere near these limits (I haven't even cracked 1 MiB in any of the quotas), and it's likely to be months or years before it's an issue for me, but I'm still curious.)
The reason I ask, is because I could reasonably read it two different ways:
How should I be reading the "Grace period" quota?
The default quota rules is what we intend to enforce, but to not yet enforce them and still show them in the quota overview we have the "Grace period" quota rules. It's also functions to prevent storage abuse for the time being as being a upper limit.
But doesn't that contradict the original announcement? It said there that you should only submit a storage expansion request if you're over the Grace Limit. Should you also submit a storage expansion request if you're over the Snowflake Limit?
Original accouncments: Codeberg/changelog#2 (comment)
Snowflake: 1.5 GiB / 750 MiB
Grace: 200 GiB / 85 GiB
Request if above: 100 GiB / 10 GiB
When exactly should I submit the request for additional storage? I'm a bit confused about that.
@mark22k, sorry but I'm not exactly sure that we're reading the same comment. It doesn't mention that you should request a exemption if you're over the 'Grace period' rule. I will verbatim copy when you should make a request exemption right now: