Support for quotas

[MarekNieslanik]

Do you plan to add possibility to set / remove quotas into the HTTP API?
Equivalent for suq, sgq, lq, and cu.

[korydraughn]

Yes. We will get these added for the next release.

[korydraughn]

The primary challenge for this issue and similar ones (e.g. setting the delay server) is figuring out which endpoint these operations should live under.

suq is no longer supported in iRODS so we're only talking about sgq, lq, and cu.

sgq could live under the /users-groups endpoint. Where would the other commands live?

There's also the possibility of introducing a /quotas endpoint for this functionality. Or a /admin endpoint (not a fan of this).

[trel]

an endpoint for each noun (aka /quotas)... i don't hate it...

also consider that we want to eventually support logical quotas in addition to physical/resource quotas.

definitely not a fan either of a general /admin endpoint without significant convincing.

[korydraughn]

/quotas is the current winner when it comes to the design. The operations offered by this endpoint could be:

• set_group_quota
• list_quotas
• calculate_quotas

The only hesitancy around this is Logical Quotas. Absorbing the Logical Quotas plugin into the iRODS server is likely to influence the outcome of this issue.

We could keep the admin rules for logical quotas executable via the /rules endpoint. This direction will depend on how the plugin is absorbed into the server.

[korydraughn]

We've observed some issues with calculating quotas, so we're going to bump this until those are worked out.

The PR for quotas support will remain in draft until then. See #457 for the implementation.