User Quota #2423
Labels
No Label
0.2.0
0.3.0
0.4.0
0.5.0
0.5.1
0.6.0
0.6.1
0.7.0
0.8.0
0.9.0
1.0.0
1.1.0
1.10.0
1.10.1
1.10.2
1.10a2
1.11.0
1.12.0
1.12.1
1.13.0
1.14.0
1.15.0
1.15.1
1.2.0
1.3.0
1.4.1
1.5.0
1.6.0
1.6.1
1.7.0
1.7.1
1.7β
1.8.0
1.8.1
1.8.2
1.8.3
1.8β
1.9.0
1.9.0-s3branch
1.9.0a1
1.9.0a2
1.9.0b1
1.9.1
1.9.2
1.9.2a1
LeastAuthority.com automation
blocker
cannot reproduce
cloud-branch
code
code-dirnodes
code-encoding
code-frontend
code-frontend-cli
code-frontend-ftp-sftp
code-frontend-magic-folder
code-frontend-web
code-mutable
code-network
code-nodeadmin
code-peerselection
code-storage
contrib
critical
defect
dev-infrastructure
documentation
duplicate
enhancement
fixed
invalid
major
minor
n/a
normal
operational
packaging
somebody else's problem
supercritical
task
trivial
unknown
was already fixed
website
wontfix
worksforme
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Reference: tahoe-lafs/trac-2024-07-25#2423
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
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?
In certain networks can be usefull to not allow users upload, more files than the space that they're sharing.
Quota management will be handled by the StorageClient, which imposes the limits on what can be uploaded to the grid. When a file is to be uploaded, the StorageClient:
1- Checks that the storage server is running and writable
2- Calculates the space it is sharing in the associated storage server.
3- The size of leases it holds on files stored on grid (requires a catalog of uploaded files and lease expiration/renewal tracking).
4- Estimates the assigned space as 'Sharing space (available + stored shares)'
5- Checks that Used space (i.e. sum of leases) is smaller than 'Sharing space'.
6- Retrieve the grid's “X out K” parameters used in erasure encoding.
7- Verifies that predicted used space and reports an error if the available quota is exceeded.
Related to #1836 and #295. (Possibly could be considered a dupe)
This feature needs to fit into a bigger picture that considers how clients are identified on a grid, how their storage usage is tracked, and how limits on that usage might be determined and enforced.
As a stand-alone, it doesn't make sense. Also, whatever
StorageClient
was no longer seems to exist in the code base. It sounds like something that might exist in a client node but it doesn't make sense to enforce quotas in the client (since a client can then just choose not to enforce them).There are lots of other tickets and content in the docs and on the wiki (eg https://tahoe-lafs.org/trac/tahoe-lafs/wiki/NewAccountingDesign) about this kind of usage tracking. I'm going to close this in favor of all that.