Roadmap #878

New issue

Closed

opened 2024-09-14 12:08:45 +00:00 by till · 1 comment

till commented

2024-09-14 12:08:45 +00:00

Hey,

sorry, if this is not the correct place to ask. I was wondering what the Roadmap for Garage looks like in terms of quota and also usage (stats) of accounts, buckets, etc.. In away if there's a doc/idea yet how to go about these.

I am mostly interested in these two things — as in setting a quota for a user account (key) and also how to determine how much storage, bandwidth etc. an account consumed.

Thank you!

Hey, sorry, if this is not the correct place to ask. I was wondering what the Roadmap for Garage looks like in terms of quota and also usage (stats) of accounts, buckets, etc.. In away if there's a doc/idea yet how to go about these. I am mostly interested in these two things — as in setting a quota for a user account (key) and also how to determine how much storage, bandwidth etc. an account consumed. Thank you!

lx commented

2024-09-14 16:04:33 +00:00

Owner

Hello, there are no plan to implement these features at the moment.

Setting a quota for a key -> this is hard to add in the current structure of the code. Also it is not clear how to measure storage used by a key when there are several access keys that have access to the same bucket(s).

Determine how much storage & bandwidth an account used -> this would add complexity to Garage as all API requests would need to cause the incrementing of a counter somewhere in the database. Garage tries to be minimalistic so we don't want to do work we can avoid. If we really wanted to add this, we would have to think about how to make it the less invasive possible so that it could be disabled completely and not impact the runtime performance for people who don't need it.

Hello, there are no plan to implement these features at the moment. *Setting a quota for a key* -> this is hard to add in the current structure of the code. Also it is not clear how to measure storage used by a key when there are several access keys that have access to the same bucket(s). *Determine how much storage & bandwidth an account used* -> this would add complexity to Garage as all API requests would need to cause the incrementing of a counter somewhere in the database. Garage tries to be minimalistic so we don't want to do work we can avoid. If we really wanted to add this, we would have to think about how to make it the less invasive possible so that it could be disabled completely and not impact the runtime performance for people who don't need it.

👍 1