Hi,
Basically we should kill quota classes.
It required out of tree stuff that was never implemented, AFAIK.
When I checked with Kevin about this, my memory says the idea was out
of tree authorization plugin would populate context.quota_class with
something like "i_have_big_credit_limit" or
On 10/25/2018 02:44 PM, melanie witt wrote:
On Thu, 25 Oct 2018 14:00:08 -0400, Jay Pipes wrote:
On 10/25/2018 01:38 PM, Chris Friesen wrote:
On 10/24/2018 9:10 AM, Jay Pipes wrote:
Nova's API has the ability to create "quota classes", which are
basically limits for a set of resource types.
On Thu, 25 Oct 2018 15:06:38 -0500, Matt Riedemann wrote:
On 10/25/2018 2:55 PM, Chris Friesen wrote:
2) The main benefit (as I see it) of the quota class API is to allow
dynamic adjustment of the default quotas without restarting services.
I could be making this up, but I want to say back at
On 10/25/2018 2:55 PM, Chris Friesen wrote:
2) The main benefit (as I see it) of the quota class API is to allow
dynamic adjustment of the default quotas without restarting services.
I could be making this up, but I want to say back at the Pike PTG people
were also complaining that not having
On 10/25/2018 12:00 PM, Jay Pipes wrote:
On 10/25/2018 01:38 PM, Chris Friesen wrote:
On 10/24/2018 9:10 AM, Jay Pipes wrote:
Nova's API has the ability to create "quota classes", which are
basically limits for a set of resource types. There is something
called the "default quota class" which
On Thu, 25 Oct 2018 14:00:08 -0400, Jay Pipes wrote:
On 10/25/2018 01:38 PM, Chris Friesen wrote:
On 10/24/2018 9:10 AM, Jay Pipes wrote:
Nova's API has the ability to create "quota classes", which are
basically limits for a set of resource types. There is something
called the "default quota
On 10/25/2018 01:38 PM, Chris Friesen wrote:
On 10/24/2018 9:10 AM, Jay Pipes wrote:
Nova's API has the ability to create "quota classes", which are
basically limits for a set of resource types. There is something
called the "default quota class" which corresponds to the limits in
the
On 10/24/2018 9:10 AM, Jay Pipes wrote:
Nova's API has the ability to create "quota classes", which are
basically limits for a set of resource types. There is something called
the "default quota class" which corresponds to the limits in the
CONF.quota section. Quota classes are basically
melanie witt wrote on 10/25/2018 02:14:40 AM:
> On Thu, 25 Oct 2018 14:12:51 +0900, ボーアディネシュ[bhor Dinesh] wrote:
> > We were having a similar use case like *Preemptible Instances* called
as
> > *Rich-VM’s* which
> >
> > are high in resources and are deployed each per hypervisor. We have a
> >
On Thu, 25 Oct 2018 14:12:51 +0900, ボーアディネシュ[bhor Dinesh] wrote:
We were having a similar use case like *Preemptible Instances* called as
*Rich-VM’s* which
are high in resources and are deployed each per hypervisor. We have a
custom code in
production which tracks the quota for such
On Wed, 24 Oct 2018 12:54:00 -0700, Melanie Witt wrote:
On Wed, 24 Oct 2018 13:57:05 -0500, Matt Riedemann wrote:
On 10/24/2018 10:10 AM, Jay Pipes wrote:
I'd like to propose deprecating this API and getting rid of this
functionality since it conflicts with the new Keystone /limits endpoint,
Message-
From: "Kevin L. Mitchell"
To: "OpenStack Development Mailing List (not for usage
questions)";
"openstack-operat...@lists.openstack.org";
Cc:
Sent: Oct 25, 2018 (Thu) 11:35:08
Subject: Re: [openstack-dev] [nova][limits] Does ANYONE at all use the quot
> On 10/24/18 10:10, Jay Pipes wrote:
> > Nova's API has the ability to create "quota classes", which are
> > basically limits for a set of resource types. There is something called
> > the "default quota class" which corresponds to the limits in the
> > CONF.quota section. Quota classes are
so FYI, in case people missing this spec, there is spec from John
https://review.openstack.org/#/c/602201/3/specs/stein/approved/unified-limits-stein.rst@170
the roadmap of this spec is also saying deprecate the quota-class API.
melanie witt 于2018年10月25日周四 上午3:54写道:
> On Wed, 24 Oct 2018
On Wed, Oct 24, 2018 at 2:49 PM Jay Pipes wrote:
> On 10/24/2018 02:57 PM, Matt Riedemann wrote:
> > On 10/24/2018 10:10 AM, Jay Pipes wrote:
> >> I'd like to propose deprecating this API and getting rid of this
> >> functionality since it conflicts with the new Keystone /limits
> >> endpoint,
On Wed, 24 Oct 2018 13:57:05 -0500, Matt Riedemann wrote:
On 10/24/2018 10:10 AM, Jay Pipes wrote:
I'd like to propose deprecating this API and getting rid of this
functionality since it conflicts with the new Keystone /limits endpoint,
is highly coupled with RAX's turnstile middleware and I
On 10/24/2018 02:57 PM, Matt Riedemann wrote:
On 10/24/2018 10:10 AM, Jay Pipes wrote:
I'd like to propose deprecating this API and getting rid of this
functionality since it conflicts with the new Keystone /limits
endpoint, is highly coupled with RAX's turnstile middleware and I
can't seem
On 10/24/2018 10:10 AM, Jay Pipes wrote:
I'd like to propose deprecating this API and getting rid of this
functionality since it conflicts with the new Keystone /limits endpoint,
is highly coupled with RAX's turnstile middleware and I can't seem to
find anyone who has ever used it. Deprecating
Forwarding to openstack-operators per Jay.
On 10/24/18 10:10, Jay Pipes wrote:
> Nova's API has the ability to create "quota classes", which are
> basically limits for a set of resource types. There is something called
> the "default quota class" which corresponds to the limits in the
>
19 matches
Mail list logo