Open Stack

That's a relieve! As you said, we designed the Quota API using the Trust API as example, so it is not in the default pipeline, and we hope to commit it soon for being reviewed. But the design is open for reviewing and feedback https://wiki.openstack.org/wiki/DomainQuotaManagementAndEnforcement

Regards,
Tiago

From: Dolph Mathews [mailto:dolph.mathews at gmail.com]
Sent: terça-feira, 2 de julho de 2013 11:33
To: OpenStack Development Mailing List
Cc: Dmitry Stepanenko
Subject: Re: [openstack-dev] [Openstack] Keystone store-quota-data blueprint


On Monday, July 1, 2013, Jamie Lennox wrote:
On Tue, 2013-07-02 at 02:03 +0000, Everett Toews wrote:
> This topic came up at the last summit in Portland at [1] and [2].
>
>
> Yehia and another colleague of his from HP had a design that was
> discussed and it seemed like they were going to start work on it.
> Another developer from CERN expressed interest too. I'm not sure if
> anything ever really got started on it.
>
>
> I think you'll want to wait until Dolph gets back (next week?) before
> doing any major work on it. Ask him before moving forward.

Also know that Dolph has said that nothing that affects the API will be
accepted after h-2 so it would have to be finished, reviewed and
commited by the 16th. Given that he's away and the discussion that would
be around this I'd say it's very tight.

"away" ... apparently they have the internet on islands, too.

Henry Nash brought up the issue of extensions that are not included in the default pipeline (which is how I think quota storage should be spec'd and implemented) vs the API feature freeze. The goal of the API feature freeze is to avoid crunch time (and producing new bugs) on release critical / core API functionality while we should be focusing on stability and polish there. I don't think extension development necessarily conflicts with that goal (besides sapping review bandwidth), so I'm happy to see them merge during milestone 3.

Granted, a whole bunch of m2 bp's already in review / approaching review fall into that category, but we should still try and get them in before m3 :)




> Regards,
> Everett
>
>
> [1] http://openstacksummitapril2013.sched.org/event/c0c6befcb4361e54d5c7e45b2f772de7
> [2] http://openstacksummitapril2013.sched.org/event/7bf2cdde2dfad733b499d9c2a3f60b08
>
>
> P.S. This email really belongs in openstack-dev
>
> On Jul 1, 2013, at 10:24 AM, Dmitry Stepanenko wrote:
>
> > Hi folks,
> >
> >
> > we're going to work on store-quota-data blueprint
> > (https://blueprints.launchpad.net/keystone/+spec/store-quota-data).
> > Did anyone already work on it?
> >
> >
> > Thanks & regards,
> > Dmitry
> > _______________________________________________
> > Mailing list: https://launchpad.net/~openstack
> > Post to     : openstack at lists.launchpad.net<javascript:;>
> > Unsubscribe : https://launchpad.net/~openstack
> > More help   : https://help.launchpad.net/ListHelp
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack at lists.launchpad.net<javascript:;>
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp




_______________________________________________
OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org<javascript:;>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


--

-Dolph
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130702/4813df75/attachment.html>