(not for usage questions)
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] Quota management and enforcement across projects
I'm resurrecting this thread to provide an update on this effort.
I have been looking at Boson [1] as a base for starting
I'm resurrecting this thread to provide an update on this effort.
I have been looking at Boson [1] as a base for starting developing a
service for managing quotas and reservations [2].
Boson's model would satisfy most of the requirements for this service, and
implementing additional requirements,
On 11/17/2014 05:49 PM, Salvatore Orlando wrote:
Hi all,
I am resuming this thread following the session we had at the summit in
Paris (etherpad here [1])
While there was some sort of consensus regarding what this library
should do, and how it should do it, the session ended with some open
Le 18/11/2014 20:05, Doug Hellmann a écrit :
On Nov 17, 2014, at 7:18 PM, Kevin L. Mitchell kevin.mitch...@rackspace.com
wrote:
On Mon, 2014-11-17 at 18:48 -0500, Doug Hellmann wrote:
I’ve spent a bit of time thinking about the resource ownership issue.
The challenge there is we don’t
All I can say at the moment is that Usage and Quota management is a crappy
thing to do in OpenStack. Every service has it's own way of doing it both
in clients and api's. +n+ for making a effort in standardizing this thing
in a way that could be alike across projects..
2014-11-19 14:33 GMT+01:00
On Nov 19, 2014, at 8:33 AM, Sylvain Bauza sba...@redhat.com wrote:
Le 18/11/2014 20:05, Doug Hellmann a écrit :
On Nov 17, 2014, at 7:18 PM, Kevin L. Mitchell
kevin.mitch...@rackspace.com wrote:
On Mon, 2014-11-17 at 18:48 -0500, Doug Hellmann wrote:
I’ve spent a bit of time thinking
Le 19/11/2014 15:06, Doug Hellmann a écrit :
On Nov 19, 2014, at 8:33 AM, Sylvain Bauza sba...@redhat.com wrote:
Le 18/11/2014 20:05, Doug Hellmann a écrit :
On Nov 17, 2014, at 7:18 PM, Kevin L. Mitchell kevin.mitch...@rackspace.com
wrote:
On Mon, 2014-11-17 at 18:48 -0500, Doug Hellmann
On Nov 19, 2014, at 9:51 AM, Sylvain Bauza sba...@redhat.com wrote:
Le 19/11/2014 15:06, Doug Hellmann a écrit :
On Nov 19, 2014, at 8:33 AM, Sylvain Bauza sba...@redhat.com wrote:
Le 18/11/2014 20:05, Doug Hellmann a écrit :
On Nov 17, 2014, at 7:18 PM, Kevin L. Mitchell
@lists.openstack.org
Subject: Re: [openstack-dev] Quota management and enforcement across
projects
Message-ID: 13f4f7a1-d4ec-4d14-a163-d477a4fd9...@doughellmann.com
Content-Type: text/plain; charset=windows-1252
On Nov 19, 2014, at 9:51 AM, Sylvain Bauza sba...@redhat.com wrote:
My bad
On Thu, 2014-11-20 at 10:16 +1100, Blair Bethwaite wrote:
For actions initiated directly through core OpenStack service APIs
(Nova, Cinder, Neutron, etc - anything using Keystone policy),
shouldn't quota-enforcement be handled by Keystone? To me this is just
a subset of authz, and OpenStack
Apparently, like everything Openstack-y we have a gathered a good crowd of
people with different opinions, more or less different, more or less strong.
My only strong opinion is that any ocean-boiling attempt should be
carefully avoided, and any proposed approach should add as little as
possible
Regards
Chaoyi Huang ( Joe Huang )
-Original Message-
From: Kevin L. Mitchell [mailto:kevin.mitch...@rackspace.com]
Sent: Thursday, November 20, 2014 7:40 AM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] Quota management and enforcement across projects
On Thu, 2014-11
On Nov 17, 2014, at 7:18 PM, Kevin L. Mitchell kevin.mitch...@rackspace.com
wrote:
On Mon, 2014-11-17 at 18:48 -0500, Doug Hellmann wrote:
I’ve spent a bit of time thinking about the resource ownership issue.
The challenge there is we don’t currently have any libraries that
define tables in
Hi all,
I am resuming this thread following the session we had at the summit in
Paris (etherpad here [1])
While there was some sort of consensus regarding what this library should
do, and how it should do it, the session ended with some open questions
which we need to address before finalising
On Nov 17, 2014, at 5:49 PM, Salvatore Orlando sorla...@nicira.com wrote:
Hi all,
I am resuming this thread following the session we had at the summit in Paris
(etherpad here [1])
While there was some sort of consensus regarding what this library should do,
and how it should do it,
On Mon, 2014-11-17 at 18:48 -0500, Doug Hellmann wrote:
I’ve spent a bit of time thinking about the resource ownership issue.
The challenge there is we don’t currently have any libraries that
define tables in the schema of an application. I think that’s a good
pattern to maintain, since it
Manila project does use policy common code from incubator.
Our small wrapper for it:
https://github.com/openstack/manila/blob/8203c51081680a7a9dba30ae02d7c43d6e18a124/manila/policy.py
On Wed, Oct 15, 2014 at 2:41 AM, Salvatore Orlando sorla...@nicira.com
wrote:
Doug,
I totally agree with
But why policy is being discussed on quota thread?
On Wed, Oct 15, 2014 at 11:55 AM, Valeriy Ponomaryov
vponomar...@mirantis.com wrote:
Manila project does use policy common code from incubator.
Our small wrapper for it:
Sigh. Because I typed the wrong command. Thanks for pointing that out.
I don’t see any instances of “quota” in openstack-common.conf files:
$ grep quota */openstack-common.conf
or in any projects under openstack/“:
$ ls */*/openstack/common/quota.py
ls: cannot access
Hi,
Would the new library support quota on domain level also? As it stands in
oslo-incubator it only does quota enforcement on project level only. The
use case for this is quota enforcement across multiple projects. For e.g.
as a cloud provider, I would like my customer to create only #X volumes
Hi Doug,
do you know if the existing quota oslo-incubator module has already some
active consumers?
In the meanwhile I've pushed a spec to neutron-specs for improving quota
management there [1]
Now, I can either work on the oslo-incubator module and leverage it in
Neutron, or develop the quota
On Oct 14, 2014, at 12:31 PM, Salvatore Orlando sorla...@nicira.com wrote:
Hi Doug,
do you know if the existing quota oslo-incubator module has already some
active consumers?
In the meanwhile I've pushed a spec to neutron-specs for improving quota
management there [1]
It looks like a
Doug,
I totally agree with your findings on the policy module.
Neutron already has some customizations there and we already have a few
contributors working on syncing it back with oslo-incubator during the Kilo
release cycle.
However, my query was about the quota module.
From what I gather it
On 8 October 2014 04:13, Joe Gordon joe.gord...@gmail.com wrote:
On Fri, Oct 3, 2014 at 10:47 AM, Morgan Fainberg
morgan.fainb...@gmail.com wrote:
Keeping the enforcement local (same way policy works today) helps limit
the fragility, big +1 there.
I also agree with Vish, we need a
Salvatore, Joe,
We do have this at the moment:
https://github.com/openstack/oslo-incubator/blob/master/openstack/common/quota.py
-- dims
On Wed, Oct 8, 2014 at 2:29 AM, Salvatore Orlando sorla...@nicira.com wrote:
On 8 October 2014 04:13, Joe Gordon joe.gord...@gmail.com wrote:
On Fri,
On Fri, Oct 3, 2014 at 10:47 AM, Morgan Fainberg morgan.fainb...@gmail.com
wrote:
Keeping the enforcement local (same way policy works today) helps limit
the fragility, big +1 there.
I also agree with Vish, we need a uniform way to talk about quota
enforcement similar to how we have a
Hi,
Quota management is currently one of those things where every openstack
project does its own thing. While quotas are obviously managed in a similar
way for each project, there are subtle differences which ultimately result
in lack of usability.
I recall that in the past there have been
I recall that in the past there have been several calls for unifying quota
management.
The blueprint [1] for instance, hints at the possibility of storing quotas in
keystone.
As an end-user: +1
For me it totally makes sense to put the quotas and access together.
On the other hand, the
Taking quota out of the service / adding remote calls for quota
management is going to make things fragile - you've somehow got to
deal with the cases where your quota manager is slow, goes away,
hiccups, drops connections etc. You'll also need some way of
reconciling actual usage against quota
The proposal in the past was to keep quota enforcement local, but to
put the resource limits into keystone. This seems like an obvious first
step to me. Then a shared library for enforcing quotas with decent
performance should be next. The quota calls in nova are extremely
inefficient right now
Thanks Vish,
this seems a very reasonable first step as well - and since most projects
would be enforcing quotas in the same way, the shared library would be the
logical next step.
After all this is quite the same thing we do with authZ.
Duncan is expressing valid concerns which in my opinion
Keeping the enforcement local (same way policy works today) helps limit the
fragility, big +1 there.
I also agree with Vish, we need a uniform way to talk about quota
enforcement similar to how we have a uniform policy language / enforcement
model (yes I know it's not perfect, but it's far closer
[mailto:jaypi...@gmail.com]
Sent: Thursday, April 03, 2014 7:21 PM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] Quota Management
On Thu, 2014-04-03 at 14:41 -0500, Kevin L. Mitchell wrote:
On Thu, 2014-04-03 at 19:16 +, Cazzolato, Sergio J wrote:
Jay, thanks for taking
On 03/04/14 23:20, Jay Pipes wrote:
On Thu, 2014-04-03 at 14:41 -0500, Kevin L. Mitchell wrote:
On Thu, 2014-04-03 at 19:16 +, Cazzolato, Sergio J wrote:
Jay, thanks for taking ownership on this idea, we are really
interested to contribute to this, so what do you think are the next
steps
Hi All,
I'd like to know your thoughts regarding Quota Management... I've been
contributing to this topic for icehouse and noticed some issues and discussions
around its implementation like code is duplicated, synch problems with
database, not having an homogeneous logic, etc... so I was
On Thu, 2014-04-03 at 15:02 +, Cazzolato, Sergio J wrote:
Hi All,
I’d like to know your thoughts regarding Quota Management… I’ve been
contributing to this topic for icehouse and noticed some issues and
discussions around its implementation like code is duplicated, synch
problems with
On Thu, Apr 3, 2014 at 11:22 AM, Jay Pipes jaypi...@gmail.com wrote:
On Thu, 2014-04-03 at 15:02 +, Cazzolato, Sergio J wrote:
Hi All,
I’d like to know your thoughts regarding Quota Management… I’ve been
contributing to this topic for icehouse and noticed some issues and
On Thu, 2014-04-03 at 09:22 -0700, Jay Pipes wrote:
Boson does indeed look interesting, but who is working on it, if anyone
at this point? I agree that having a centralized quota management system
makes sense, in order to make the handling of quotas and reservations
consistent across projects
On Thu, 2014-04-03 at 12:13 -0500, Kevin L. Mitchell wrote:
On Thu, 2014-04-03 at 09:22 -0700, Jay Pipes wrote:
Boson does indeed look interesting, but who is working on it, if anyone
at this point? I agree that having a centralized quota management system
makes sense, in order to make the
On Thu, 2014-04-03 at 10:54 -0700, Jay Pipes wrote:
On Thu, 2014-04-03 at 12:13 -0500, Kevin L. Mitchell wrote:
On Thu, 2014-04-03 at 09:22 -0700, Jay Pipes wrote:
Boson does indeed look interesting, but who is working on it, if anyone
at this point? I agree that having a centralized
[mailto:kevin.mitch...@rackspace.com]
Sent: Thursday, April 03, 2014 3:13 PM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] Quota Management
On Thu, 2014-04-03 at 10:54 -0700, Jay Pipes wrote:
On Thu, 2014-04-03 at 12:13 -0500, Kevin L. Mitchell wrote:
On Thu, 2014-04-03 at 09:22 -0700, Jay
On Thu, 2014-04-03 at 19:16 +, Cazzolato, Sergio J wrote:
Jay, thanks for taking ownership on this idea, we are really
interested to contribute to this, so what do you think are the next
steps to move on?
Perhaps a summit session on quota management would be in order?
--
Kevin L. Mitchell
+1
-Original Message-
From: Kevin L. Mitchell [mailto:kevin.mitch...@rackspace.com]
Sent: Thursday, April 03, 2014 4:42 PM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] Quota Management
On Thu, 2014-04-03 at 19:16 +, Cazzolato, Sergio J wrote:
Jay, thanks
On Thu, 2014-04-03 at 14:41 -0500, Kevin L. Mitchell wrote:
On Thu, 2014-04-03 at 19:16 +, Cazzolato, Sergio J wrote:
Jay, thanks for taking ownership on this idea, we are really
interested to contribute to this, so what do you think are the next
steps to move on?
Perhaps a summit
Glad to see that, for sure I'll participate of this session.
Thanks
-Original Message-
From: Jay Pipes [mailto:jaypi...@gmail.com]
Sent: Thursday, April 03, 2014 7:21 PM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] Quota Management
On Thu, 2014-04-03 at 14:41
45 matches
Mail list logo
