[openstack-dev] Nova quota statistics counting issue
tdurakov at mirantis.com
Thu Apr 14 12:08:45 UTC 2016
I think it would be ok to store persistently quota details on compute side,
as was discussed during mitaka mid-cycle for migrations. So if
compute service fails we could restore state and update quota after compute
 - https://etherpad.openstack.org/p/mitaka-nova-priorities-tracking
 - https://review.openstack.org/#/c/291161/5/nova/compute/background.py
On Wed, Apr 13, 2016 at 7:27 PM, Dmitry Stepanenko <dstepanenko at mirantis.com
> Hi Team,
> I worked on nova quota statistics issue (
> https://bugs.launchpad.net/nova/+bug/1284424) happenning when nova-*
> processes are restarted during removing instances and was able to reproduce
> it. For repro I used devstack and started nova-api and nova-compute in
> separate screen windows. For killing them I used ctrl+c. As I found this
> issue happened if nova-* processes are killed after instance was deleted
> but right before quota commit procedure finishes.
> We discussed these results with Markus Zoeller and decided that even
> though killing nova processes is a bit exotic event, this still should be
> fixed because quotas counting affects billing and very important for us.
> So, we need to introduce some mechanism that will prevent us from reaching
> inconsistent states in terms of quotas. In other words, this mechanism
> should work in such a way that both instance create/remove operation and
> quota usage recount operation happened or not happened together.
> Any ideas how to do that properly?
> Kind regards,
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev