Re: [openstack-dev] Gate issues - what you can do to help

Hi, Can some Neutron cores please look at https://review.openstack.org/#/c/49943/. I have tested this locally and it addresses the issues that I have encountered. Thanks Gary >On Fri, Oct 4, 2013 at 2:06 AM, Akihiro Motoki wrote: >> Hi, >> >> I would like to share what Gary and I investigated, wh

Re: [openstack-dev] [Neutron] Tenant isolation gate failures?

https://review.openstack.org/#/c/46900/ On 10/7/13 10:36 AM, "Maru Newby" wrote: >The tenant isolation gates that have been failing so frequently seem to >be passing all of a sudden. I didn't see any merges that claimed to fix >the issue, so maybe this is just a lull due to a lower volume of g

[openstack-dev] Scheduling meeting

Hi, Ideas for an agenda: 1. Following last weeks meeting the following document was drawn up: https://docs.google.com/document/d/17OIiBoIavih-1y4zzK0oXyI66529f-7JTCVj-BcXURA/edit?usp=sharing 2. Open issues See you at the end of the hour Thanks Gary ___ O

[openstack-dev] Stable/grizzly

Hi, The gate is once again broken: 2013-10-10 05:15:05.036 | Traceback (most recent call last): 2013-10-10 05:15:05.036 | File "/home/jenkins/workspace/gate-nova-python26/nova/tests/test_api.py", line 389, in test_group_name_valid_length_security_group 2013-10-10 05:15:05.036 | self.expec

Re: [openstack-dev] Stable/grizzly

