<div dir="ltr">I completely agree with you - Sean and Joe.<div><br></div><div>Since the argument was brought up I just wanted to point out that this "quota service" thing is a bit of a unicorn at the moment, and it should not distract from fixing and improving quota maangement & enforcement logic in the various openstack projects.</div><div><br></div><div>I wan't be able to introduce hierarchical quotas in neutron by the end of Kilo, but I'll keep it on the roadmap for Liberty.</div><div><br></div><div>Salvatore<br><div class="gmail_extra"><br><div class="gmail_quote">On 12 March 2015 at 11:59, Sean Dague <span dir="ltr"><<a href="mailto:sean@dague.net" target="_blank">sean@dague.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 03/11/2015 08:31 PM, Joe Gordon wrote:<br>
><br>
><br>
> On Wed, Mar 11, 2015 at 4:07 PM, Ihar Hrachyshka <<a href="mailto:ihrachys@redhat.com">ihrachys@redhat.com</a><br>
</span><div><div class="h5">> <mailto:<a href="mailto:ihrachys@redhat.com">ihrachys@redhat.com</a>>> wrote:<br>
><br>
> -----BEGIN PGP SIGNED MESSAGE-----<br>
> Hash: SHA1<br>
><br>
> On 03/11/2015 07:48 PM, Joe Gordon wrote:<br>
> > Out of sync Quotas ------------------<br>
> ><br>
> > <a href="https://etherpad.openstack.org/p/PHL-ops-nova-feedback" target="_blank">https://etherpad.openstack.org/p/PHL-ops-nova-feedback</a> L63<br>
> ><br>
> > The quotas code is quite racey (this is kind of a known if you look<br>
> > at the bug tracker). It was actually marked as a top soft spot<br>
> > during last fall's bug triage -<br>
> > <a href="http://lists.openstack.org/pipermail/openstack-dev/2014-September/046517.html" target="_blank">http://lists.openstack.org/pipermail/openstack-dev/2014-September/046517.html</a><br>
> ><br>
> > There is an operator proposed spec for an approach here -<br>
> > <a href="https://review.openstack.org/#/c/161782/" target="_blank">https://review.openstack.org/#/c/161782/</a><br>
> ><br>
> > Action: we should make a solution here a top priority for enhanced<br>
> > testing and fixing in Liberty. Addressing this would remove a lot<br>
> > of pain from ops.<br>
> ><br>
> ><br>
> > To help us better track quota bugs I created a quotas tag:<br>
> ><br>
> > <a href="https://bugs.launchpad.net/nova/+bugs?field.tag=quotas" target="_blank">https://bugs.launchpad.net/nova/+bugs?field.tag=quotas</a><br>
> ><br>
> > Next step is re-triage those bugs: mark fixed bugs as fixed,<br>
> > deduplicate bugs etc.<br>
><br>
> (Being quite far from nova code, so ignore if not applicable)<br>
><br>
> I would like to note that other services experience races in quota<br>
> management too. Neutron has a spec approved to land in Kilo-3 that is<br>
> designed to introduce a new quota enforcement mechanism that is<br>
> expected to avoid (some of those) races:<br>
><br>
> <a href="https://github.com/openstack/neutron-specs/blob/master/specs/kilo/better-quotas.rst" target="_blank">https://github.com/openstack/neutron-specs/blob/master/specs/kilo/better-quotas.rst</a><br>
><br>
> I thought you may be interested in looking into it to apply similar<br>
> ideas to nova.<br>
><br>
><br>
> Working on a library for this hasn't been ruled out yet. But right now I<br>
> am simply trying to figure out how to reproduce the issue, and nothing else.<br>
<br>
</div></div>Right, I think assuming an architecture change will magically fix this<br>
without scenarios that expose the existing bugs seems overly optimistic.<br>
<br>
I think there is a short / medium term test / reproduce question here,<br>
then a longer term question about different architecture.<br>
<span class="im HOEnZb"><br>
-Sean<br>
<br>
--<br>
Sean Dague<br>
<a href="http://dague.net" target="_blank">http://dague.net</a><br>
<br>
</span><div class="HOEnZb"><div class="h5">__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</div></div></blockquote></div><br></div></div></div>