Re: [openstack-dev] [Neutron]{l2-gateway] is this project alive

2016-01-12 Thread Armando M.
On 12 January 2016 at 09:21, Gary Kotton wrote: > Here is an example of a patch that was posted 5 weeks ago. - > https://review.openstack.org/#/c/254816/ > That is a pretty long time for something that is trivial > 5 weeks is bad but not the end of the world. We all have

Re: [openstack-dev] [Neutron]{l2-gateway] is this project alive

2016-01-12 Thread Armando M.
On 12 January 2016 at 06:14, Gary Kotton wrote: > Its like a desert out here trying to get a review… > There was a patch that was meant to unwedge a few things. I wouldn't say it's a desert, things are still slow after the holidays. > >

Re: [openstack-dev] [Neutron] Team meeting on Tuesday 1400UTC

2016-01-11 Thread Armando M.
define it. :) > > > > > > On Jan 11, 2016, at 11:00 AM, Kyle Mestery <mest...@mestery.com> wrote: > > > > On Mon, Jan 11, 2016 at 12:57 PM, Kyle Mestery <mest...@mestery.com> > wrote: > >> > >> On Mon, Jan 11, 2016 a

Re: [openstack-dev] [Neutron] Elevating context to remove subnets created by admin

2016-06-03 Thread Armando M.
On 3 June 2016 at 13:31, Carl Baldwin wrote: > On Fri, Jun 3, 2016 at 2:26 PM, Henry Gessau wrote: > > Darek Smigiel wrote: > >> strange, that owner is not able to just get rid of *his* network and > subnets. > > > > But not all

Re: [openstack-dev] [Neutron] Getting project version from API

2016-06-06 Thread Armando M.
On 6 June 2016 at 10:06, Oleg Bondarev wrote: > Hi, > > There are cases where it would be useful to know the version of Neutron > (or any other project) from API, like during upgrades or in cross-project > communication cases. > For example in

Re: [openstack-dev] [neutron][devstack] Does the openvswitch-agent need to be run along side the neutron-l3-agent?

2016-06-06 Thread Armando M.
On 6 June 2016 at 19:59, Sean M. Collins wrote: > While reviewing https://review.openstack.org/#/c/292778/5 I think I > might have found a bit of coupling between the neutron l2 agent and the > l3 agent when it comes to DevStack. > > In the DevStack neutron guide - the

Re: [openstack-dev] [Neutron] Getting project version from API

2016-06-06 Thread Armando M.
On 6 June 2016 at 17:05, Andreas Scheuring wrote: > Is there a chance to get rid of this vif-plugged event at all? E.g. by > transitioning it to an ReST API interface? As far as I know this is the > only RPC interface between neutron and nova. > This handshake

Re: [openstack-dev] [Neutron] support of NSH in networking-SFC

2016-05-25 Thread Armando M.
On 24 May 2016 at 22:07, Elzur, Uri <uri.el...@intel.com> wrote: > Hi Armando > > > > Pls see below [UE] > > > > Thx > > > > Uri (“Oo-Ree”) > > C: 949-378-7568 > > > > *From:* Armando M. [mailto:arma...@gmail.com] > *Sent:* Frida

Re: [openstack-dev] [Neutron] support of NSH in networking-SFC

2016-05-25 Thread Armando M.
fic. Thoughts? > Tim Rozet > Red Hat SDN Team > > - Original Message - > From: "Armando M." <arma...@gmail.com> > To: "OpenStack Development Mailing List (not for usage questions)" < > openstack-dev@lists.openstack.org> > Cc: "Tim R

Re: [openstack-dev] [Neutron] support of NSH in networking-SFC

2016-05-25 Thread Armando M.
> > Thx > > > > Uri (“Oo-Ree”) > > C: 949-378-7568 > > > > *From:* Armando M. [mailto:arma...@gmail.com] > *Sent:* Wednesday, May 25, 2016 9:33 AM > *To:* OpenStack Development Mailing List (not for usage questions) < > openstack-dev@lists.openstack.org>

Re: [openstack-dev] [Neutron] support of NSH in networking-SFC

2016-05-25 Thread Armando M.
ovs-dev list [1] rather > than the openstack-dev list? I'm sure the OVS devs would be happy to > continue a discussion about the possibility of using VXLAN+NSH over GENEVE > there. > > [1] http://mail.openvswitch.org/mailman/listinfo/dev > > > > > > > Thx > > > > >

Re: [openstack-dev] [neutron][ovs] The way we deal with MTU

2016-06-14 Thread Armando M.
On 13 June 2016 at 22:22, Terry Wilson wrote: > > So basically, as long as we try to plug ports with different MTUs into > the same bridge, we are utilizing a bug in Open vSwitch, that may break us > any time. > > > > I guess our alternatives are: > > - either redesign bridge

Re: [openstack-dev] [Neutron][os-vif] Expanding vif capability for wiring trunk ports

