Open Stack

As an Op, I've seen quota's in the db get out of sync all the time.... I'm sure some of my clouds right now have some stuff out of sync :/

With my dev hat on:
The code is really hard to get right.

There are also a lot of places quota's are missing. quota's per host aggregate, quota's for floating ips per external network.

Also hierarchical quota's are going to be important and that will touch a million projects too.

Then there's lots of projects that don't implement but the most basic of quota's.

Really, centralizing it will be a lot of work initially, but long term, I think will pay off in that there will be only one place to fix bugs and add important features. It will allow each project to easily add quota's to the places they need to be in, since they won't have to write a whole quota system themselves.

With an op hat on again, putting them all in one place will also make it easier to administer. "floating ip's on this cloud are ... neutron, so I need to use the neutron command to set the quota for that" can be a thing of the past.

Thanks,
Kevin

________________________________________
From: Joshua Harlow [harlowja at fastmail.com]
Sent: Wednesday, March 16, 2016 9:58 AM
To: openstack-dev at lists.openstack.org
Subject: Re: [openstack-dev] [cross-project] [all] Quotas -- service vs. library

On 03/16/2016 05:22 AM, Julien Danjou wrote:
> On Wed, Mar 16 2016, Attila Fazekas wrote:
>
>> The quota usage handling MUST happen in the same DB transaction as the
>> resource record (volume, server..) create/update/delete  .
>
> […]
>
>> We have a transaction capable DB, to help us,
>> not using it would be lame.
>
> Amen to that.

Double amen!

>
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>

__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev