<div dir="ltr">On a related note, I am trying to come up with different ways to reproduce the quota bugs (as tracked in <a href="https://bugs.launchpad.net/nova/+bug/1284424" target="_blank">https://bugs.launchpad.net/nova/+bug/1284424</a>) and so far I have found one way, but I bet there are many more. So far I have only reproduced <a href="https://bugs.launchpad.net/nova/+bug/1296414" target="_blank">https://bugs.launchpad.net/nova/+bug/1296414</a>, 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.<div><br></div><div>So if anyone knows of any other ways to trigger this type of bug, information would be appreciated. </div><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Mar 14, 2015 at 8:53 PM, Mike Dorman <span dir="ltr"><<a href="mailto:mdorman@godaddy.com" target="_blank">mdorman@godaddy.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Yeah the default is just ‘0’ for both, which disables the refresh.<br>
<br>
<br>
<br>
The one downside is that it may not be 100% transparent to the user. If<br>
the quota is already (incorrectly) too high, and exceeding the quota<br>
limit, the reservation that triggers the refresh will still fail. I.e.<br>
the reservation is attempted based on the quota usage values _before_ the<br>
refresh. But then after that the quota should be fixed and it will work<br>
again on the next reservation.<br>
<br>
But my thinking is that most quota issues happen slowly over time. If we<br>
are correcting them often and automatically, they hopefully never get to<br>
the point where they’re bad enough to manifest reservation errors to the<br>
user.<br>
<br>
I don’t have any information re: db load. I assume it regenerates based<br>
on what’s in the instances or reservations table. I imagine the load for<br>
doing a single refresh is probably comparable to doing a ‘nova list’.<br>
<span><font color="#888888"><br></font></span></blockquote><div><br></div><div>My understanding is rackspace has both of these enabled, and haven't seen any significant impact on the DB.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span><font color="#888888">
Mike<br>
</font></span><div><div><br>
<br>
<br>
On 3/14/15, 2:27 PM, "Tim Bell" <<a href="mailto:Tim.Bell@cern.ch" target="_blank">Tim.Bell@cern.ch</a>> wrote:<br>
<br>
>Interesting... what are the defaults ?<br>
><br>
>Assuming no massive DB load, getting synced within a day would seem<br>
>reasonable. Is the default no max age ?<br>
><br>
>Tim<br>
><br>
>> -----Original Message-----<br>
>> From: Jesse Keating [mailto:<a href="mailto:jlk@bluebox.net" target="_blank">jlk@bluebox.net</a>]<br>
>> Sent: 14 March 2015 16:59<br>
>> To: <a href="mailto:openstack-operators@lists.openstack.org" target="_blank">openstack-operators@lists.openstack.org</a><br>
>> Subject: Re: [Openstack-operators] max_age and until_refresh for fixing<br>
>>Nova<br>
>> quotas<br>
>><br>
>> On 3/14/15 8:11 AM, Mike Dorman wrote:<br>
>> > I did short write-up here <a href="http://t.co/Q5X1hTgJG1" target="_blank">http://t.co/Q5X1hTgJG1</a> if you are interested<br>
>> > in the details.<br>
>> ><br>
>><br>
>> Thanks for sharing Matt! That's an excellent write up.<br>
>><br>
>> --<br>
>> -jlk<br>
>><br>
>> _______________________________________________<br>
>> OpenStack-operators mailing list<br>
>> <a href="mailto:OpenStack-operators@lists.openstack.org" target="_blank">OpenStack-operators@lists.openstack.org</a><br>
>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><br>
><br>
>_______________________________________________<br>
>OpenStack-operators mailing list<br>
><a href="mailto:OpenStack-operators@lists.openstack.org" target="_blank">OpenStack-operators@lists.openstack.org</a><br>
><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><br>
_______________________________________________<br>
OpenStack-operators mailing list<br>
<a href="mailto:OpenStack-operators@lists.openstack.org" target="_blank">OpenStack-operators@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><br>
</div></div></blockquote></div><br></div></div>