Excerpts from Lance Bragstad's message of 2018-03-12 11:45:28 -0500:
> I missed the document describing the process for this sort of thing [0].
> So I'm back tracking a bit to go through a more formal process.
>
> [0]
>
The following may give u some more insight into delimiter,
https://review.openstack.org/#/c/284454/
-Josh
Lance Bragstad wrote:
I missed the document describing the process for this sort of thing [0].
So I'm back tracking a bit to go through a more formal process.
[0]
Huge +1 from me on bringing sanity to the various quota implementations
in OpenStack. This is something we discussed back in Paris, but the
conclusion at the time was that it wasn't practical for it to live in
Oslo because there was no place for Oslo to store the data (Oslo libs
dictating db
I missed the document describing the process for this sort of thing [0].
So I'm back tracking a bit to go through a more formal process.
[0]
http://specs.openstack.org/openstack/oslo-specs/specs/policy/new-libraries.html
# Proposed new library oslo.limit
This is a proposal to create a new
So the following was a prior effort:
https://github.com/openstack/delimiter
Maybe just continue down the path of that and/or take that whole repo
over and iterate (or adjust the prior code, or ...)?? Or if not that's
ok to, ya'll get to decide.
Yeah, we need a unified limit library , from oslo side we need a spec
according to new library process. The spec will be useful to track the
background and update oslo wiki [1]
[0]
http://specs.openstack.org/openstack/oslo-specs/specs/policy/new-libraries.html
[1]
On 03/07/2018 09:49 AM, Lance Bragstad wrote:
On 03/07/2018 09:31 AM, Chris Friesen wrote:
On 03/07/2018 08:58 AM, Lance Bragstad wrote:
Hi all,
Per the identity-integration track at the PTG [0], I proposed a new oslo
library for services to use for hierarchical quota enforcement [1]. Let
On 03/07/2018 10:33 AM, Tim Bell wrote:
Sorry, I remember more detail now... it was using the 'owner' of the VM as part
of the policy rather than quota.
Is there a per-user/per-group quota in Nova?
Nova supports setting quotas for individual users within a project (as long as
they are
t 17:29
> To: "OpenStack Development Mailing List (not for usage questions)" <
> openstack-dev@lists.openstack.org>
> Subject: Re: [openstack-dev] [keystone] [oslo] new unified limit library
>
>
> There was discussion that Nova would deprecate the user quota fea
e questions)"
<openstack-dev@lists.openstack.org>
Date: Wednesday, 7 March 2018 at 17:29
To: "OpenStack Development Mailing List (not for usage questions)"
<openstack-dev@lists.openstack.org>
Subject: Re: [openstack-dev] [keystone] [oslo] new unified limit library
7 March 2018 at 16:51
To: "openstack-dev@lists.openstack.org" <openstack-dev@lists.openstack.org>
Subject: Re: [openstack-dev] [keystone] [oslo] new unified limit library
On 03/07/2018 09:31 AM, Chris Friesen wrote:
> On 03/07/2018 08:58 AM, Lance Bragstad wrote:
&g
On 03/07/2018 09:31 AM, Chris Friesen wrote:
> On 03/07/2018 08:58 AM, Lance Bragstad wrote:
>> Hi all,
>>
>> Per the identity-integration track at the PTG [0], I proposed a new oslo
>> library for services to use for hierarchical quota enforcement [1]. Let
>> me know if you have any questions
On 03/07/2018 08:58 AM, Lance Bragstad wrote:
Hi all,
Per the identity-integration track at the PTG [0], I proposed a new oslo
library for services to use for hierarchical quota enforcement [1]. Let
me know if you have any questions or concerns about the library. If the
oslo team would like, I
Hi all,
Per the identity-integration track at the PTG [0], I proposed a new oslo
library for services to use for hierarchical quota enforcement [1]. Let
me know if you have any questions or concerns about the library. If the
oslo team would like, I can add an agenda item for next weeks oslo
14 matches
Mail list logo
