ion.blogspot.fr/2015/03/nova-quota-usage-synchronization.html
and code at https://github.com/cernops/nova-quota-sync
Tim
-Original Message-
From: Mike Dorman [mailto:mdor...@godaddy.com]
Sent: 20 March 2015 18:01
To: OpenStack Operators
Subject: Re: [Openstack-operators] max_age and until_refresh for fixin
015 18:01
> To: OpenStack Operators
> Subject: Re: [Openstack-operators] max_age and until_refresh for fixing Nova
> quotas
>
> Hey Sam,
>
> When you say it occurs every 10 minutes, what exactly do you mean? The quota
> refresh? Or a quota getting out of sync?
>
>
;>> 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’.
> >>>
> >>> Mike
> >>>
> >>>
> >&
rates
>>> 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’.
>>>
>>> Mike
>>>
>>>
>>>
>>> On
gt;>> doing a single refresh is probably comparable to doing a Œnova list¹.
>>>
>>> Mike
>>>
>>>
>>>
>>> On 3/14/15, 2:27 PM, "Tim Bell" wrote:
>>>
>>>> Interesting... what are the defaults ?
>>>>
Bell" 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
hat¹s in the instances or reservations table. I imagine the load
> >>for
> >> doing a single refresh is probably comparable to doing a Œnova list¹.
> >>
> >> Mike
> >>
> >>
> >>
> >> On 3/14/15, 2:27 PM, "Tim Bell&qu
d, getting synced within a day would seem
>>> reasonable. Is the default no max age ?
>>>
>>> Tim
>>>
>>>> -Original Message-
>>>> From: Jesse Keating [mailto:j...@bluebox.net]
>>>> Sent: 14 March 2015 16:59
&
t; From: Jesse Keating [mailto:j...@bluebox.net]
>>> Sent: 14 March 2015 16:59
>>> To: openstack-operators@lists.openstack.org
>>> Subject: Re: [Openstack-operators] max_age and until_refresh for fixing
>>> Nova
>>> quotas
>>>
>>> On 3/14/1
suming 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:j...@bluebox.net]
> >> Sent: 14 March 2015 16:59
> >> To: openst
>> From: Jesse Keating [mailto:j...@bluebox.net]
>> Sent: 14 March 2015 16:59
>> To: openstack-operators@lists.openstack.org
>> Subject: Re: [Openstack-operators] max_age and until_refresh for fixing
>>Nova
>> quotas
>>
>> On 3/14/15 8:11 AM, Mike Dorm
ck-operators@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.
> >
>
> Thank
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@li
For those not following the discussion on
https://review.openstack.org/#/c/161782/ around fixing Nova quota usages, there
are a couple config options that can help: max_age and until_refresh.
I had not known about these before. I deployed them out this week and they
seem to do a pretty good j
14 matches
Mail list logo