2016-06-13 Thread Armando M.
On 13 June 2016 at 10:35, Daniel P. Berrange wrote: > On Thu, Jun 09, 2016 at 05:31:13PM -0600, Carl Baldwin wrote: > > Hi, > > > > You may or may not be aware of the vlan-aware-vms effort [1] in > > Neutron. If not, there is a spec and a fair number of patches in > >

Re: [openstack-dev] [Neutron][os-vif] Expanding vif capability for wiring trunk ports

2016-06-13 Thread Armando M.
On 13 June 2016 at 14:11, Daniel P. Berrange <berra...@redhat.com> wrote: > On Mon, Jun 13, 2016 at 02:08:30PM +0200, Armando M. wrote: > > On 13 June 2016 at 10:35, Daniel P. Berrange <berra...@redhat.com> > wrote: > > > > > On Thu, Jun 09, 2016

Re: [openstack-dev] [Neutron][Release] Changing release model for *-aas services

2016-05-31 Thread Armando M.
On 31 May 2016 at 11:17, Ihar Hrachyshka <ihrac...@redhat.com> wrote: > > > On 31 May 2016, at 20:12, Armando M. <arma...@gmail.com> wrote: > > > > Hi folks, > > > > Having looked at the recent commit volume that has been going into the > *-aas re

[openstack-dev] [Neutron][Release] Changing release model for *-aas services

2016-05-31 Thread Armando M.
Hi folks, Having looked at the recent commit volume that has been going into the *-aas repos, I am considering changing the release model for neutron-vpnaas, neutron-fwaas, neutron-lbaas from release:cycle-with-milestones [1] to release:cycle-with-intermediary [2]. This change will allow us to

[openstack-dev] [Neutron] Team meeting - cancelled

2016-05-27 Thread Armando M.
Neutrinos, Because of holidays in US/UK, it's probably safer to cancel the meeting for the week starting Monday 30th. We are approaching N-1, and we'll cut the release sometime next week. Please be aware of release deadlines [1], if you have cross-project items you are working on. Cheers,

[openstack-dev] [Neutron] Stadium Evolution - next steps

2016-05-27 Thread Armando M.
Hi Neutrinos, I wanted to give an update on [1]. Based on the feedback received so far I think it is time to get on the next stage of this transition and execute on some of the things identified in the proposal, as well as provide more detailed information to some of the folks involved in the

Re: [openstack-dev] [Neutron][Release] Changing release model for *-aas services

2016-06-01 Thread Armando M.
On 1 June 2016 at 02:28, Thierry Carrez <thie...@openstack.org> wrote: > Armando M. wrote: > >> Having looked at the recent commit volume that has been going into the >> *-aas repos, I am considering changing the release model for >> neutron-vpnaas, neutro

Re: [openstack-dev] [Neutron][os-vif] Expanding vif capability for wiring trunk ports

2016-06-16 Thread Armando M.
On 16 June 2016 at 03:33, Matt Riedemann wrote: > On 6/13/2016 3:35 AM, Daniel P. Berrange wrote: > >> On Thu, Jun 09, 2016 at 05:31:13PM -0600, Carl Baldwin wrote: >> >>> Hi, >>> >>> You may or may not be aware of the vlan-aware-vms effort [1] in >>> Neutron. If

[openstack-dev] [Neutron] Intermittent failures on unit tests

2016-06-21 Thread Armando M.
Neutrinos, There's been a number of intermittent failures induced by the DNS integration code that popped up lately. One has been reported in [1], another showed up in [2]. I am in the progress of digging deeper to see what's going on, but if someone knows or working on the issue, please let us

[openstack-dev] [Neutron] Deprecation and release notes

2016-06-21 Thread Armando M.
Hi Neutrinos, I would like to remind you to be extra careful when handling the deprecation of config options. Do not forget to associate release notes when appropriate, or even bug reports tagged with 'deprecation' to track the deprecation cycle. Alerting operators/deployers/packagers of

Re: [openstack-dev] [Neutron] Intermittent failures on unit tests

2016-06-21 Thread Armando M.
On 21 June 2016 at 08:41, Armando M. <arma...@gmail.com> wrote: > Neutrinos, > > There's been a number of intermittent failures induced by the DNS > integration code that popped up lately. One has been reported in [1], > another showed up in [2]. I am in the progress of

Re: [openstack-dev] [Neutron] Elevating context to remove subnets created by admin

2016-06-21 Thread Armando M.
On 20 June 2016 at 18:41, Carl Baldwin wrote: > Somehow, this thread hid from me for a couple of weeks. I just > reviewed something relevant to this here [1]. It proposes adding > tenant id to segment. But, it also enforces that tenant id is the > same as that of the

Re: [openstack-dev] [Neutron][os-vif] Expanding vif capability for wiring trunk ports

2016-06-15 Thread Armando M.
On 16 June 2016 at 00:31, Carl Baldwin wrote: > I know I've been pretty quiet since I started this thread. Y'all have > been doing so well, I've just been reading the thread every day and > enjoying it. I thought I'd top post here to kind of summarize. > > I see wisdom in

