[openstack-dev] [cross-project][quotas][delimiter] Austin Summit - Design Session Summary

Hi All, For people who missed the design summit session on Delimiter - Cross project Quota enforcement library here is a gist of what we discussed. Etherpad [1] captures the details. 1. Delimiter will not be responsible for rate-limiting. 2. Delimiter will not maintain data for the projects. 3.

Re: [openstack-dev] More on the topic of DELIMITER, the Quota Management Library proposal

a whole >>>> bunch >>>> of code that does post-auditing of claims and quotas and a system >>>> that >>>> accepts that oversubscription and out-of-sync quota limits and usages >>>> is >>>> a fact of life. Not to mention needing to implement JOINs in Python. &

Re: [openstack-dev] More on the topic of DELIMITER, the Quota Management Library proposal

I strongly agree with Jay on the points related to "no reservation" , keeping the interface simple and the role for Delimiter (impose limits on resource consumption and enforce quotas). The point to keep user quota, tenant quotas in Keystone sounds interestring and would need support from

[openstack-dev] [cross-project] [all] Quotas and the need for reservation

Hi All, As part of the cross project Quota library effort [1] there has been a discussion around the need for reservations or getting rid of reservations altogether. It is believed that reservation help to to reserve a set of resources beforehand and hence eventually preventing any other

Re: [openstack-dev] [magnum] Proposing Eli Qiao for Magnum core reviewer team

+1 On Sat, Apr 2, 2016 at 7:24 AM, Kai Qiang Wu wrote: > + 1 for Eli :) > > > Thanks > > Best Wishes, > > > Kai Qiang Wu (吴开强 Kennan） > IBM China System and Technology Lab, Beijing > > E-mail:

Re: [openstack-dev] [oslo] PTL for Newton and beyond

Thanks for all the hard work Dims! On Wed, Mar 9, 2016 at 3:06 AM, Ivan Kolodyazhny wrote: > Thanks for your hard work, Dims! > > Regards, > Ivan Kolodyazhny, > http://blog.e0ne.info/ > > On Fri, Mar 4, 2016 at 3:34 PM, Mehdi Abaakouk wrote: > >> Hi, >> >>

Re: [openstack-dev] [magnum-ui] Proposed Core addition, and removal notice

blockquote, div.yahoo_quoted { margin-left: 0 !important; border-left:1px #715FFA solid !important; padding-left:1ex !important; background-color:white !important; } +1 for Shu.  He has been contributing consistently to magnum-ui. Keep up the good work! Sent from Yahoo Mail for iPhone On

Re: [openstack-dev] [magnum] containers across availability zones

+1 from me too for the idea. Please file a blueprint. Seems feasible and useful. -Vilobh On Tue, Feb 23, 2016 at 7:25 PM, Adrian Otto wrote: > Ricardo, > > Yes, that approach would work. I don’t see any harm in automatically > adding tags to the docker daemon on the

Re: [openstack-dev] [Magnum] Bug 1541105 options

Hi Corey, This is slowing down our merge rate and needs to be fixed IMHO. What risk are you talking about when using newer version of etcd ? Is it documented somewhere for the team to have a look ? -Vilobh On Wed, Feb 3, 2016 at 8:11 AM, Corey O'Brien wrote: > Hey

Re: [openstack-dev] [Magnum] New Core Reviewers

+1 from me for both. On Mon, Feb 1, 2016 at 10:00 AM, Gal Sagie wrote: > Not part of Magnum team, but Egor is a great help for Kuryr as well and is > a great addition in my eyes > > On Mon, Feb 1, 2016 at 7:00 PM, Davanum Srinivas > wrote: > >> +1 from

Re: [openstack-dev] [openstack][magnum][heat] Quota for Magnum Resources

doing a great job at since I changed > my focus. I'd be interested to hear if operators have been lamenting > the lack of quotas in heat. > > BTW, in the quoted emails, there are multiple 2)'s. You should probably > reply in-line so it is clear what you mean. > > > On Tue, Dec

Re: [openstack-dev] [openstack][magnum] Quota for Magnum Resources

As mentioned by Hongbin we might have these 3 cases. Hongbin and I did discuss about these in the Magnum IRC. The interestring case being the #2 one. Where in case enough resources are not available at the IaaS layer, and Magnum is in the process of creating a Bay; Magnum needs to be more

Re: [openstack-dev] [openstack][magnum] Quota for Magnum Resources

The intent here in Magnum is to enforce quota on resources owned by Magnum (#of bays etc that are allowed to be created for a user in a project). +1 to Lee that "Resources created by Magnum COEs should be governed by existing quota policies governing said resources (e.g. Nova and vCPUs).".

Re: [openstack-dev] [openstack][magnum] Quota for Magnum Resources

> Adrian > > > > On Dec 14, 2015, at 10:22 PM, Tim Bell <tim.b...@cern.ch> wrote: > > > > Can we have nested project quotas in from the beginning ? Nested projects > are in Keystone V3 from Kilo onwards and retrofitting this is hard work. > > > > Fo

[openstack-dev] [openstack][magnum] Quota for Magnum Resources

Hi All, Currently, it is possible to create unlimited number of resource like bay/pod/service/. In Magnum, there should be a limitation for user or project to create Magnum resource, and the limitation should be configurable[1]. I proposed following design :- 1. Introduce new table

Re: [openstack-dev] [nova]New Quota Subteam on Nova

I am highly supportive for the idea of Nova Quota sub-team, for something as complex as Quota, as it helps to move quickly on reviews and changes. Agree with John, a test framework to test quotas will be helpful and can be one of the first task the Nova Quota sub team can focus on as that will

Re: [openstack-dev] [all] Outcome of distributed lock manager discussion @ the summit

I will be working on adding the Consul driver to Tooz [1]. -Vilobh [1] https://blueprints.launchpad.net/python-tooz/+spec/add-consul-driver On Wed, Nov 4, 2015 at 2:05 PM, Mark Voelker wrote: > On Nov 4, 2015, at 4:41 PM, Gregory Haynes wrote: > > > >

[openstack-dev] [openstack] [nova] Instance snapshot creation locally and Negative values returned by Resource Tracker

Hi All, I see negative values being returned by resource tracker, which is surprising, since enough capacity is available on Hypervisor (as seen through df -ha output [0]). In my setup I have configured nova.conf to created instance snapshot locally and I *don't have* disk-filter enabled. Local

Re: [openstack-dev] [magnum] New Core Reviewers

e for both Vilobh and Hua. >> >> >> >> Thanks, >> >> Dims >> >> >> >> On Wed, Sep 30, 2015 at 6:47 PM, Adrian Otto <adrian.o...@rackspace.com> >> wrote: >> >> Core Reviewers, >> >> I propose the following

[openstack-dev] [nova] Servicegroup refactoring for the Control Plane - Mitaka

Hi All, As part of Liberty spec [1] was approved with the conclusion that nova.services data be stored and managed by respective driver backend that is selected by the CONF.servicegroup_driver (which can be DB/Zookeeper/Memcache). When this spec was proposed again for Mitaka[3], the idea that

[openstack-dev] [magnum] Unit Tests Objects from Bay

Hi All, As discussed in today's weekly meeting sending the list of Unit Tests that need to be modified as part of "Objects from Bay" feature[1]. Right now after the switch to k8s v1 api yesterday, the changes for Replication Controller are up [2] will update the patches for Service object and

[openstack-dev] [magnum] Should pod/rc/service 'bay_uuid' be foreign key for Bay 'uuid' ?

Hi All, K8s resources Pod/RC/Service share same 'bay_uuid' which it gets from the Bay 'uuid' (which happens to be the primary key for Bay). Shouldn't it be a good idea to make pod/rc/service 'bay_uuid' be foreign key for Bay 'uuid'. Are there any cons in doing so ? Why was it done in this

[openstack-dev] [Magnum] Obtain the objects from the bay endpoint

Hi All, As discussed in today's Magnum weekly meeting I had shown interest to work on [1]. Problem :- Currently objects (pod/rc/service) are read from the database. In order for native clients to work, they must be read from the ReST bay endpoint. To execute native clients, we must have one

Re: [openstack-dev] [cinder] Nested Quota Driver and policy.json changes

Hi, While developing Nested Quota Driver for Cinder, when performing show/update/delete following restrictions apply :- 1. show : Only user who is admin or admin in parent or admin in root project should be able to perform show/view the quota of the leaf projects. 2. update : Only user admin in

[openstack-dev] [cinder] Nested Quota Driver and policy.json changes

Hi, While developing Nested Quota Driver for Cinder, when performing show/update/delete following restrictions apply :- 1. show : Only user who is admin or admin in parent or admin in root project should be able to perform show/view the quota of the leaf projects. 2. update : Only user admin in

Re: [openstack-dev] [nova] Service group foundations and features

Few more places which can trigger inconsistent behaviour. - https://github.com/openstack/nova/blob/stable/kilo/nova/api/openstack/compute/contrib/services.py#L44 - https://github.com/openstack/nova/blob/stable/kilo/nova/api/openstack/compute/contrib/hypervisors.py#L98 -

Re: [openstack-dev] [nova][all] Architecture Diagrams in ascii art?

+1 On Thu, May 14, 2015 at 3:52 AM, John Garbutt j...@johngarbutt.com wrote: On 12 May 2015 at 20:33, Sean Dague s...@dague.net wrote: On 05/12/2015 01:12 PM, Jeremy Stanley wrote: On 2015-05-12 10:04:11 -0700 (-0700), Clint Byrum wrote: It's a nice up side. However, as others have

Re: [openstack-dev] [Cinder] [Taskflow]Review help to cinder bp:Implement function to manage/unmanage snapshots

Hi Michal, Apart from reviewing your changes, few more efforts done from TaskFlow side that I find useful for Cinder's case (and in general). https://review.openstack.org/#/c/186524/ https://review.openstack.org/#/c/184814/ -Vilobh On Tue, Jun 2, 2015 at 2:45 AM, Dulko, Michal

[openstack-dev] [openstack] [cinder] Problems with existing Cinder Database Quota Driver

Hi All, I am working on the Nested Quota Driver for Cinder [1] and with that effort trying to clean up some of the existing quota related issues we have with Cinder. Few of the obvious ones which we saw recently is [2] where usage and reservation quota was being deleted on quota deletion. It

Re: [openstack-dev] [oslo] Adding Joshua Harlow to oslo-core

Not a core but definitely a +1 from my side. Has great technical insights and is someone who is always happy to help others. -Vilobh On Tue, May 5, 2015 at 12:55 PM, David Medberry openst...@medberry.net wrote: Not a voting member, but +1 from me. He's core in my book. On Tue, May 5, 2015 at

Re: [openstack-dev] [nova] Proposal to add Melanie Witt to nova-core

Not a core but definitely a +1. She is very helpful. On Fri, May 1, 2015 at 9:43 PM, Gary Kotton gkot...@vmware.com wrote: +1 From: Alex Xu sou...@gmail.com Reply-To: OpenStack List openstack-dev@lists.openstack.org Date: Friday, May 1, 2015 at 6:30 AM To: OpenStack List

Re: [openstack-dev] [openstack][nova] Does anyone use Zookeeper, Memcache Nova ServiceGroup Driver ?

/blog/2013/10/18/innodb-scalability-issues-tables-without-primary-keys/ - Original Message - From: Vilobh Meshram vilobhmeshram.openst...@gmail.com To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.org, OpenStack Mailing List (not for usage

[openstack-dev] [openstack][nova] Does anyone use Zookeeper, Memcache Nova ServiceGroup Driver ?

Hi, Does anyone use Zookeeper[1], Memcache[2] Nova ServiceGroup Driver ? If yes how has been your experience with it. It was noticed that most of the deployment try to use the default Database driver[3]. Any experiences with Zookeeper, Memcache driver will be helpful. -Vilobh [1]

Re: [openstack-dev] 答复: 答复: [neutron] Neutron scaling datapoints?

Hi Robin, The idea sounds good to me too. I am working on refactoring ServiceGroup code. Tooz has a nice compatibility matrix which can be found here [2] which you might find useful. -Vilobh [1] Servicegroup code refactoring : https://review.openstack.org/#/c/172502/ [2] Tooz compatibility

Re: [openstack-dev] [Keystone] Core Reviewer Update

Congrats Lin ! :) Keep up the good work. On Tue, Apr 7, 2015 at 4:07 PM, Joshua Harlow harlo...@outlook.com wrote: Congrats Lin, thanks for the hard work :-) Morgan Fainberg wrote: I am pleased to announce that Lin Hua Cheng has joined the Keystone Core Reviewer team. He has been

[openstack-dev] [CINDER] Exception request : Making Introducing micro_states for create workflow part of K-3

As discussed in Cinder Weekly meeting on 02/12 the deadline for K3 (kilo-3 k3 : Cinder https://launchpad.net/cinder/+milestone/kilo-3) is Feb28 (please correct me if I am wrong). So I have a working prototype for micro-states feature https://review.openstack.org/#/c/124205 and is been already out

[openstack-dev] [CINDER] Exception request : Making Introducing micro_states for create workflow part of K-3

Hi, As discussed in Cinder Weekly meeting on 02/12 the deadline for K3 (kilo-3 k3 : Cinder) is Feb28 (please correct me if I am wrong). So I have a working prototype for micro-states feature https://review.openstack.org/#/c/124205 and is been already out for review for quite some time now; if

Re: [openstack-dev] [Cinder] Cinder State Machine - Kilo Design Summit Talk - November 5

. Thanks,Vilobh From: Vilobh Meshram vilob...@yahoo-inc.com To: openst...@lists.openstack.org openst...@lists.openstack.org Cc: Vilobh Meshram vilob...@yahoo-inc.com Sent: Tuesday, November 4, 2014 2:55 PM Subject: [Cinder] Cinder State Machine - Kilo Design Summit Talk - November 5

[openstack-dev] Monitoring IP Availability

Hello OpenStack Dev, We wanted to have your input on how different companies/organizations, using Openstack, are monitoring IP availability as this can be useful to track the used IP’s and total number of IP’s. Please let us know your thoughts. Thanks, Vilobh