Open Stack

On a related note, I am trying to come up with different ways to reproduce
the quota bugs (as tracked in https://bugs.launchpad.net/nova/+bug/1284424)
and so far I have found one way, but I bet there are many more. So far I
have only reproduced https://bugs.launchpad.net/nova/+bug/1296414, which
causes quotas to not be decremented when a delete is completed on a
nova-compute startup.   When nova-compute starts up, it looks for
unfinished actions to resume, and it doesn't handle the quotas if the
action is a delete instance.  The good news is there is a patch up for
review that should fix this issue, and it should hopefully land in Kilo.

So if anyone knows of any other ways to trigger this type of bug,
information would be appreciated.

On Sat, Mar 14, 2015 at 8:53 PM, Mike Dorman <mdorman at godaddy.com> wrote:

> Yeah the default is just ‘0’ for both, which disables the refresh.
>
>
>
> The one downside is that it may not be 100% transparent to the user.  If
> the quota is already (incorrectly) too high, and exceeding the quota
> limit, the reservation that triggers the refresh will still fail.  I.e.
> the reservation is attempted based on the quota usage values _before_ the
> refresh.  But then after that the quota should be fixed and it will work
> again on the next reservation.
>
> But my thinking is that most quota issues happen slowly over time.  If we
> are correcting them often and automatically, they hopefully never get to
> the point where they’re bad enough to manifest reservation errors to the
> user.
>
> I don’t have any information re: db load.  I assume it regenerates based
> on what’s in the instances or reservations table.  I imagine the load for
> doing a single refresh is probably comparable to doing a ‘nova list’.
>
>
My understanding is rackspace has both of these enabled, and haven't seen
any significant impact on the DB.


> Mike
>
>
>
> On 3/14/15, 2:27 PM, "Tim Bell" <Tim.Bell at cern.ch> wrote:
>
> >Interesting... what are the defaults ?
> >
> >Assuming no massive DB load, getting synced within a day would seem
> >reasonable. Is the default no max age ?
> >
> >Tim
> >
> >> -----Original Message-----
> >> From: Jesse Keating [mailto:jlk at bluebox.net]
> >> Sent: 14 March 2015 16:59
> >> To: openstack-operators at lists.openstack.org
> >> Subject: Re: [Openstack-operators] max_age and until_refresh for fixing
> >>Nova
> >> quotas
> >>
> >> On 3/14/15 8:11 AM, Mike Dorman wrote:
> >> > I did short write-up here http://t.co/Q5X1hTgJG1 if you are
> interested
> >> > in the details.
> >> >
> >>
> >> Thanks for sharing Matt! That's an excellent write up.
> >>
> >> --
> >> -jlk
> >>
> >> _______________________________________________
> >> OpenStack-operators mailing list
> >> OpenStack-operators at lists.openstack.org
> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
> >
> >_______________________________________________
> >OpenStack-operators mailing list
> >OpenStack-operators at lists.openstack.org
> >http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20150315/00358afb/attachment.html>