[openstack-dev] OpenStack Object Storage Quota API

John Dickinson me at not.mn
Thu Mar 7 00:37:52 UTC 2013


Limited self-service quotas are already included on a container basis (https://github.com/openstack/swift/commit/24ef12027c7b6e1e2f55275bed18ceac725e27a5) and there is currently a patch under review to add quotas on an account level (https://github.com/openstack/swift/commit/24ef12027c7b6e1e2f55275bed18ceac725e27a5).

Both of these quota patches are based only on aggregate storage used and subject to eventual consistency constraints.

--John




On Mar 6, 2013, at 4:23 PM, Gabriel Hurley <Gabriel.Hurley at nebula.com> wrote:

> Given that:
> 
>    1. OpenStack's APIs are meant to serve both public and private cloud needs,
>    2. Per-tenant quotas are commonly requested/expected of Object Storage (as with the Compute and Volume services), and
>    3. OpenStack's APIs are meant to have at least a modest level of commonality/parity,
> 
> I propose that the OpenStack Object Storage API specification should include Quota management.
> 
> 
> A minimum quota spec would simply allow control for the total storage size (bytes), and could also include quotas for number of objects and/or number of containers. For parity with current behavior the default value could be "unlimited" (-1).
> 
> 
> What do people think? Should this be moved forward via blueprints, etc?
> 
> All the best,
> 
>    - Gabriel
> 
> 
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev




More information about the OpenStack-dev mailing list