I have been working in Nova Quotas for more than a year, and I also think that
Nova Quota sub-team is a good idea. Let us form the team and work together.
best
regards
sajeesh
________________________________
From: Vilobh Meshram [[email protected]]
Sent: 02 December 2015 01:15:31
To: OpenStack Development Mailing List (not for usage questions); OpenStack
Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [nova]New Quota Subteam on Nova
I am highly supportive for the idea of Nova Quota sub-team, for something as
complex as Quota, as it helps to move quickly on reviews and changes.
Agree with John, a test framework to test quotas will be helpful and can be one
of the first task the Nova Quota sub team can focus on as that will lay the
foundation for whether the bugs mentioned here http://bit.ly/1Pbr8YL are valid
or not.
Having worked in the area of Quotas for a while now by introducing features
like Cinder Nested Quota Driver [1] [2] I strongly feel that something like a
Nova Quota sub-team will definitely help. Mentioning about Cinder Quota driver
since it was accepted in Mitaka design summit that Nova Nested Quota Driver[3]
would like to pursue the route taken by Cinder. Since Nested quota is a one
part of Quota subsystem and working in small team helped to iterate quickly for
Nested Quota patches[4][5][6][7] so IMHO forming a Nova quota subteam will help.
Melanie,
If you can share the details of the bug that Joe mentioned, to reproduce quota
bugs locally, it would be helpful.
-Vilobh (irc: vilobhmm)
[1] Code : https://review.openstack.org/#/c/205369/
[2] Blueprint :
https://blueprints.launchpad.net/cinder/+spec/cinder-nested-quota-driver
[3] Nova Nested Quota Spec : https://review.openstack.org/#/c/209969/
[4] https://review.openstack.org/#/c/242568/
[5] https://review.openstack.org/#/c/242500/
[6] https://review.openstack.org/#/c/242514/
[7] https://review.openstack.org/#/c/242626/
On Mon, Nov 30, 2015 at 10:59 AM, melanie witt
<[email protected]<mailto:[email protected]>> wrote:
On Nov 26, 2015, at 9:36, John Garbutt
<[email protected]<mailto:[email protected]>> wrote:
> A suggestion in the past, that I like, is creating a nova functional
> test that stress tests the quota code.
>
> Hopefully that will be able to help reproduce the error.
> That should help prove if any proposed fix actually works.
+1, I think it's wise to get some data on the current state of quotas before
choosing a redesign. IIRC, Joe Gordon described a test scenario he used to use
to reproduce quota bugs locally, in one of the launchpad bugs. If we could
automate something like that, we could use it to demonstrate how quotas
currently behave during parallel requests and try things like disabling
reservations. I also like the idea of being able to verify the effects of
proposed fixes.
-melanie (irc: melwitt)
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
[email protected]?subject:unsubscribe<http://[email protected]?subject:unsubscribe>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
