Open Stack

I've just proposed a design summit session with the description below. I sincerely hope anyone interested in quotas will attend. Please have a look at the etherpad to see what's already been done.

"The quota situation is getting out of control. There are already a number of quota implementations for Swift. I expect that Glance will get its own implementation of quotas next followed closely by Quantum and probably Cinder. Each service will have its own implementation and different API to boot. This is definitely suboptimal.

We need centralized quotas, otherwise it will become an operations nightmare.

This session will be focused on how that goal can be achieved and who would be willing and able to contribute to it.

I've started an Etherpad at https://etherpad.openstack.org/HavanaCentralizedQuotas for this session and to track the existing efforts on quotas. Feel free to add any implementations I've missed.

To keep the session focused we won't be discussing Nova quotas. If we can nail down a way forward for centralized quotas, perhaps one day we can roll Nova quotas into it."

Regards,
Everett


On Mar 6, 2013, at 6:37 PM, John Dickinson wrote:

> 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
> 
> 
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev