Unsolved
This post is more than 5 years old
1 Message
0
1072
Question about Atmos Storage Quotas
Hello,
I'm new to Atmos but we have installed the latest version (2.1). I'm trying to figure out 2 things:
1) How storage quotas work and are set
2) How to manage storage quotas via the Atmos Management API
There is some detail on storage quotas in the Admin guide starting at pg109 but it's not clear about how they are set nor the purpose of them as they don't appear to automatically limit a subtenants usage. Based on what the admin guide states I need to deploy text files that limit a subtenant's write access once their quota has been exceeded - I guess I don't understand why write limitations wouldn't kick in automatically if a storage quota is set.
Finally, there's nothing in the Management API guide about how to set quotas via the REST mgmt API. Any insight into this feature is much appreciated, thanks!
-Dave
Anonymous
5 Practitioner
5 Practitioner
•
274.2K Posts
0
May 7th, 2013 00:00
I got this response from engineering. I haven't seen user quota allocation in atmos. Only option to measure user utilization is Metering Report tool to generate the user capacity utilization and than implement overquota on user subtenants.
Basically, the feature is not a true quota enforced by Atmos. The customer is responsible for querying the metering APIs and determining which accounts have gone over quota. They then generate a file named overquota.txt and put it into
/etc/maui on each cdp ws node. This makes that subtenant and/or uid only allowed to read or delete data until the customer's script runs again and removes the restriction.
Regards,
Chilla Murthy.