Same on trunk! From: Administrator mailto:gkot...@vmware.com>> Reply-To: OpenStack Development Mailing List mailto:openstack-dev@lists.openstack.org>> Date: Thursday, October 10, 2013 9:10 AM To: OpenStack Development Mailing List mailto:openstack-dev@lists.openstack.org>> Subject: [openstack-de

Re: [openstack-dev] Stable/grizzly

races between the parallelled unittests. 2013/10/10 Gary Kotton mailto:gkot...@vmware.com>> Hi, The gate is once again broken: 2013-10-10 05:15:05.036 | Traceback (most recent call last): 2013-10-10 05:15:05.036 | File "/home/jenkins/workspace/gate-nova-python26/nova/test

Re: [openstack-dev] [nova] Jekins failed for all nova submit due to library boto change method signature

Hi, I am dealing this with this – please see https://review.openstack.org/50904 Thanks Gary From: Chang Bo Guo mailto:guoc...@cn.ibm.com>> Reply-To: OpenStack Development Mailing List mailto:openstack-dev@lists.openstack.org>> Date: Thursday, October 10, 2013 2:15 PM To: "openstack-dev@lists.ope

Re: [openstack-dev] [Openstack-stable-maint] Stable/grizzly

updated. Maybe someone who is familiar with that can chime in. Thanks Gary On 10/10/13 12:20 PM, "Alan Pevec" wrote: >2013/10/10 Gary Kotton : >> The problem seems to be with the boto python library. I am not really >> familiar with this but I have seen this is the last

Re: [openstack-dev] [Nova] Icehouse design summit proposal deadline

FYI On 10/10/13 9:43 PM, "Russell Bryant" wrote: >Greetings, > >We already have more proposals for the Nova design summit track than >time slots. Please get your proposals in as soon as possible, and >ideally no later than 1 week from today - Thursday, October 17. At that >point we will be foc

Re: [openstack-dev] [nova] Looking for clarification on the diagnostics API

Yup, it seems to be hypervisor specific. I have added in the Vmware support following you correcting in the Vmware driver. Thanks Gary From: Matt Riedemann mailto:mrie...@us.ibm.com>> Reply-To: OpenStack Development Mailing List mailto:openstack-dev@lists.openstack.org>> Date: Thursday, October

Re: [openstack-dev] [nova] Looking for clarification on the diagnostics API

ns and OpenStack Development Phone: 1-507-253-7622 | Mobile: 1-507-990-1889 E-mail: mrie...@us.ibm.com<mailto:mrie...@us.ibm.com> [cid:_1_09B39E1009B3987C0011B74C86257C03] 3605 Hwy 52 N Rochester, MN 55901-1407 United States From:Gary Kot

Re: [openstack-dev] Scheduler meeting and Icehouse Summit

Hi, I agree with Phil. This has been on the agenda of the scheduling meetings for over a month now. Thanks Gary On 10/15/13 2:40 PM, "Day, Phil" wrote: >Hi Alex, > >My understanding is that the 17th is the deadline and that Russell needs >to be planning the sessions from that point onwards. If

Re: [openstack-dev] [Nova] VMWare Mine Sweeper, Congrats!

Kudos to Sreeram. Great work here. From: Sreeram Yerrapragada mailto:syerraprag...@vmware.com>> Reply-To: OpenStack Development Mailing List mailto:openstack-dev@lists.openstack.org>> Date: Saturday, October 19, 2013 1:29 AM To: OpenStack Development Mailing List mailto:openstack-dev@lists.open

[openstack-dev] [nova] resource tracking

Hi, I have encountered a few issues regarding the resource tracking and hopefully someone can help clarify here. From what I understand we just seem to ignore the actual used disk and memory from the hypervisor and calculate it according to the allocated instances. For example, if the hypervisor

[openstack-dev] [Nova] Stable/Havana Gate broken

Hi, The gate for stable Hanava is broken in Nova with the following error: == 2013-10-24 12:48:35.629 | F

Re: [openstack-dev] [Nova] Blueprint review process

On 10/24/13 4:46 PM, "Dan Smith" wrote: >> In the last meeting we discussed an idea that I think is worth trying at >> least for icehouse-1 to see if we like it or not. The idea is that >> *every* blueprint starts out at a Low priority, which means "best >> effort, but no promises". For a blu

Re: [openstack-dev] [Nova] Stable/Havana Gate broken

rg>> Subject: Re: [openstack-dev] [Nova] Stable/Havana Gate broken This is being tracked in bug https://bugs.launchpad.net/tempest/+bug/1244055 and a fix is working its way through the gate now (https://review.openstack.org/#/c/53699/) On Thu, Oct 24, 2013 at 2:51 PM, Gary Kotton mailto:

[openstack-dev] Stable backports

Hi, In the case of stable back ports which have "Fixes bug: #XYZ" we will have to change this to the new format "Closes-bug: #XYZ". Any thoughts on this? Thanks Gary ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.

Re: [openstack-dev] [nova][scheduler] Instance Group Model and APIs - Updated document with an example request payload

> to finding a capable hypervisor for the VM that someone would like to > boot, and then just slightly beyond. +1 [Gary Kotton] When we proposed the initial VM ensembles this was one of the option that was considered. The guys from Heat did not like this approach. I like the idea and

[openstack-dev] [nova] Closes-Bug and Launchpad

Hi, Over the last few days I have noticed that bug fixes posted to gerrit are not updated in Launchpad. Am I doing something wrong? I think that the commit message is the correct format: Closes-Bug: #. Any ideas? Thanks Gary ___ OpenStack-dev mailing li

Re: [openstack-dev] [Nova] Configuration validation

Hi, I think that John has a very valid point. My understanding from the session was that this should be a stand alone tool that will also work across services, that is, if neutron is configured then it will check that the neutron credentials are correct. Thanks Gary On 11/11/13 1:55 PM, "John Garb

Re: [openstack-dev] [qa] Policy on spelling and grammar

I am in favor/favour of the -1 with suggestions on what to change. The more input we can provide on a review the better. Thanks Gary On 11/11/13 8:21 PM, "Collins, Sean (Contractor)" wrote: >As long as the -1's include a correction that can be copied >and pasted, I think they're OK. > >I know I

[openstack-dev] [Scheduler] Meeting

Hi, I am sorry but my calendar was a mess – daylight saving changes etc. So I did not make it to the meeting. Hopefully we can pick up next week and follow up on what was discussed at the summit. So humble apologies for not running the meeting this week and see you guys next week. Thanks Gary __

Re: [openstack-dev] [ALL] Removing generate_uuid() from uuidutils

I recall a few cycles ago having str(uuid.uuid4()) replaced by generate_uuid(). There was actually a helper function in neutron (back when it was called quantum) and it was replaced. So now we are going back… I am not in favor of this change. From: Zhongyue Luo mailto:zhongyue@intel.com>> Re

Re: [openstack-dev] Problems with devstack installation

Please delete the file - /usr/bin/nova-rootwrap (this code was updated to use the openstack common root wrap code). I also hit the same issue yesterday Thanks Gary From: , Jon Paul mailto:jonpaul.sulli...@hp.com>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" mailto:o

[openstack-dev] [stable/havana] gate broken

Hi, The gating for the stable version is broken when the running the neutron gate. Locally this works but the gate has problem. All of the services are up and running correctly. There are some exceptions with the ceilometer service but that is not related to the neutron gating. The error messag

Re: [openstack-dev] [stable/havana] gate broken

Thanks. Looks like something fishy with tempest. When I just run neutron everything is well and fine. On 11/17/13 5:50 PM, "Matt Riedemann" wrote: > > >On Sunday, November 17, 2013 7:46:39 AM, Gary Kotton wrote: >> Hi, >> The gating for the stable version

Re: [openstack-dev] [stable/havana] gate broken

Thanks for dealing with this! On 11/17/13 10:45 PM, "Sean Dague" wrote: >Clark, > >Thanks for tracking that down, just pushed those changes to the gate. > >On Sun, Nov 17, 2013 at 3:03 PM, Clark Boylan >wrote: >> On Sun, Nov 17, 2013 at 7:53 AM, Gary Kot

Re: [openstack-dev] Migrating plugins from Nova to Quantum

On 06/19/2013 09:39 PM, Abhishek Chanda wrote: Hi all, Is there an official guide to migrate nova network plugins to quantum plugins (or rather, neutron plugins)? Hi, Sadly we have not made much progress with this. There are a number of issues to consider when moving from traditional nova ne

Re: [openstack-dev] [Networking] Question on portbinding

On 06/25/2013 07:59 AM, Chandan Dutta Chowdhury wrote: Hello All, While going through the portbinding extension I noticed that a patch has been proposed for calls from nova to checks and updates the port binding attributes for a plugin which supports this extension. https://review.openstack.

Re: [openstack-dev] [oslo] Sample config file location inconsistency

On 06/25/2013 06:03 AM, Zhongyue Luo wrote: Hi team I'm currently trying to move the generate_sample.sh script in nova to oslo. Before pushing the patch to gerrit, I wanted to give the output directory a default value if it was not stated so I was wondering where projects put their sample c

Re: [openstack-dev] Nova scheduler sub-group meeting agenda 6/25

On 06/25/2013 04:54 AM, Dugger, Donald D wrote: 1) Follow ups on the scheduler BPs 2) Opens? Not really much on the agenda for this week, we'll probably have a short meeting (I'm still studying the scheduler's use of fan-out messages and the DB, I'll want to go over that in more detail once

[openstack-dev] [OSLO] Current DB status

Hi, Can someone please clarify what the DB status is in OSLO. Last week the code was imported to Neutron (aka Quantum). The review process is Nova has been -1'ed due to issues with the common code (https://review.openstack.org/#/c/34671/). What is the current status? Does the code need to be re

Re: [openstack-dev] [OSLO] Current DB status

On 07/01/2013 06:13 PM, Mark McLoughlin wrote: (Oslo is not an acronym) ok. can someone please clarify what the database status is in Oslo? On Mon, 2013-07-01 at 18:07 +0300, Gary Kotton wrote: Hi, Can someone please clarify what the DB status is in OSLO. Last wee

Re: [openstack-dev] [OSLO] Current DB status

On 07/01/2013 06:49 PM, Mark McLoughlin wrote: On Mon, 2013-07-01 at 18:32 +0300, Gary Kotton wrote: On 07/01/2013 06:13 PM, Mark McLoughlin wrote: (Oslo is not an acronym) ok. can someone please clarify what the database status is in Oslo? What apart from the oslo.config issue do you want

Re: [openstack-dev] [OSLO] Current DB status

On 07/01/2013 07:07 PM, Mark McLoughlin wrote: On Mon, 2013-07-01 at 18:59 +0300, Gary Kotton wrote: On 07/01/2013 06:49 PM, Mark McLoughlin wrote: On Mon, 2013-07-01 at 18:32 +0300, Gary Kotton wrote: On 07/01/2013 06:13 PM, Mark McLoughlin wrote: (Oslo is not an acronym) ok. can someone

Re: [openstack-dev] [OSLO] Current DB status

On 07/01/2013 07:35 PM, Mark McLoughlin wrote: On Mon, 2013-07-01 at 19:33 +0300, Gary Kotton wrote: On 07/01/2013 07:07 PM, Mark McLoughlin wrote: On Mon, 2013-07-01 at 18:59 +0300, Gary Kotton wrote: On 07/01/2013 06:49 PM, Mark McLoughlin wrote: On Mon, 2013-07-01 at 18:32 +0300, Gary

[openstack-dev] [nova] generate_sample.sh

Hi, I have run into a problem with pep8 for https://review.openstack.org/#/c/37539/. The issue is that have run the script in the subject and the pep8 fails. Any ideas? Thanks Gary ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://

Re: [openstack-dev] [Neutron] Proposal to add new neutron-core members

A big +2 for both! They have been doing a great job as of late. -Original Message- From: Mark McClain [mailto:mark.mccl...@dreamhost.com] Sent: Tuesday, July 23, 2013 10:15 PM To: OpenStack Development Mailing List Subject: [openstack-dev] [Neutron] Proposal to add new neutron-core member

[openstack-dev] [nova] generate_sample.sh

Hi, Over the last few days I have been battling with this script (I am only human). Recently there was a nice change that removed the number of entries which helps with the merges. One thing that I have encountered over the last 2 days is that the pep8 passes with my environment and fails with t

[openstack-dev] [Nova] Random gate failures

Hi, Since the addition of https://review.openstack.org/#/c/32966/ there have been a number of failures with unit tests (sadly this is not consistent) but examples are: https://review.openstack.org/#/c/35189/ https://review.openstack.org/#/c/33504/ I have managed to reproduce this on a local setup

[openstack-dev] [Nova][Ceilometer] blueprint utilization-aware-scheduling

Hi, >From reviewing the patches for >https://blueprints.launchpad.net/nova/+spec/utilization-aware-scheduling it >seems like there is a lot of code here that may already existing the >Ceilometer. I wonder if this is something that should be implemented in Nova >or if Nova should receive the inf

Re: [openstack-dev] Scheduler sub-group meeting agenda 7/30

Hi, Would it be possible that we also discuss the instance groups. This was blocked because the new API did not support objects. The relevant patches for objects have been added and it is pending review. Thanks Gary -Original Message- From: Dugger, Donald D [mailto:donald.d.dug...@intel.

Re: [openstack-dev] [Nova][Ceilometer] blueprint utilization-aware-scheduling

es on other components) but we should look into scheduler/ceilometers integration for the future (good session topic for the Icehouse summit). -- Don Dugger "Censeo Toto nos in Kansa esse decisse." - D. Gale Ph: 303/443-3786 From: Gary Kotton [mailto:gkot...@vmware.com] Sent: Tuesday, Jul

[openstack-dev] [Nova] RPC versionsing and backports

Hi, I have a question regarding the RPC versioning and backports. More specifically a patch was added upstream to fix a bug. This required a new RPC version. If this patch is to be backported to stable/grizzly, what is required treatment for the RPC versions. Please see https://review.openstack.

Re: [openstack-dev] [Nova] RPC versionsing and backports

2013, at 6:17 AM, Gary Kotton mailto:gkot...@vmware.com>> wrote: Hi, I have a question regarding the RPC versioning and backports. More specifically a patch was added upstream to fix a bug. This required a new RPC version. If this patch is to be backported to stable/grizzly, what is re

Re: [openstack-dev] [Nova] Proposal to add Nikola Đipanov to nova-core

+1 -Original Message- From: Sean Dague [mailto:s...@dague.net] Sent: Thursday, August 01, 2013 1:51 PM To: OpenStack Development Mailing List Subject: Re: [openstack-dev] [Nova] Proposal to add Nikola Đipanov to nova-core On 07/31/2013 03:10 PM, Russell Bryant wrote: > Greetings, > > I p

[openstack-dev] [Nova] Monitoring plugin file names

Hi, As part of the BP blueprint utilization-aware-scheduling a plugin has been added. I have an issue with the placement of the drivers (the code is looking good:)) and would like to know what the community thin

Re: [openstack-dev] [Nova] Monitoring plugin file names

driver. [Gary Kotton] This works for me :) By the way, can nova core or those who are interested in the bp review our patch sets at https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/ubs,n,z? Thanks. -- Shane From: Gary Kotton [mailto:gkot...@vmware.com

[openstack-dev] [Nova] Blueprint approval

Hi, Would it be possible to get approval for the following blueprint - https://blueprints.launchpad.net/openstack/?searchtext=vmware-nova-cinder-support A WIP review has been posted. Today I am going to add in the unit tests so hopefully this will be ready for review by the end of the day. Thanks

Re: [openstack-dev] [Nova] Blueprint approval

Thank you! -Original Message- From: Russell Bryant [mailto:rbry...@redhat.com] Sent: Tuesday, August 06, 2013 6:30 PM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [Nova] Blueprint approval On 08/06/2013 02:25 AM, Gary Kotton wrote: > Hi, > > Would it be

[openstack-dev] [Nova] Review requests

Hi, At the moment we have some blocking bugs with the VMware drivers. Would it be possible to get some reviews for this: https://review.openstack.org/#/c/39046/ - tempest tests fail with rescue/unrescue https://review.openstack.org/#/c/40105/ - attempting to attach/detach a volume causes an exce

Re: [openstack-dev] a blueprint and bugs needing attention

27;re becoming problems). This blueprint is not accepted... but the associated patch is merged already! Can we just get the paperwork on this one caught up? * https://blueprints.launchpad.net/nova/+spec/vmware-configuration-section ** https://review.openstack.org/#/c/37539/ [Gary Kotton] The BP has