Re: [openstack-dev] [Neutron][os-vif] Expanding vif capability for wiring trunk ports

2016-06-15 Thread Armando M.
On 16 June 2016 at 03:33, Matt Riedemann wrote: > On 6/13/2016 3:35 AM, Daniel P. Berrange wrote: > >> On Thu, Jun 09, 2016 at 05:31:13PM -0600, Carl Baldwin wrote: >> >>> Hi, >>> >>> You may or may not be aware of the vlan-aware-vms effort [1] in >>> Neutron. If

[openstack-dev] [Neutron] Team meeting on Tuesday 1400UTC

2016-01-11 Thread Armando M.
Hi neutrinos, A kind reminder for tomorrow's meeting at 1400UTC. Cheers, Armando [1] https://wiki.openstack.org/wiki/Network/Meetings __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [Neutron] Team meeting on Tuesday 1400UTC

2016-01-11 Thread Armando M.
Disregard the email subject. I stand corrected. Let's meet today. On 11 January 2016 at 10:24, Ihar Hrachyshka <ihrac...@redhat.com> wrote: > Armando M. <arma...@gmail.com> wrote: > > Hi neutrinos, >> >> A kind reminder for tomorrow's meeting at 1400UTC. >>

Re: [openstack-dev] Further closing the holes that let gate breakage happen

2016-01-13 Thread Armando M.
On 13 January 2016 at 11:24, Carl Baldwin wrote: > Hi, > > I was looking at the most recent gate breakage in Neutron [1], fixed > by [2]. This gate breakage was held off for some time by the > upper-constraints.txt file. This is great progress and I applaud it. > I'll

[openstack-dev] [Neutron] Team meeting on Monday at 2100UTC

2016-01-15 Thread Armando M.
Hi folks, A reminder of next week meeting. Let's see if we manage to have the first one of the year! Word of notice: Monday is a public holiday for US. Cheers, Armando __ OpenStack Development Mailing List (not for usage

[openstack-dev] [Neutron] Gate failure

2016-01-13 Thread Armando M.
It's the usual time of the week where I submit the dreaded email Please do not push anything in the queue until change [1] merges. Cheers, Armando [1] https://review.openstack.org/#/c/266885/ __ OpenStack Development

Re: [openstack-dev] [Neutron] Team meeting on Tuesday 1400UTC

2016-01-13 Thread Armando M.
On 12 January 2016 at 20:07, Kyle Mestery wrote: > On Tue, Jan 12, 2016 at 5:28 PM, Doug Wiegley < > doug...@parksidesoftware.com> wrote: > >> I don’t think it ninja merged. It had plenty of reviews, and was open >> during international hours. I don’t have any issue there.

Re: [openstack-dev] [QA][Neutron] IPv6 related intermittent test failures

2016-02-05 Thread Armando M.
On 3 February 2016 at 18:49, Armando M. <arma...@gmail.com> wrote: > > > On 3 February 2016 at 04:28, Sean Dague <s...@dague.net> wrote: > >> On 02/02/2016 10:03 PM, Matthew Treinish wrote: >> > On Tue, Feb 02, 2016 at 05:09:47PM -0800, Armando M. wrote: >

Re: [openstack-dev] [neutron] [ipam] Migration to pluggable IPAM

2016-02-04 Thread Armando M.
On 4 February 2016 at 08:22, John Belamaric wrote: > > > On Feb 4, 2016, at 11:09 AM, Carl Baldwin wrote: > > > > On Thu, Feb 4, 2016 at 7:23 AM, Pavel Bondar > wrote: > >> I am trying to bring more attention to [1] to make

Re: [openstack-dev] [Neutron] Evolving the stadium concept

2016-02-05 Thread Armando M.
ing related projects "near" > the group of people that has the best context to review / help and > comment, its obviously not working and thats fine, lets > try something different... > > > On Thu, Feb 4, 2016 at 8:18 PM, Armando M. <arma...@gmail.com> wrote: &g

Re: [openstack-dev] [nova][neutron] How would nova microversion get-me-a-network in the API?

2016-02-12 Thread Armando M.
On 12 February 2016 at 09:15, Matt Riedemann wrote: > Forgive me for thinking out loud, but I'm trying to sort out how nova > would use a microversion in the nova API for the get-me-a-network feature > recently added to neutron [1] and planned to be leveraged in nova

Re: [openstack-dev] [nova][neutron] How would nova microversion get-me-a-network in the API?

2016-02-12 Thread Armando M.
On 12 February 2016 at 11:08, Matt Riedemann <mrie...@linux.vnet.ibm.com> wrote: > > > On 2/12/2016 12:44 PM, Armando M. wrote: > >> >> >> On 12 February 2016 at 09:15, Matt Riedemann <mrie...@linux.vnet.ibm.com >> <mailto:mrie...@linux.vnet.ibm.co

Re: [openstack-dev] [Neutron] Evolving the stadium concept

2016-02-04 Thread Armando M.
rceive the practical effect of that decision. >> >> Allow me to expand: >> It seems to me like there is no significance to who is 'in or out'. >> However, people, including potential customers, look at the list of >> the Neutron stadium and deduce that project X is better than Y be

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

2016-02-05 Thread Armando M.
Hi neutrinos, A kind reminder for next week's meeting. More on the agenda [1]. Cheers, Armando [1] https://wiki.openstack.org/wiki/Network/Meetings __ OpenStack Development Mailing List (not for usage questions)

Re: [openstack-dev] [Nova][Neutron] Scheduling with routed networks

2016-01-29 Thread Armando M.
On 29 January 2016 at 12:16, Jay Pipes wrote: > On 01/28/2016 09:15 PM, Carl Baldwin wrote: > >> Hi Nova and Neutron, >> >> It was a pleasure to attend the Nova mid-cycle in Bristol this week. >> > > Indeed, I thought the mid-cycle was super-productive. Yup, I always

Re: [openstack-dev] [neutron] https://wiki.openstack.org/wiki/Neutron_Plugins_and_Drivers

2016-01-27 Thread Armando M.
I'll kill it, as this should be superseded by the in-tree devref version. Thanks for pointing my attention to it. On 27 January 2016 at 23:40, Neil Jerram wrote: > Is there any part of the cited wiki page that is still relevant?I've just > been asked whether

[openstack-dev] [QA][Neutron] IPv6 related intermittent test failures

2016-02-02 Thread Armando M.
Folks, We have some IPv6 related bugs [1,2,3] that have been lingering for some time now. They have been hurting the gate (e.g. [4] the most recent offending failure) and since it looks like they have been without owners nor a plan of action for some time, I made the hard decision of skipping

Re: [openstack-dev] [QA][Neutron] IPv6 related intermittent test failures

2016-02-03 Thread Armando M.
On 3 February 2016 at 04:28, Sean Dague <s...@dague.net> wrote: > On 02/02/2016 10:03 PM, Matthew Treinish wrote: > > On Tue, Feb 02, 2016 at 05:09:47PM -0800, Armando M. wrote: > >> Folks, > >> > >> We have some IPv6 related bugs [1,2,3] that have been l

[openstack-dev] Team meeting this Tuesday at 1400 UTC

2016-01-30 Thread Armando M.
Hi neutrinos, According to [1], this is a kind reminder for next week's meeting: please do not get caught by the confusion. The Tuesday meetings will be hosted by Ihar, and I will be working with him to discuss these meeting agendas [2] ahead of time. For this reason, stay tuned for reminder

Re: [openstack-dev] [QA][Neutron] IPv6 related intermittent test failures

2016-02-02 Thread Armando M.
On 2 February 2016 at 19:03, Matthew Treinish <mtrein...@kortar.org> wrote: > On Tue, Feb 02, 2016 at 05:09:47PM -0800, Armando M. wrote: > > Folks, > > > > We have some IPv6 related bugs [1,2,3] that have been lingering for some > > time now. They have been hu

[openstack-dev] [Neutron] Drivers meeting cancelled Feb 25

2016-02-23 Thread Armando M.
Folks, Just a reminder that due to the ongoing Neutron mid-cycle, the drivers team is cancelled for this week. We'll be sending out a report at the end of the week/early next week to keep you abreast of the progress made. Cheers, Armando

[openstack-dev] [Neutron] Gate failure

2016-02-25 Thread Armando M.
Folks, The API job recent breakage prevents us from merging code. Please refrain from pushing patches to the merge queue until [1] completes going through the pipeline. A. [1] https://review.openstack.org/#/c/284911/ __

[openstack-dev] [Neutron] DocImpact flag: a kind reminder

2016-02-29 Thread Armando M.
Hi Neutrinos, Please remember that what you decorate a commit message with DocImpact, this must be followed by a brief description of the documentation impact [1]. Also, please be aware that currently, as soon as the patch merges, a bug report is filed against the Launchpad project of the

Re: [openstack-dev] [Neutron] DocImpact flag: a kind reminder

2016-02-29 Thread Armando M.
don't need to add the flag into the implementation patch, > do we? > I would not personally add a DocImpact on a spec patch. > > Thanks, > Hirofumi > > > On 2016/03/01 7:18, Armando M. wrote: > > Hi Neutrinos, > > Please remember that what you decorate a co

[openstack-dev] [Neutron] Mid-cycle report

2016-02-26 Thread Armando M.
Hi Neutrinos, For those of you who couldn't join in person, please find a few notes below to capture some of the highlights of the event. I would like to thank everyone one who helped me put this report together, and everyone who helped make this mid-cycle a fruitful one. I would also like to

Re: [openstack-dev] [nova][neutron][upgrade] Grenade multinode partial upgrade - Nova metadata failure

2016-02-22 Thread Armando M.
On 22 February 2016 at 04:56, Ihar Hrachyshka <ihrac...@redhat.com> wrote: > Sean M. Collins <s...@coreitpro.com> wrote: > > Armando M. wrote: >> >>> Now that the blocking issue has been identified, I filed project-config >>> change [1] to enable

Re: [openstack-dev] [nova][neutron][upgrade] Grenade multinode partial upgrade - Nova metadata failure

2016-02-22 Thread Armando M.
On 22 February 2016 at 08:52, Ihar Hrachyshka <ihrac...@redhat.com> wrote: > Armando M. <arma...@gmail.com> wrote: > > >> >> On 22 February 2016 at 04:56, Ihar Hrachyshka <ihrac...@redhat.com> >> wrote: >> Sean M. Collins <s..

Re: [openstack-dev] [Neutron] Gate failure

2016-02-26 Thread Armando M.
Cheers, Armando > > Thanks, > doug > > On Feb 25, 2016, at 2:46 PM, Armando M. <arma...@gmail.com> wrote: > > Folks, > > The API job recent breakage prevents us from merging code. Please refrain > from pushing patches to the merge queue until [1] completes

Re: [openstack-dev] [neutron] BGP Dynamic Routing Development Going Forward

2016-01-22 Thread Armando M.
On 22 January 2016 at 08:57, Tidwell, Ryan wrote: > I wanted to raise the question of whether to develop BGP dynamic routing > in the Neutron repo or spin it out to as a stadium project. This question > has been raised recently on reviews and in offline discussions. For

Re: [openstack-dev] [neutron] BGP Dynamic Routing Development Going Forward

2016-01-25 Thread Armando M.
past/ongoing experience; if you continue ignoring this simple fact in your judgement, then this discussion is pointless. > > > Gal. > > > > On Sat, Jan 23, 2016 at 2:15 AM, Vikram Choudhary <viks...@gmail.com> > wrote: > > I agree with Armando and feel option 2 would be v

Re: [openstack-dev] [Neutron][[Infra] Gate failure

2016-01-19 Thread Armando M.
bs. > > > > -- Dims > > > > On Tue, Jan 19, 2016 at 8:28 PM, Armando M. <arma...@gmail.com> wrote: > >> Hi neutrinos, > >> > >> New week, new gate failure. This time this might be infra related [1]. > This > >>

Re: [openstack-dev] [Neutron] Team meeting on Tuesday 1400UTC

2016-01-20 Thread Armando M.
On 20 January 2016 at 08:20, Edgar Magana wrote: > Just providing support for Kyle’s proposal! > It is working very well for other teams such as nova, docs between others. > At risk of stating the obvious, not every project is equal, and as I mentioned in an earlier

[openstack-dev] [Neutron] Drivers meeting calendar update

2016-01-20 Thread Armando M.
Hi folks, At request of a team member, we've been looking into other time slots [1] I am afraid, there is no way we can please everyone, and we may want to revise the slot in function of the location of the team members in the future. Let me remind that we look at team membership [2] regularly

Re: [openstack-dev] [keystone][neutron][requirements] - keystonemiddleware-4.1.0 performance regression

2016-01-19 Thread Armando M.
On 19 January 2016 at 22:46, Kevin Benton wrote: > Hi all, > > We noticed a major jump in the neutron tempest and API test run times > recently in Neutron. After digging through logstash I found out that it > first occurred on the requirements bump here: >

Re: [openstack-dev] [keystone][neutron][requirements] - keystonemiddleware-4.1.0 performance regression

2016-01-20 Thread Armando M.
] https://review.openstack.org/#/c/270417/ > > > stevemar > > [image: Inactive hide details for "Armando M." ---2016/01/20 01:59:44 > AM---On 19 January 2016 at 22:46, Kevin Benton <blak...@gmail.com]"Armando > M." ---2016/01/20 01:59:44 AM---On 19

[openstack-dev] [Neutron] Mitaka-2

2016-01-20 Thread Armando M.
Hi neutrinos, The release patch [1] has landed. The existing workload for the remainder of the cycle is tracked in [2]. If you have something shown on this dashboard (or if you don't, but you want to), please reach out either via ML (on this thread) or on #openstack-neutron. Cheers, Armando

Re: [openstack-dev] [neutron][networking-calico] To be or not to be an ML2 mechanism driver?

2016-01-24 Thread Armando M.
On 22 January 2016 at 10:35, Neil Jerram wrote: > networking-calico [1] is currently implemented as an ML2 mechanism > driver, but > I'm wondering if it might be better as its own core plugin, and I'm > looking for > input about the implications of that, or for

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

2016-01-24 Thread Armando M.
Hi neutrinos, A kind reminder for next week's meeting. Being the meeting right after the milestone was cut, I'd like to take most of the hour to talk about blueprints/specs, i.e. the beefy workload that has merged, and has yet to merge. We'll be brief on announcements and bugs, and skip the

[openstack-dev] [Neutron][[Infra] Gate failure

2016-01-19 Thread Armando M.
Hi neutrinos, New week, new gate failure. This time this might be infra related [1]. This one fails with [2]. If you know what's going on, spread the word! Cheers, Armando [1] https://review.openstack.org/#/c/269937/ [2]

[openstack-dev] [Neutron] Check queue broken on master

2016-02-17 Thread Armando M.
Hi folks, It looks like something slipped in and how we got persistent failures on functional/fullstack jobs [1]. Has anyone triaged? I couldn't find anything in [2]. The effect for this: we can't merge anything until this gets resolved. Some might argue this is not necessarily a bad thing...

Re: [openstack-dev] [Neutron] Check queue broken on master

2016-02-17 Thread Armando M.
On 17 February 2016 at 11:12, Armando M. <arma...@gmail.com> wrote: > Hi folks, > > It looks like something slipped in and how we got persistent failures on > functional/fullstack jobs [1]. Has anyone triaged? I couldn't find anything > in [2]. > Looks like [1] fixed it

Re: [openstack-dev] [Neutron] Check queue broken on master

2016-02-17 Thread Armando M.
On 17 February 2016 at 11:22, Assaf Muller <amul...@redhat.com> wrote: > On Wed, Feb 17, 2016 at 2:16 PM, Armando M. <arma...@gmail.com> wrote: > > > > > > On 17 February 2016 at 11:12, Armando M. <arma...@gmail.com> wrote: > >> > >> Hi fo

Re: [openstack-dev] [nova][neutron][upgrade] Grenade multinode partial upgrade

2016-02-18 Thread Armando M.
On 18 February 2016 at 08:41, Sean M. Collins wrote: > This week's update: > > Armando was kind enough to take a look[1], since he's got a fresh > perspective. I think I've been suffering from Target Fixation[1] > where I failed to notice a couple other failures in the logs.

Re: [openstack-dev] [nova][neutron][upgrade] Grenade multinode partial upgrade - Nova metadata failure

2016-02-19 Thread Armando M.
On 19 February 2016 at 04:43, Sean Dague <s...@dague.net> wrote: > On 02/18/2016 09:50 PM, Armando M. wrote: > > > > > > On 18 February 2016 at 08:41, Sean M. Collins <s...@coreitpro.com > > <mailto:s...@coreitpro.com>> wrote: > > > >

[openstack-dev] [Neutron] next Team meeting cancelled (Feb-22)

2016-02-19 Thread Armando M.
Hi Neutrinos, This week is Mid-cycle week [1], and some of us will be potentially enroute to the destination. For this reason, the meeting is cancelled. If you're interested in participating remotely, please keep an eye on the etherpad for updates. Cheers, Armando [1]

Re: [openstack-dev] [nova][neutron] How would nova microversion get-me-a-network in the API?

2016-02-19 Thread Armando M.
On 19 February 2016 at 09:49, John Garbutt wrote: > On 19 February 2016 at 16:28, Andrew Laski wrote: > > On Fri, Feb 19, 2016, at 11:14 AM, Sean Dague wrote: > >> On 02/19/2016 09:30 AM, Andrew Laski wrote: > >> > > >> > > >> > On Thu, Feb 18, 2016, at

Re: [openstack-dev] [kolla] discussion about core reviewer limitations by company

2016-02-21 Thread Armando M.
On 20 February 2016 at 12:58, Steven Dake (stdake) wrote: > Neutron, the largest project in OpenStack by active committers and > reviewers as measured by the governance repository teamstats tool, has a > limit of 2 core reviewers per company. They do that for a reason. I >

Re: [openstack-dev] [kolla] discussion about core reviewer limitations by company

2016-02-21 Thread Armando M.
On 20 February 2016 at 14:06, Kevin Benton wrote: > I don't think neutron has a limit. There are 4 from redhat and 3 from hp > and mirantis right now. > https://review.openstack.org/#/admin/groups/38,members > By the way, technically speaking some of those also only limit

Re: [openstack-dev] [neutron] [ipam] Migration to pluggable IPAM

2016-02-11 Thread Armando M.
On 10 February 2016 at 15:19, Carl Baldwin <c...@ecbaldwin.net> wrote: > On Thu, Feb 4, 2016 at 8:12 PM, Armando M. <arma...@gmail.com> wrote: > > Technically we can make this as sophisticated and seamless as we want, > but > > this is a one-off, once it's done th

Re: [openstack-dev] [neutron] [ipam] Migration to pluggable IPAM

2016-02-11 Thread Armando M.
after that. But perhaps the > other way of looking at it is that we should make an exception in the > deprecation process. > >> > >> Salvatore > >> > >> On 11 February 2016 at 00:19, Carl Baldwin <c...@ecbaldwin.net> wrote: > >>

Re: [openstack-dev] [Neutron] Team meeting this Tuesday at 1400 UTC

2016-02-01 Thread Armando M.
ng this, I totally miss it, the jet lag must have caught up with me. Cheers, Armando > On Sat, Jan 30, 2016 at 2:27 PM, Armando M. <arma...@gmail.com> wrote: > > Hi neutrinos, > > > > According to [1], this is a kind reminder for next week's meeting: &g

[openstack-dev] [Neutron] Hitting Mitaka Milestone 3 and feature freeze exception process

2016-03-01 Thread Armando M.
Hi Neutrinos, As I am sure all of you know, this week is Milestone week [1], for this reason, we need to cut releases for both neutron, neutron *-aas, and the client. Patches [2, 3] are still in draft, and whilst stuff is in flight, we'll hold on until we have reached a sensible point where it's

Re: [openstack-dev] [neutron][oslo]neutron agent not receiving callback

2016-03-09 Thread Armando M.
On 9 March 2016 at 09:14, Assaf Muller wrote: > On Wed, Mar 9, 2016 at 9:40 AM, Ihar Hrachyshka > wrote: > > Vikash Kumar wrote: > > > >> > >> > >> On Wed, Mar 9, 2016 at 3:42 PM, Vikash Kumar > >>

[openstack-dev] [Neutron] stable/mitaka branch imminent for the client

2016-03-09 Thread Armando M.
Folks, Please see [1]. I gave Doug the go-ahead. Cheers, Armando [1] http://lists.openstack.org/pipermail/openstack-dev/2016-March/088853.html __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

[openstack-dev] [Neutron] Ihar as *-aas core reviewer

2016-03-09 Thread Armando M.
Folks, I would like to have Ihar as core reviewer for the advanced services (or any neutron-governance project for the time we have those projects in the governance). Ihar is instrumental in ensuring that gate/stable issues are dealt with promptly and swiftly and I trust he'll be using such as

Re: [openstack-dev] [neutron] Last chance to finish changes affecting DB schema for Mitaka

2016-03-09 Thread Armando M.
On 9 March 2016 at 07:42, Ihar Hrachyshka wrote: > Henry Gessau wrote: > > By tomorrow we intend to tag the heads of all the neutron alembic branches >> with the MITAKA label [1][2][3][4]. >> >> If you have a patch that adds an alembic migration and you

Re: [openstack-dev] [release][all][ptl] preparing to create stable/mitaka branches for libraries

2016-03-09 Thread Armando M.
Good to go with: openstack/python-neutronclient 4.1.1 Thanks, Armando On 9 March 2016 at 09:26, Doug Hellmann wrote: > It's time to start opening the stable branches for libraries. I've > prepared a list of repositories and the proposed versions from which > we will

Re: [openstack-dev] [Neutron] Mitaka release planning

2016-03-10 Thread Armando M.
On 3 March 2016 at 12:05, Armando M. <arma...@gmail.com> wrote: > Hi Neutrinos, > > Mitaka-3 is out [1] and we should be focussing on rc1. This is the time > where we switch gear: > >- Test M-3, find issues and target them for RC1 [2]; >- Apply/agree for FFE

Re: [openstack-dev] [Neutron] Ironing out outstanding issues in time for RC1

2016-03-13 Thread Armando M.
On 13 March 2016 at 15:14, Ihar Hrachyshka <ihrac...@redhat.com> wrote: > Armando M. <arma...@gmail.com> wrote: > > Neutrinos, >> >> We have about ~20 outstanding bugs marked Medium/High/Critical, and we >> have only one or two days left to have a chance to

[openstack-dev] [Neutron] RC1 candidate

2016-03-15 Thread Armando M.
Neutrinos, I believe we reached the point [1] where RC1 can be cut [2]. If I made an error of judgement, or any other catastrophic failure arises, please report a bug, and tag it as mitaka-rc-potential [3]. Please, sign off on postmortem [4], so that we can finalize the specs status for Mitaka

Re: [openstack-dev] [neutron][release] Releasing python-neutronclient 4.1.2?

2016-03-08 Thread Armando M.
On 8 March 2016 at 15:07, Doug Hellmann <d...@doughellmann.com> wrote: > Excerpts from Armando M.'s message of 2016-03-08 12:49:16 -0700: > > Hi folks, > > > > There's a feature or two that are pending to be delivered in Mitaka > [1,2], > > and those involve c

[openstack-dev] [Neutron] Linuxbridge gate failures

2016-03-09 Thread Armando M.
Neutrinos, We had two back-to-back gate failures on [1,2] and more seem to be ramping up. These are tracked in bug [3] (e-r query tracked in [4]). Can I trouble some gentle soul to have a look? Thanks, Armando [1] https://review.openstack.org/#/c/286818/ [2]

[openstack-dev] [Neutron] Ironing out outstanding issues in time for RC1

2016-03-11 Thread Armando M.
Neutrinos, We have about ~20 outstanding bugs marked Medium/High/Critical, and we have only one or two days left to have a chance to get them in the gate queue [1]. Can I trouble you to go and make sure patches are up to date and well reviewed? Many thanks, Armando [1]

Re: [openstack-dev] [Neutron] BGP support

2016-03-30 Thread Armando M.
On 30 March 2016 at 17:07, Abhishek Raut wrote: > I think what Gary is talking about is BGP and the Border Gateway API > spec[1] in L2 GW repo. > [1] https://review.openstack.org/#/c/270786/ > Spec [1] has nothing to do with BGP (the routing protocol) last time I checked (note

Re: [openstack-dev] [nova][neutron] What to do about booting into port_security_enabled=False networks?

2016-03-30 Thread Armando M.
On 30 March 2016 at 13:40, Sean Dague wrote: > On 03/29/2016 09:55 PM, Matt Riedemann wrote: > > > > > Yup, HenryG walked me through the cases on IRC today. > > > > The more I think about option (b) above, the less I like that idea given > > how much work goes into the

Re: [openstack-dev] [nova][neutron] What to do about booting into port_security_enabled=False networks?

2016-03-30 Thread Armando M.
On 29 March 2016 at 18:55, Matt Riedemann <mrie...@linux.vnet.ibm.com> wrote: > > > On 3/29/2016 4:44 PM, Armando M. wrote: > >> >> >> On 29 March 2016 at 08:08, Matt Riedemann <mrie...@linux.vnet.ibm.com >> <mailto:mrie...@linux.vnet.ibm.com>

[openstack-dev] [Neutron] Drivers team cancelled

2016-04-07 Thread Armando M.
Hi Neutrinos, Too many firefights this week and I personally didn't have much time to spend on reviewing RFEs etc. If you guys want to have it, please go ahead but I won't be able to join. Cheers, Armando __ OpenStack

[openstack-dev] Drivers team cancelled

2016-04-07 Thread Armando M.
Hi Neutrinos, Too many firefights this week and I personally didn't have much time to spend on reviewing RFEs etc. If you guys want to have it, please go ahead but I won't be able to join. Cheers, Armando __ OpenStack

Re: [openstack-dev] [Neutron] Newton blueprints call for action

2016-04-07 Thread Armando M.
GP SIGNED MESSAGE- > Hash: SHA256 > > Hi Armando, > > On 05/04/16 01:13 AM, Armando M. wrote: > > Hi Neutrinos, > > > > During today's team meeting [0], we went through the current > > milestone workload [1]. > > > > This is mostly made of Mitaka bac

Re: [openstack-dev] [Neutron] Newton Design summit schedule - Draft

2016-04-12 Thread Armando M.
On 12 April 2016 at 12:16, Matt Riedemann <mrie...@linux.vnet.ibm.com> wrote: > > > On 4/11/2016 11:56 PM, Armando M. wrote: > >> Hi folks, >> >> A provisional schedulefor the Neutron project is available [1]. I am >> still working with the session

Re: [openstack-dev] [Neutron] Newton Design summit schedule - Draft

2016-04-12 Thread Armando M.
n-2016/summit-schedule/events/6893?goback=1 > > Michael > Swapped with the first slot of the day. I also loaded etherpads here: https://wiki.openstack.org/wiki/Design_Summit/Newton/Etherpads#Neutron Cheers, Armando > > > On Mon, Apr 11, 2016 at 9:56 PM, Armando M. <arma..

Re: [openstack-dev] [Neutron] Newton Design summit schedule - Draft

2016-04-12 Thread Armando M.
On 12 April 2016 at 12:36, Anita Kuno <ante...@anteaya.info> wrote: > On 04/12/2016 03:23 PM, Armando M. wrote: > > On 12 April 2016 at 12:16, Matt Riedemann <mrie...@linux.vnet.ibm.com> > > wrote: > > > >> > >> > >>

Re: [openstack-dev] [devstack][neutron] Eliminating the DevStack layer

2016-04-08 Thread Armando M.
On 8 April 2016 at 11:06, Sean Dague wrote: > On 04/08/2016 12:05 PM, Morales, Victor wrote: > > Agree, sometimes is hard to figure out what is the Devstack variable > that will modify the configuration value. > > > > There is an effort to categorize the configuration options[1]

[openstack-dev] [Neutron] Newton Design summit schedule - Draft

2016-04-11 Thread Armando M.
Hi folks, A provisional schedule for the Neutron project is available [1]. I am still working with the session chairs and going through/ironing out some details as well as gathering input from [2]. I hope I can get something more final by the end of this week. In the meantime, please free to ask

Re: [openstack-dev] [Neutron] Evolving the stadium concept

2016-04-07 Thread Armando M.
t. Thanks, Armando [1] https://review.openstack.org/#/c/303026/ [2] https://review.openstack.org/#/c/303039/ [3] https://review.openstack.org/#/c/276461/ [4] https://github.com/openstack/releases/tree/master/deliverables/_independent > > > On Fri, Mar 4, 2016 at 12:39 AM, Armando M. &

<    1   2   3   4   5   6   7   >