Sending a follow up here since there has been some movement on this
recently.
There is a nova specification up for review that goes through the work to
consume unified limits out of keystone [0]. John and Jay have also been
working through the oslo.limit integration, which is forcing us to think
a
Extra eyes on the API would be appreciated. We're also close to the point
where we can start incorporating oslo.limit into services, so preparing
those changes might be useful, too.
One of the outcomes from yesterday's session was that Jay and Mel (from
nova) were going to work out some examples w
I recommend li...@unitedstack.com to join in to help to work forward.
May be first we should the keystone unified limits api really ok or
something else ?
Lance Bragstad 于2018年9月8日周六 上午2:35写道：
>
> That would be great! I can break down the work a little bit to help describe
> where we are at with
We had an extensive discussion of this in the keystone room today:
https://etherpad.openstack.org/p/keystone-stein-unified-limits
We had a couple of Nova people in the room, so if anyone from other
teams can take a look at the outcomes on the etherpad and let us know if
there are any issues wi
We had talked about Tuesday afternoon. I need to sync up with Lance and
figure out exactly when will work best.
On 09/08/2018 10:58 AM, Jay S Bryant wrote:
Ben,
Ping me when you are planning on having this discussion if you think of
it. Since there is interest in this for Cinder I would like
Ben,
Ping me when you are planning on having this discussion if you think of
it. Since there is interest in this for Cinder I would like to try to
be there.
Thanks!
Jay
On 9/7/2018 1:43 PM, Ben Nemec wrote:
I will also note that I had an oslo.limit topic on the Oslo PTG
schedule: https:/
I will also note that I had an oslo.limit topic on the Oslo PTG
schedule: https://etherpad.openstack.org/p/oslo-stein-ptg-planning
I don't know whether anybody from Jaze's team will be there, but if so
that would be a good opportunity for some face-to-face discussion. I
didn't give it a whole
That would be great! I can break down the work a little bit to help
describe where we are at with different parts of the initiative. Hopefully
it will be useful for your colleagues in case they haven't been closely
following the effort.
# keystone
Based on the initial note in this thread, I'm sur
Lance Bragstad 于2018年9月6日周四 下午10:01写道：
>
> I wish there was a better answer for this question, but currently there are
> only a handful of us working on the initiative. If you, or someone you know,
> is interested in getting involved, I'll happily help onboard people.
Well，I can recommend some
I wish there was a better answer for this question, but currently there are
only a handful of us working on the initiative. If you, or someone you
know, is interested in getting involved, I'll happily help onboard people.
On Wed, Sep 5, 2018 at 8:52 PM Jaze Lee wrote:
> On Stein only one service
On Stein only one service?
Is there some methods to move this more fast?
Lance Bragstad 于2018年9月5日周三 下午9:29写道：
>
> Not yet. Keystone worked through a bunch of usability improvements with the
> unified limits API last release and created the oslo.limit library. We have a
> patch or two left to la
Not yet. Keystone worked through a bunch of usability improvements with the
unified limits API last release and created the oslo.limit library. We have
a patch or two left to land in oslo.limit before projects can really start
using unified limits [0].
We're hoping to get this working with at leas
Hello,
Does nova and cinder use keystone's unified limits api to do quota job?
If not, is there a plan to do this?
Thanks a lot.
--
谦谦君子
__
OpenStack Development Mailing List (not for usage questions)
Unsubscrib
13 matches
Mail list logo