[openstack-dev] [Neutron] Ceilometer support

[cid:image001.jpg@01CE98FD.2A08F120] <>___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Proposal oslo.db lib

Hi, I have a number of things to say here: 1. Great work in getting the DB into the common and ironing out the issues 2. As far as I know only Neutron and Nova are making use of the common DB code. Neutron has been using this since the beginning of H2 (this did not resolve all of th

Re: [openstack-dev] Proposal oslo.db lib

) So are you agree with next points? 1) In Havana focus on migrating in all projects to oslo.db code [Gary Kotton] It is worth going for. 2) in IceHouse create and move to oslo.db lib [Gary Kotton] I am in favor of this pending the stability of the oslo db code (which is on the right track) An

Re: [openstack-dev] VMwareAPI sub-team status update 2013-08-19

Hi, You have omitted the following which are very critical for our tempest runs: 1. https://review.openstack.org/#/c/39046/ (VMware: fix rescue/unrescue instance) 2. https://review.openstack.org/#/c/41058/ (VMware: Add driver support for hypervisor uptime) 3. [Included below] https://review.opens

Re: [openstack-dev] [Nova] Proposal to revert per-user-quotas

viable approach, I prefer that we attempt to fix the code in tree. We attempted to get this code in grizzly and had to revert. I'd hate to go through the cycle again in I if we can fix it now. [Gary Kotton] I too prefer this approach. Vish 2013/8/20 Andrew Laski mailto:andrew.la...@rackspac

Re: [openstack-dev] Code review study

started to enforce that here: > >>> > >>> https://review.openstack.org/41695 > >>> > >>> and the exact example I mentioned above :) > >>> > >>> We should not enforce rules like this blindly. > >> > >> Agreed, l

Re: [openstack-dev] [Nova] Requesting feedback on review 35759

the patches for bp > https://blueprints.launchpad.net/nova/+spec/utilization-aware-scheduling > 1+ month ago. > The first patch is to add a column to save metrics collected by plugins - > https://review.openstack.org/#/c/35759/. > Is there anyone who is interested in that, would it be possib

Re: [openstack-dev] [Nova] Requesting feedback on review 35759

frustration but still have passion:) [Gary Kotton] Cool. Nice to hear. > > -- > Shane > > > -----Original Message- > > From: Gary Kotton [mailto:gkot...@vmware.com] > > Sent: Tuesday, August 27, 2013 3:36 PM > > To: OpenStack Development Mailing List >

[openstack-dev] [Nova] Scheduler support for PCI passthrough

