Open Stack

Hi Kevin,

Thanks for your interest!

In the current implementation for Nested Quota, we want to provide a better
way to handle with Hierarchical Multitenancy on Nova, like we did on Cinder
<https://github.com/openstack/cinder/commit/8a7ab267a6bbd48fc5e9ccb91a1472cf1e017e3f>.
Also, I already created the subteam on the etherpad:
https://etherpad.openstack.org/p/mitaka-nova-priorities-tracking

About the re-design, I agree the quota concept that we have today it's not
optimized and consistent.  I think that the problem that we're trying to
solve is create a simple solution that says if the user should or shouldn't
perform the action. Some similar what we are doing with the policy
enforcement.

If we want discuss more about it, i'm available :)

Cheers,

Raildo

On Mon, Nov 23, 2015 at 2:30 PM Kevin L. Mitchell <
kevin.mitchell at rackspace.com> wrote:

> On Fri, 2015-11-20 at 16:13 +0000, Raildo Mascena wrote:
> > Me and other guys are working in the nested quota driver
> > (https://review.openstack.org/#/q/status:open+project:openstack/nova
> > +branch:master+topic:bp/nested-quota-driver-api,n,z) on Nova.
> >
> >
> > in addition, We want discuss the re-design of the quota implementation
> > on nova and in other projects, like cinder and neutron and we already
> > have a base spec for this here:
> >
> https://review.openstack.org/#/c/182445/4/specs/backlog/approved/quotas-reimagined.rst
> >
> >
> > So was I thinking on create a subteam on Nova to speed up the code
> > review in the nested quota implementation and discuss this re-design
> > of quotas. Someone have interest on be part of this subteam or
> > suggestions?
>
> Given my history of working on the nova quota code, I'm potentially
> interested in participating.  However, I'd like to start off by asking
> if "quota" is the correct concept?  It might be worthwhile to make a
> detour and consider what the problem is we're actually trying to solve.
> I think in the end it'll still end up being recognizably "quota", but I
> think it would be a worthwhile exercise and may provide better insights…
> --
> Kevin L. Mitchell <kevin.mitchell at rackspace.com>
> Rackspace
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20151125/9a294935/attachment.html>