Re: [openstack-dev] [cross-project] [all] Quotas -- service vs. library

On 03/16/2016 07:10 AM, Attila Fazekas wrote: NO : For any kind of extra quota service. In other places I saw other reasons for a quota service or similar, the actual cost of this approach is higher than most people would think so NO. Maybe Library, But I do not want to see for example the

Re: [openstack-dev] [cross-project] [all] Quotas -- service vs. library

Thanks for your feedback Erno. I've answered your question inline. On 3/17/16 2:21 AM, Erno Kuvaja wrote: > On Wed, Mar 16, 2016 at 6:25 AM, Nikhil Komawar > wrote: > > Hello everyone, > > > > tl;dr; > > I'm writing to request

Re: [openstack-dev] [cross-project] [all] Quotas -- service vs. library

Hi Amrith, Thank you for your feedback and asking all the important questions. Over the last week, I've interacted with people who are willing to work on this, who have been involved in this, who have stake in this, etc. Based on the digest of all of those I intend to reply to your questions.

Re: [openstack-dev] [cross-project] [all] Quotas -- service vs. library

, March 16, 2016 9:58 AM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [cross-project] [all] Quotas -- service vs. library On 03/16/2016 05:22 AM, Julien Danjou wrote: > On Wed, Mar 16 2016, Attila Fazekas wrote: > >> The quota usage handling MUST happen in t

Re: [openstack-dev] [cross-project] [all] Quotas -- service vs. library

On Wed, 16 Mar 2016, Salvatore Orlando wrote: - Looking at quotas it is worth distinguishing between management (eg:: resource limits per tenant and/or users), and enforcement (eg.: can the bakery service give me 4 cookies or did I already eat too many?) While for the reasons listed throughout

Re: [openstack-dev] [cross-project] [all] Quotas -- service vs. library

On 16/03/2016 06:28, Nikhil Komawar wrote: > Hello everyone, > > tl;dr; > I'm writing to request some feedback on whether the cross project Quotas > work should move ahead as a service or a library or going to a far > extent I'd ask should this even be in a common repository, would > projects

Re: [openstack-dev] [cross-project] [all] Quotas -- service vs. library

This has been proposed a number of times in the past with projects such as Boson (https://wiki.openstack.org/wiki/Boson) and an extended discussion at one of the summits (I think it was San Diego). Then, there were major reservations from the PTLs at the impacts in terms of latency, ability

Re: [openstack-dev] [cross-project] [all] Quotas -- service vs. library

On 16/03/2016 9:39 AM, Sean Dague wrote: > This has to live inside all the upgrade constraints we currently have > (like online data migration in the Nova case), otherwise it's a non starter. completely agree -- gord __

Re: [openstack-dev] [cross-project] [all] Quotas -- service vs. library

On Wed, Mar 16, 2016 at 6:25 AM, Nikhil Komawar wrote: > Hello everyone, > > tl;dr; > I'm writing to request some feedback on whether the cross project Quotas > work should move ahead as a service or a library or going to a far > extent I'd ask should this even be in a

Re: [openstack-dev] [cross-project] [all] Quotas -- service vs. library

Excerpts from Sean Dague's message of 2016-03-16 06:09:47 -0400: > On 03/16/2016 05:46 AM, Duncan Thomas wrote: > > On 16 March 2016 at 09:15, Tim Bell > > wrote: > > > > Then, there were major reservations from the PTLs at the impacts in > >

Re: [openstack-dev] [cross-project] [all] Quotas -- service vs. library

On 03/16/2016 08:27 AM, Amrith Kumar wrote: > Nikhil, thank you for the very timely posting. This is a topic that has > been discussed quite a bit recently within the Trove team. I've read the > document you reference as [1] and I have not been part of earlier > conversations on this subject so I

Re: [openstack-dev] [cross-project] [all] Quotas -- service vs. library

I'm not sure if this was mentioned already throughout the thread, however as I've been working a bit on quotas in the past I might have some additional information: - Looking at quotas it is worth distinguishing between management (eg:: resource limits per tenant and/or users), and enforcement

Re: [openstack-dev] [cross-project] [all] Quotas -- service vs. library

There are two types of quotas you may want to enforce in an OpenStack project: technical and business. Technical quotas are things that are hard limits of the system based on either actual resources available or protecting the system itself. For example, you can't provision a 2TB volume if you

Re: [openstack-dev] [cross-project] [all] Quotas -- service vs. library

On 03/16/2016 05:22 AM, Julien Danjou wrote: On Wed, Mar 16 2016, Attila Fazekas wrote: The quota usage handling MUST happen in the same DB transaction as the resource record (volume, server..) create/update/delete . […] We have a transaction capable DB, to help us, not using it would be

Re: [openstack-dev] [cross-project] [all] Quotas -- service vs. library

On 03/16/2016 09:34 AM, gordon chung wrote: > > > On 16/03/2016 7:10 AM, Attila Fazekas wrote: >> >> NO : For any kind of extra quota service. >> >> In other places I saw other reasons for a quota service or similar, >> the actual cost of this approach is higher than most people would think so

Re: [openstack-dev] [cross-project] [all] Quotas -- service vs. library

On 03/16/2016 08:42 AM, Sean Dague wrote: > On 03/16/2016 08:27 AM, Amrith Kumar wrote: >> Nikhil, thank you for the very timely posting. This is a topic that has >> been discussed quite a bit recently within the Trove team. I've read the >> document you reference as [1] and I have not been part

Re: [openstack-dev] [cross-project] [all] Quotas -- service vs. library

On 16/03/2016 7:10 AM, Attila Fazekas wrote: > > NO : For any kind of extra quota service. > > In other places I saw other reasons for a quota service or similar, > the actual cost of this approach is higher than most people would think so > NO. > > > Maybe Library, > But I do not want to see

Re: [openstack-dev] [cross-project] [all] Quotas -- service vs. library

Nikhil, thank you for the very timely posting. This is a topic that has been discussed quite a bit recently within the Trove team. I've read the document you reference as [1] and I have not been part of earlier conversations on this subject so I may be missing some context here. I feel that the

Re: [openstack-dev] [cross-project] [all] Quotas -- service vs. library

On 16 March 2016 at 10:09, Sean Dague wrote: > On 03/16/2016 05:46 AM, Duncan Thomas wrote: >> On 16 March 2016 at 09:15, Tim Bell > > wrote: >> >> Then, there were major reservations from the PTLs at the impacts in >> terms of

Re: [openstack-dev] [cross-project] [all] Quotas -- service vs. library

On 03/16/2016 10:04 AM, Davanum Srinivas wrote: To complete the context: https://review.openstack.org/#/c/132127/ https://etherpad.openstack.org/p/kilo-oslo-common-quota-library (from https://wiki.openstack.org/wiki/Design_Summit/Kilo/Etherpads) -- Dims On Wed, Mar 16, 2016 at 9:53 AM, Doug

Re: [openstack-dev] [cross-project] [all] Quotas -- service vs. library

To complete the context: https://review.openstack.org/#/c/132127/ https://etherpad.openstack.org/p/kilo-oslo-common-quota-library (from https://wiki.openstack.org/wiki/Design_Summit/Kilo/Etherpads) -- Dims On Wed, Mar 16, 2016 at 9:53 AM, Doug Hellmann wrote: > Excerpts

Re: [openstack-dev] [cross-project] [all] Quotas -- service vs. library

On Wed, Mar 16 2016, Attila Fazekas wrote: > The quota usage handling MUST happen in the same DB transaction as the > resource record (volume, server..) create/update/delete . […] > We have a transaction capable DB, to help us, > not using it would be lame. Amen to that. -- Julien Danjou

Re: [openstack-dev] [cross-project] [all] Quotas -- service vs. library

gt; > To: "OpenStack Development Mailing List" <openstack-dev@lists.openstack.org> > > Sent: Wednesday, March 16, 2016 7:25:26 AM > > Subject: [openstack-dev] [cross-project] [all] Quotas -- service vs. library > > > > Hello everyone, > > > > t

Re: [openstack-dev] [cross-project] [all] Quotas -- service vs. library

On 03/16/2016 05:42 AM, Sean Dague wrote: On 03/16/2016 08:27 AM, Amrith Kumar wrote: Nikhil, thank you for the very timely posting. This is a topic that has been discussed quite a bit recently within the Trove team. I've read the document you reference as [1] and I have not been part of

Re: [openstack-dev] [cross-project] [all] Quotas -- service vs. library

ailing List" <openstack-dev@lists.openstack.org> > Sent: Wednesday, March 16, 2016 7:25:26 AM > Subject: [openstack-dev] [cross-project] [all] Quotas -- service vs. library > > Hello everyone, > > tl;dr; > I'm writing to request some feedback on whether the cross projec

Re: [openstack-dev] [cross-project] [all] Quotas -- service vs. library

On 03/16/2016 05:46 AM, Duncan Thomas wrote: > On 16 March 2016 at 09:15, Tim Bell > wrote: > > Then, there were major reservations from the PTLs at the impacts in > terms of > latency, ability to reconcile and loss of control (transactions

Re: [openstack-dev] [cross-project] [all] Quotas -- service vs. library

On 16 March 2016 at 09:15, Tim Bell wrote: Then, there were major reservations from the PTLs at the impacts in terms of > latency, ability to reconcile and loss of control (transactions are > difficult, transactions > across services more so). > > Not just PTLs :-) > > I

Re: [openstack-dev] [cross-project] [all] Quotas -- service vs. library

Nikhil, Thank you for rising this question. IMHO quotas should be moved into separated services (this is right micro services approach). It will make a lot of things simpler: 1) this removes a lot of logic/code from projects 2) cross project atomic quotas reservation (will be possible) (e.g.

Re: [openstack-dev] [cross-project] [all] Quotas -- service vs. library

On 16/03/16 07:25, "Nikhil Komawar" wrote: >Hello everyone, > >tl;dr; >I'm writing to request some feedback on whether the cross project Quotas >work should move ahead as a service or a library or going to a far >extent I'd ask should this even be in a common repository,

[openstack-dev] [cross-project] [all] Quotas -- service vs. library

Hello everyone, tl;dr; I'm writing to request some feedback on whether the cross project Quotas work should move ahead as a service or a library or going to a far extent I'd ask should this even be in a common repository, would projects prefer to implement everything from scratch in-tree? Should