Hi, Whilst reviewing the code I think that I have stumbled on an issue (I hope that I am mistaken). The change set (https://review.openstack.org/#/c/35749/) expects pci stats to be returned from the host. There are a number of issues here that I have concern with an would like to know what the p

Re: [openstack-dev] [Nova] Frustrations with review wait times

Hi, I am not sure that there is a good solution. I guess that we all need to 'vasbyt' (that is Afrikaans for bite the bullet) and wait for the code posted to be reviewed. In Neutron when we were heading towards the end of a cycle and there were a ton of BP's being added the PTL would ensure that

[openstack-dev] Review request

Hi, Would it be possible for a core reviewer to please look at https://review.openstack.org/#/c/40105/. Thanks Gary ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [nova] sample configuration file

Hi, Whilst reviewing the olso messaging (my poor browser with all of the open tabs) it has come to my attention that the nova sample configuration file no longer has the RPC message configuration values. The common CFG values are also no longer in the file. I think that this is a bug and would l

Re: [openstack-dev] Confused about GroupAntiAffinityFilter and GroupAffinityFilter

Hi, Hopefully I will be able to address your questions. First lets start with the group anti-affinity. This was added towards the end of the Grizzly release cycle as a scheduling hint. At the last summit we sat and agreed on a more formal approach to deal with this and we proposed and developed htt

[openstack-dev] [nova] rebased after approval

Hi, The following patch was approved but failed as it required a rebase - https://review.openstack.org/#/c/41058/. Would it be possible that a core reviewer takes a look. Thanks in advance Gary ___ OpenStack-dev mailing list OpenStack-dev@lists.openstac

Re: [openstack-dev] Confused about GroupAntiAffinityFilter and GroupAffinityFilter

>>> >>>+--+-++- >>>---+-+--+ >>> >>> >>> >>> I've pasted the scheduler logs [1] and my nova.conf file [2]. As you >>> will s

Re: [openstack-dev] [Nova] FFE Request: bp/instance-group-api-extension

On 9/6/13 5:07 PM, "Russell Bryant" wrote: >On 09/06/2013 05:06 AM, Thierry Carrez wrote: >> Debojyoti Dutta wrote: >>> As per my IRC chats with dansmith, russellb, this feature needs the >>> user auth checks (being taken care of in >>> https://bugs.launchpad.net/nova/+bug/1221396). >>> >>> Dan

Re: [openstack-dev] [Nova] FFE Request: bp/instance-group-api-extension

of resource allocation, >scheduling, policies etc. Hence a little sad. > >Hopefully we will have better luck next time :) Thanks to all the >reviewers esp Chris Yeoh, Dan Smith, Alex Xu and Russell Bryant for >their time. Thanks Thierry for trying to help with the FFE! > >d

Re: [openstack-dev] Confused about GroupAntiAffinityFilter and GroupAffinityFilter

. The scheduling after a failed attempt would not invoke the anti affinity scheduling, which may lead to an invalid host being selected. I am going to post a patch soon. Thanks Gary On 9/6/13 3:18 PM, "Gary Kotton" wrote: >Hi, >Sorry for the delayed response (it is new years my s

[openstack-dev] Scheduler sub-group meeting on 9/10

Hi, Don is on vacation. Lets try and have the meeting today. Topics that come to mind: 1. https://etherpad.openstack.org/IceHouse-Nova-Scheduler-Sessions 2. Scheduling BP's that missed H. Bad timing or do we need to discuss and see how we can improve the process 3. Open issues Thanks Gary

Re: [openstack-dev] [Neutron] New Plug-in development for Neutron

Hi, Anyone can submit a new plugin :). The proposed code will go through the regular review process. It is best to open a blueprint for the proposed plugin (https://launchpad.net/neutron). At the moment we are in a feature freeze for the H cycle. So the chances of it getting in now are pretty sl

[openstack-dev] Scheduling Meeting Minutes

Hi, The meeting minutes can be found below. Thanks Gary Minutes: http://eavesdrop.openstack.org/meetings/scheduling/2013/scheduling.2013-09-10-15.04.html Minutes (text): http://eavesdrop.openstack.org/meetings/scheduling/2013/scheduling.2013-09-10-15.04.txt Log: http://eavesdr

Re: [openstack-dev] [heat] Comments/questions on the instance-group-api-extension blueprint

enstack-dev] [heat] Comments/questions on the instance-group-api-extension blueprint First, I'm a newbie here, wondering: is this the right place for comments/questions on blueprints? Supposing it is... [Gary Kotton] Yeah, as Russel said this is the correct place I

Re: [openstack-dev] [Neutron] Neutron Social Meetup in Tokyo

+1 From: Kevin Benton mailto:blak...@gmail.com>> Reply-To: OpenStack List mailto:openstack-dev@lists.openstack.org>> Date: Saturday, October 24, 2015 at 6:38 AM To: OpenStack List mailto:openstack-dev@lists.openstack.org>> Subject: Re: [openstack-dev] [Neutron] Neutron Social Meetup in Tokyo Ho

Re: [openstack-dev] How we can find list of medium/low bugs for nova

Hi, In general the process is as follows: 1. Fix the bug in the trunk/master branch 2. If the bug meets stable back port criteria (https://wiki.openstack.org/wiki/StableBranch), and it is approved in trunk, then do a cherry pick Thanks Gary From: chandraprakash mishra mailto:cpmishra...

[openstack-dev] [Neutron][Infra] Neutron gate issues

Hi, At the moment the neutron gate is broken due to LBaaSv1 issues. This is meant to be deprecated in favor of LBaaSV2 (https://review.openstack.org/#/c/239863). Is there any chance that we can get that approved? Thanks Gary _

Re: [openstack-dev] [neutron][stable] should we open gate for per sub-project stable-maint teams?

From: "mest...@mestery.com" mailto:mest...@mestery.com>> Reply-To: OpenStack List mailto:openstack-dev@lists.openstack.org>> Date: Tuesday, November 3, 2015 at 7:09 PM To: OpenStack List mailto:openstack-dev@lists.openstack.org>> Subject: Re: [openstack-dev] [neutro

Re: [openstack-dev] [Neutron] Mid-cycle meetup for Mitaka

Hi, In Nova the new black is the os-vif-lib (https://etherpad.openstack.org/p/mitaka-nova-os-vif-lib). It may be worthwhile seeing if we can maybe do something at the same time with the nova crew and then bash out the dirty details here. It would be far easier if everyone was in the same room.

Re: [openstack-dev] [nova] Proposal to add Alex Xu to nova-core

+1. Well deserved! On 11/8/15, 7:28 AM, "GHANSHYAM MANN" wrote: >I am not core but Big +1 for Alex. It will be great to have him in nova core. > >Thanks >ghanshyam > >On Sat, Nov 7, 2015 at 12:32 AM, John Garbutt wrote: >> Hi, >> >> I propose we add Alex Xu[1] to nova-core. >> >> Over the la

Re: [openstack-dev] [Neutron][IPAM] Arbitrary JSON blobs in ipam db tables

I think that id we can move to a versioned object model model then it will be better. Having random json blobs passed around is going to cause problems. From: "Armando M." mailto:arma...@gmail.com>> Reply-To: OpenStack List mailto:openstack-dev@lists.openstack.org>> Date: Wednesday, November 4,

Re: [openstack-dev] [Neutron][IPAM] ML2 don't call ipam driver remove_subnet function

Hi, This should be resolved with this path - https://review.openstack.org/239885 Good luck Gary From: thanh le giang mailto:legiangth...@gmail.com>> Reply-To: OpenStack List mailto:openstack-dev@lists.openstack.org>> Date: Wednesday, November 11, 2015 at 5:20 AM To: OpenStack List mailto:opensta

Re: [openstack-dev] [stable] Preparing 2014.2.4 (Juno) WAS Re: [Openstack-operators] [stable][all] Keeping Juno "alive" for longer.

On 11/13/15, 3:23 PM, "Flavio Percoco" wrote: >On 10/11/15 16:11 +0100, Alan Pevec wrote: >>Hi, >> >>while we continue discussion about the future of stable branches in >>general and stable/juno in particular, I'd like to execute the current >>plan which was[1] >> >>2014.2.4 (eol) early Novembe

Re: [openstack-dev] Last sync from oslo-incubator

On 11/13/15, 8:04 PM, "Doug Hellmann" wrote: >Excerpts from Davanum Srinivas (dims)'s message of 2015-11-13 07:44:26 -0500: >> Hear Hear! Thierry. Many many thanks to everyone who made this possible. >> >> -- Dims > >Indeed, as Thierry said, it has truly been a group effort, spanning >many

[openstack-dev] [Neutron] Bug update

Hi, There are a ton of old and ancient bugs that have not been trained. If you guys have some time then please go over them. In most cases some are not even bugs and are just questions. I have spent the last few days going over and training a few. Over the last two days a number of bugs related

Re: [openstack-dev] [Neutron] Bug update

nd what are new features etc. Just a thought. Thanks Gary From: Gary Kotton mailto:gkot...@vmware.com>> Reply-To: OpenStack List mailto:openstack-dev@lists.openstack.org>> Date: Friday, November 20, 2015 at 9:10 AM To: OpenStack List mailto:openstack-dev@lists.openstack.org>>

Re: [openstack-dev] [Neutron] Bug update

= triaging brace = rbac ah! On Nov 20, 2015, at 12:41 PM, Armando M. mailto:arma...@gmail.com>> wrote: On 19 November 2015 at 23:10, Gary Kotton mailto:gkot...@vmware.com>> wrote: Hi, There are a ton of old and ancient bugs that have not been trained. If you guys have some tim

Re: [openstack-dev] [neutron][neutron-*] Notice! pylint breakage

Should we not be updating this in the requirements project? From: Paul Michali mailto:p...@michali.net>> Reply-To: OpenStack List mailto:openstack-dev@lists.openstack.org>> Date: Tuesday, December 1, 2015 at 4:50 PM To: OpenStack List mailto:openstack-dev@lists.openstack.org>> Subject: Re: [open

Re: [openstack-dev] [Neutron] Bug deputy process

From: "Armando M." mailto:arma...@gmail.com>> Reply-To: OpenStack List mailto:openstack-dev@lists.openstack.org>> Date: Saturday, December 5, 2015 at 1:27 AM To: OpenStack List mailto:openstack-dev@lists.openstack.org>> Subject: Re: [openstack-dev] [Neutron] Bug deputy process On 4 December

Re: [openstack-dev] [Neutron] Team meeting this Monday at 2100 UTC

Nice suggestion! From: "Armando M." mailto:arma...@gmail.com>> Reply-To: OpenStack List mailto:openstack-dev@lists.openstack.org>> Date: Friday, December 4, 2015 at 10:50 PM To: OpenStack List mailto:openstack-dev@lists.openstack.org>> Subject: [openstack-dev] [Neutron] Team meeting this Monday

[openstack-dev] [devstack] Neutron plugins that do not run q-l3 fail tempest

Hi, A recent change in devstack https://review.openstack.org/#q,d894221457efa3a2a0bf3db76a4c5e8ffba36e29,n,z has broken plugins that do not run l3 agents. I have reverted the patch https://review.openstack.org/#/c/316690/. Thanks Gary __

Re: [openstack-dev] [devstack] Neutron plugins that do not run q-l3 fail tempest

Correct - https://review.openstack.org/#/c/316660 - addresses the issue (this was posted first) From: Gary Kotton Reply-To: OpenStack List Date: Monday, May 16, 2016 at 1:00 PM To: OpenStack List Subject: [openstack-dev] [devstack] Neutron plugins that do not run q-l3 fail tempest Hi, A

Re: [openstack-dev] [neutron][devstack] Third party CI breakage around Q_L3_ENABLED

I disagree. Sadly I approved the patch and it breaks all of the plugins that have L3 support but do not require an agent. Would it be possible that we unblock all of the plugins and try and work towards a better solution. The OVN example is good but that have a very small subset of tests. Thanks Ga

Re: [openstack-dev] [neutron][devstack] Third party CI breakage around Q_L3_ENABLED

Hi, Actually the breakage is not sue to Q_L3_ENABLED. It is due to https://review.openstack.org/#q,d894221457efa3a2a0bf3db76a4c5e8ffba36e29,n, z The Q_L3_ENABLED is something that each CI can configure depending on what their supported mode is. Until now this mean that L3 was supported by the plugi

Re: [openstack-dev] [neutron][devstack] Third party CI breakage around Q_L3_ENABLED

Hi, This is even more motivation for us to revert the patch. Please consider this. Thanks Gary On 5/16/16, 6:23 PM, "Sean M. Collins" wrote: >Gary Kotton wrote: >> Hi, >> Actually the breakage is not sue to Q_L3_ENABLED. It is due to >> &g

Re: [openstack-dev] [neutron][stable] proposing Brian Haley for neutron-stable-maint

+1 On 5/17/16, 2:56 PM, "Henry Gessau" wrote: >+1 for Brian. (And retroactive +1 for Cedric.) > >Ihar Hrachyshka wrote: >> Hi stable-maint-core and all, >> >> I would like to propose Brian for neutron specific stable team. >> >> His stats for neutron stable branches are (last 120 days): >> >

[openstack-dev] [Neutron] Neutron plugins that do not have L3 agents

Hi, The patch [i] broke all of the Neutron plugins that do not run L3 agents. This was due to the fact that some different plugins expected different values for the Q_L3_ENABLED.The revert for that patch has been blocked [ii]. In order to get out of this pickle we have proposed the following: 1

Re: [openstack-dev] [neutron] DHCP Agent Scheduling for Segments

Today the DHCP schedulers have support for ‘AZ hints’. My understanding is that a segment is a subset of an AZ. So why are we not able to leverage that logic or make it more generic? Thanks Gary On 5/22/16, 4:02 AM, "Carl Baldwin" wrote: >On Fri, May 20, 2016 at 1:44 PM, Brandon Logan > wrote:

Re: [openstack-dev] [neutron][ovo] NeutronDbObject concurrency issues

Hi, We have used tooz to enable concurrency. Zookeeper and Redis worked well. I think that it is certainly something that we need to consider. The challenge becomes a deployment. Thanks Gary From: Damon Wang Reply-To: OpenStack List Date: Tuesday, May 24, 2016 at 5:58 AM To: OpenStack List Su

<    1   2   3   4   5   6   7   >