forgejo/modules/structs
Gergely Nagy e1fe3bbdc0
feat(quota): Humble beginnings of a quota engine
This is an implementation of a quota engine, and the API routes to
manage its settings. This does *not* contain any enforcement code: this
is just the bedrock, the engine itself.

The goal of the engine is to be flexible and future proof: to be nimble
enough to build on it further, without having to rewrite large parts of
it.

It might feel a little more complicated than necessary, because the goal
was to be able to support scenarios only very few Forgejo instances
need, scenarios the vast majority of mostly smaller instances simply do
not care about. The goal is to support both big and small, and for that,
we need a solid, flexible foundation.

There are thee big parts to the engine: counting quota use, setting
limits, and evaluating whether the usage is within the limits. Sounds
simple on paper, less so in practice!

Quota counting
==============

Quota is counted based on repo ownership, whenever possible, because
repo owners are in ultimate control over the resources they use: they
can delete repos, attachments, everything, even if they don't *own*
those themselves. They can clean up, and will always have the permission
and access required to do so. Would we count quota based on the owning
user, that could lead to situations where a user is unable to free up
space, because they uploaded a big attachment to a repo that has been
taken private since. It's both more fair, and much safer to count quota
against repo owners.

This means that if user A uploads an attachment to an issue opened
against organization O, that will count towards the quota of
organization O, rather than user A.

One's quota usage stats can be queried using the `/user/quota` API
endpoint. To figure out what's eating into it, the
`/user/repos?order_by=size`, `/user/quota/attachments`,
`/user/quota/artifacts`, and `/user/quota/packages` endpoints should be
consulted. There's also `/user/quota/check?subject=<...>` to check
whether the signed-in user is within a particular quota limit.

Quotas are counted based on sizes stored in the database.

Setting quota limits
====================

There are different "subjects" one can limit usage for. At this time,
only size-based limits are implemented, which are:

- `size:all`: As the name would imply, the total size of everything
  Forgejo tracks.
- `size:repos:all`: The total size of all repositories (not including
  LFS).
- `size:repos:public`: The total size of all public repositories (not
  including LFS).
- `size:repos:private`: The total size of all private repositories (not
  including LFS).
- `size:git:all`: The total size of all git data (including all
  repositories, and LFS).
- `size:git:lfs`: The size of all git LFS data (either in private or
  public repos).
- `size:assets:all`: The size of all assets tracked by Forgejo.
- `size:assets:attachments:all`: The size of all kinds of attachments
  tracked by Forgejo.
- `size:assets:attachments:issues`: Size of all attachments attached to
  issues, including issue comments.
- `size:assets:attachments:releases`: Size of all attachments attached
  to releases. This does *not* include automatically generated archives.
- `size:assets:artifacts`: Size of all Action artifacts.
- `size:assets:packages:all`: Size of all Packages.
- `size:wiki`: Wiki size

Wiki size is currently not tracked, and the engine will always deem it
within quota.

These subjects are built into Rules, which set a limit on *all* subjects
within a rule. Thus, we can create a rule that says: "1Gb limit on all
release assets, all packages, and git LFS, combined". For a rule to
stand, the total sum of all subjects must be below the rule's limit.

Rules are in turn collected into groups. A group is just a name, and a
list of rules. For a group to stand, all of its rules must stand. Thus,
if we have a group with two rules, one that sets a combined 1Gb limit on
release assets, all packages, and git LFS, and another rule that sets a
256Mb limit on packages, if the user has 512Mb of packages, the group
will not stand, because the second rule deems it over quota. Similarly,
if the user has only 128Mb of packages, but 900Mb of release assets, the
group will not stand, because the combined size of packages and release
assets is over the 1Gb limit of the first rule.

Groups themselves are collected into Group Lists. A group list stands
when *any* of the groups within stand. This allows an administrator to
set conservative defaults, but then place select users into additional
groups that increase some aspect of their limits.

To top it off, it is possible to set the default quota groups a user
belongs to in `app.ini`. If there's no explicit assignment, the engine
will use the default groups. This makes it possible to avoid having to
assign each and every user a list of quota groups, and only those need
to be explicitly assigned who need a different set of groups than the
defaults.

If a user has any quota groups assigned to them, the default list will
not be considered for them.

The management APIs
===================

This commit contains the engine itself, its unit tests, and the quota
management APIs. It does not contain any enforcement.

The APIs are documented in-code, and in the swagger docs, and the
integration tests can serve as an example on how to use them.

Signed-off-by: Gergely Nagy <forgejo@gergo.csillger.hu>
2024-08-02 11:10:34 +02:00
..
activity.go Document possible action types for the user activity feed API () 2024-06-09 11:13:39 +02:00
activitypub.go
admin_user.go
attachment.go Implement external assets 2024-07-29 20:35:55 +02:00
commit_status.go
commit_status_test.go
cron.go
doc.go
fork.go
git_blob.go
git_hook.go
hook.go Add support for workflow_dispatch () 2024-06-28 05:17:11 +00:00
issue.go Make gitea webhooks openproject compatible (gitea#28435) 2024-06-05 15:58:51 +02:00
issue_comment.go
issue_label.go Support using label names when changing issue labels () 2024-05-19 13:12:35 +02:00
issue_milestone.go
issue_reaction.go
issue_stopwatch.go
issue_test.go Add testifylint to lint checks () 2024-07-30 19:41:10 +00:00
issue_tracked_time.go
lfs_lock.go
mirror.go
miscellaneous.go
moderation.go
nodeinfo.go
notifications.go
org.go
org_member.go
org_team.go Increase max length of org team names from 30 to 255 characters () 2024-06-23 12:21:38 +02:00
package.go
pull.go Make gitea webhooks openproject compatible (gitea#28435) 2024-06-05 15:58:51 +02:00
pull_review.go
quota.go feat(quota): Humble beginnings of a quota engine 2024-08-02 11:10:34 +02:00
release.go
repo.go Add topics for repository API () 2024-06-02 16:26:54 +02:00
repo_actions.go
repo_branch.go
repo_collaborator.go
repo_commit.go
repo_compare.go
repo_file.go
repo_flags.go
repo_key.go
repo_note.go
repo_refs.go
repo_tag.go Add tag protection via rest api () 2024-06-16 13:42:59 +02:00
repo_topic.go
repo_tree.go
repo_watch.go
repo_wiki.go
secret.go
settings.go
status.go
task.go
user.go Make gitea webhooks openproject compatible (gitea#28435) 2024-06-05 15:58:51 +02:00
user_app.go
user_email.go
user_gpgkey.go
user_key.go
variable.go
visible_type.go
workflow.go Add support for workflow_dispatch () 2024-06-28 05:17:11 +00:00