[openstack-dev] [requirements] cross project testing

One of the things that seems to happen now and then is that an update to requirements breaks gate for other projects in some way. One thing that helps is cross project testing, though we do that on a one off basis I'd like to see this testing become more codified. I have a review out that does a

Re: [openstack-dev] [octavia] ssl re-encryption in octavia

I do not believe it is in it and I don't know if anyone is working on it. I believe it has pushed down the priority stack, but someone might correct me if I'm wrong. Thanks, Brandon On Fri, 2016-07-22 at 16:00 -0700, Akshay Kumar Sanghai wrote: > Hi, > I saw in specs of kilo that ssl

Re: [openstack-dev] [Congress] Congress horizon plugin - congressclient/congress API auth issue - help

Hi Aimee, Thanks for the investigation. I remember testing congress client with V3 password based authentication , which worked fine .. but never tested with token based . Please go ahead and fix it , if you think there is any issue . On 22-Jul-2016 9:38 PM, "Aimee Ukasick"

Re: [openstack-dev] [Neutron][networking-ovn][networking-odl] Syncing neutron DB and OVN DB

Thanks Numan & Amitabha, this may be the right direction to solve the bug [1]. It basically implements Neutron API as async call, and queuing the request within DB transaction, and the ordering is preserved by the journal thread "lock" that is implemented with state PROCESSING plus DB

Re: [openstack-dev] [kolla] Monitoring tooling

Yes, this is my thought. The scope of the Sensu work is: "Is this thing working?" (with the reference being up/down) But the scope of the Grafana and friends is, "How hard is this working?" (but no alerting) They are certainly complementary However, Sensu can throw data at a Grafana stack

Re: [openstack-dev] [kolla] Monitoring tooling

I think those are two different, complementary things. One's metrics and the other is monitoring. You probably want both at the same time. Thanks, Kevin From: Steven Dake (stdake) [std...@cisco.com] Sent: Friday, July 22, 2016 3:52 PM To: OpenStack

[openstack-dev] [octavia] ssl re-encryption in octavia

Hi, I saw in specs of kilo that ssl re-encryption will be introduced in later phase. Is the ssl re-encryption feature available in the mitaka release? I understand ssl offload is available, but I want to try the ssl re-encryption on octavia lbaas. This link refers to v1 probably

Re: [openstack-dev] [kolla] Monitoring tooling

Thanks for pointing that out. Brain out to lunch today it appears :( I think choices are a good thing even though they increase our implementation footprint. Anyone opposed to implementing both with something in globals.yml like monitoring: grafana or monitoring: sensu Comments questions or

Re: [openstack-dev] [kolla] Monitoring tooling

Don't forget mewalds implementation as well - we now have 2 monitoring options for kolla :-) On Fri, Jul 22, 2016 at 3:15 PM, Steven Dake (stdake) wrote: > Hi folks, > > At the midcycle we decided to push off implementing Monitoring until post > Newton. The rationale for this

Re: [openstack-dev] [Magnum] Remove Davanum Srinivas from Magnum core team

Your a class act Dims. It was good working with you on Magnum :) Regards -steve On 7/22/16, 2:15 PM, "Davanum Srinivas" wrote: >Thanks Hongbin! > >On Fri, Jul 22, 2016 at 5:13 PM, Hongbin Lu wrote: >> Hi all, >> >> >> >> Based on Dims¹s request, I

Re: [openstack-dev] [kolla] Please start getting in the habit of breaking up containers from ansible changes

Precisely! From: "Fox, Kevin M" > Reply-To: "OpenStack Development Mailing List (not for usage questions)" > Date: Friday, July 22, 2016 at 3:03 PM To: "OpenStack Development

[openstack-dev] [kolla] Monitoring tooling

Hi folks, At the midcycle we decided to push off implementing Monitoring until post Newton. The rationale for this decision was that the core review team has enough on their plates and nobody was super keen to implement any monitoring solution given our other priorities. Like all good

Re: [openstack-dev] [kolla] Please start getting in the habit of breaking up containers from ansible changes

I think its an interesting idea. If nothing else, it will show what it would be like to have a split set of repo's before it actually is a thing and can't be undone. Thanks, Kevin From: Dave Walker [em...@daviey.com] Sent: Friday, July 22, 2016 2:19 PM To:

Re: [openstack-dev] [kolla] Please start getting in the habit of breaking up containers from ansible changes

From: Dave Walker > Reply-To: "OpenStack Development Mailing List (not for usage questions)" > Date: Friday, July 22, 2016 at 2:19 PM To: "OpenStack Development Mailing List

Re: [openstack-dev] [tc][all] Plugins for all

On Fri, Jul 22, 2016 at 2:08 PM, Hayes, Graham wrote: > * OpenStack Client > > OpenStack CLI privileged projects have access to more commands, as > plugins cannot hook in to them (e.g. quotas) > It's been OSC's intention to allow for command hooking, we just don't

Re: [openstack-dev] [tripleo] CI job to test undercloud only

On Fri, Jul 22, 2016 at 4:53 PM, Emilien Macchi wrote: > Hi, > > I started some work to have a CI job that will only deploy an undercloud. > We'll save time and resources. > > I used storyboard: https://storyboard.openstack.org/#!/story/2000682 > and I invite our contributors

Re: [openstack-dev] [kolla] Please start getting in the habit of breaking up containers from ansible changes

On 22 July 2016 at 21:35, Steven Dake (stdake) wrote: > > Hey folks, > > I know it doesn't make a lot of sense to break up containers from ansible changes to people outside the core review team, but for anything with backport potential, please do so. We are considering in

Re: [openstack-dev] [Magnum] Remove Davanum Srinivas from Magnum core team

Thanks Hongbin! On Fri, Jul 22, 2016 at 5:13 PM, Hongbin Lu wrote: > Hi all, > > > > Based on Dims’s request, I removed him from the Magnum core reviewer team. > Dims’s contribution started from the first commit of the Magnum tree, and he > was served as a Magnum core

[openstack-dev] [Magnum] Remove Davanum Srinivas from Magnum core team

Hi all, Based on Dims's request, I removed him from the Magnum core reviewer team. Dims's contribution started from the first commit of the Magnum tree, and he was served as a Magnum core reviewer for a long time. I am sorry to hear that Dims want to leave the team, but thanks for his

Re: [openstack-dev] [tc][all] Plugins for all

On 21/07/2016 16:49, Doug Hellmann wrote: > Excerpts from Hayes, Graham's message of 2016-07-19 16:59:20 +: >> On 19/07/2016 16:39, Doug Hellmann wrote: >>> Excerpts from Hayes, Graham's message of 2016-07-18 17:13:09 +: On 18/07/2016 17:57, Thierry Carrez wrote: > Hayes, Graham

[openstack-dev] [tripleo] CI job to test undercloud only

Hi, I started some work to have a CI job that will only deploy an undercloud. We'll save time and resources. I used storyboard: https://storyboard.openstack.org/#!/story/2000682 and I invite our contributors to use it too when working in TripleO CI, it helps us to track our current work. So far

[openstack-dev] [kolla] Please start getting in the habit of breaking up containers from ansible changes

Hey folks, I know it doesn't make a lot of sense to break up containers from ansible changes to people outside the core review team, but for anything with backport potential, please do so. We are considering in Occata splitting the kolla repo into two (kolla = containers & build,

[openstack-dev] [magnum] Proposing Spyros Trigazis for Magnum core reviewer team

Hi all, Spyros has consistently contributed to Magnum for a while. In my opinion, what differentiate him from others is the significance of his contribution, which adds concrete value to the project. For example, the operator-oriented install guide he delivered attracts a significant number of

Re: [openstack-dev] [Neutron] Proposing Jakub Libosvar for testingcore

Ofcourse insightful reviewers will make development fast. So ++ From: Darek Śmigiel [mailto:smigiel.dari...@gmail.com] Sent: Friday, July 22, 2016 7:20 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Neutron]

Re: [openstack-dev] [devstack][neutron] - neutron gate blocked by devstack change

Also I was the one who approved the original patch, so the fault rests on my shoulders. My apologies. -- Sean M. Collins __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [devstack][neutron] - neutron gate blocked by devstack change

I just approved the revert. I think we need to step back and re-evaluate the work that we are doing in neutron-legacy. It's very fragile - and really any change to that piece of logic ends up breaking networking-generic-switch, ironic-multitenant-network, midonet, or the gate. Which is why I'm

Re: [openstack-dev] [devstack] How to enable SSL in devStack?

On Wed, Jul 20, 2016, at 07:01 AM, Rob Crittenden wrote: > Andrey Pavlov wrote: > > Hi, > > > > When I ran devstack with SSL I found a bug and tried to fix it - > > https://review.openstack.org/#/c/242812/ > > But no one agree with me. > > Try to apply this patch - it may help. > > Also there is

Re: [openstack-dev] [Neutron] Proposing Jakub Libosvar for testingcore

+1 On Fri, 2016-07-22 at 09:19 -0500, Darek Śmigiel wrote: > I’m not a core, so treat this as +0 but I think Jakub will be good > addition to core team. > > > So +1 > > > On Jul 22, 2016, at 3:20 AM, Martin Hickey > > wrote: > > > > +1 > > > > Oleg Bondarev

Re: [openstack-dev] [cinder] Volume Drivers unit tests

Eric, you're right. I've disabled all such tests using '@unittest.skip("Skip until bug #1578986 is fixed")' decorator in my patch: $ grep -r '1578986' cinder/tests/unit/ | grep -v 'pyc' | wc -l 37 Next step is to fix them. [1] https://review.openstack.org/#/c/320148/ Regards, Ivan

Re: [openstack-dev] [nova] gate "gate-nova-python27-db" is broken due to oslo.context 2.6.0

Excerpts from Jamie Lennox's message of 2016-07-20 10:28:29 +1000: > On 20 July 2016 at 00:06, Joshua Harlow wrote: > > > Hayes, Graham wrote: > > > >> On 18/07/16 22:27, Ronald Bradford wrote: > >> > >>> Hi All, > >>> > >>> For Oslo libraries we ensure that API's are

[openstack-dev] [Cinder] Midcycle Action item Summary

Hello All, We came out of the Midcycle with a lot of things on a lot of people’s plates. Here is a summary of what everyone signed up for and what things need owners. scottda: - Pick a time to meet weekly to discuss and push ahead with Active-Active HA (day1) - Find out the

Re: [openstack-dev] [Congress] Congress horizon plugin - congressclient/congress API auth issue - help

All - I made the change to the auth_url that Anusha suggested. Same problem as before " Cannot authorize API client" 2016-07-22 14:13:50.835861 * calling policies_list = client.list_policy()* 2016-07-22 14:13:50.836062 Unable to get policies list: Cannot authorize API client. I used the

Re: [openstack-dev] [devstack] How to enable SSL in devStack?

Brant Knudson wrote: On Wed, Jul 20, 2016 at 12:29 PM, Rob Crittenden > wrote: Fixing Keystone is easy. An Apache VirtualHost for 443 needs to be added. But I found another, deeper problem: cinder won't listen on SSL. When they

Re: [openstack-dev] [Nova] Remove duplicate code using Data Driven Tests (DDT)

On Thu, Jul 21, 2016 at 07:03:53AM -0700, Matt Riedemann wrote: > On 7/21/2016 2:03 AM, Bhor, Dinesh wrote: > > Hi Nova Devs, > > > > > > > > Many times, there are a number of data sets that we have to run the same > > tests on. > > > > And, to create a different test for each data set values

Re: [openstack-dev] [devstack] How to enable SSL in devStack?

On Wed, Jul 20, 2016 at 12:29 PM, Rob Crittenden wrote: > Rob Crittenden wrote: > >> Andrey Pavlov wrote: >> >>> Hi, >>> >>> When I ran devstack with SSL I found a bug and tried to fix it - >>> https://review.openstack.org/#/c/242812/ >>> But no one agree with me. >>> Try to

Re: [openstack-dev] [devstack] some compress error when deploy OS

hope can help you. http://www.chenshake.com/openstack-project-series-3-devstack/ On Fri, Jul 22, 2016 at 9:35 AM, wrote: > > Hi all, > > When i use devstack to deploy a OS env, it raise the error. > The log is as follows. > Does anybody know how to resolve this

Re: [openstack-dev] [cinder] [nova] os-brick privsep failures and an upgrade strategy?

On 7/22/2016 8:20 AM, Angus Lees wrote: On Thu, 21 Jul 2016 at 09:27 Sean Dague > wrote: On 07/12/2016 06:25 AM, Matt Riedemann wrote: > We probably aren't doing anything while Sean Dague is on vacation. He's > back next week and we

Re: [openstack-dev] [Neutron][oslo.db] Inspecting sqlite db during unit tests

On 07/22/2016 04:02 AM, Kevin Benton wrote: Now that we have switched to oslo.db for test provisioning the responsibility of choosing a location lands here: https://github.com/openstack/oslo.db/blob/a79479088029e4fa51def91cb36bc652356462b6/oslo_db/sqlalchemy/provision.py#L505 The problem is

Re: [openstack-dev] [Neutron][oslo.db] Inspecting sqlite db during unit tests

On 07/22/2016 04:02 AM, Kevin Benton wrote: Now that we have switched to oslo.db for test provisioning the responsibility of choosing a location lands here: https://github.com/openstack/oslo.db/blob/a79479088029e4fa51def91cb36bc652356462b6/oslo_db/sqlalchemy/provision.py#L505 The problem is

Re: [openstack-dev] [nova][qa] When do we need tests for microversions in Tempest?

On 7/14/2016 4:40 PM, Matt Riedemann wrote: On 7/14/2016 3:11 AM, GHANSHYAM MANN wrote: 1. Always add a schema change to Tempest if a microversion changes a response. The problem with this is we shouldn't land a schema change by itself in tempest. Until we have something using the schema we

Re: [openstack-dev] [telemetry] Mascot

On Thu, Jul 21 2016, gordon chung wrote: > meerkat is a good option too. i think we have something to vote on :) I've started a poll (sent to core reviewers, it's the easiest), go ahead and vote. I'll stop the vote Tuesday (or before if everyone voted by then!). -- Julien Danjou # Free

[openstack-dev] [nova] Overview of the libvirt instance storage series

This series is part of the priority feature libvirt-instance-storage[1]. At first glance it may not be immediately apparent why, so I'll work backwards for context. The purpose of the feature is to create an unambiguous, canonical source of metadata about 'local' storage. 'Local' here is defined

Re: [openstack-dev] [Neutron] Proposing Jakub Libosvar for testingcore

I’m not a core, so treat this as +0 but I think Jakub will be good addition to core team. So +1 > On Jul 22, 2016, at 3:20 AM, Martin Hickey wrote: > > +1 > > Oleg Bondarev ---22/07/2016 09:13:16---+1 On Fri, Jul 22, 2016 > at 2:36 AM, Doug Wiegley

[openstack-dev] [Fuel] New version of fuel-devops (2.9.22)

Hi All! Today we are going to update the 'fuel-devops' framework on our product CI to the version 2.9.22. It's the FINAL version in 2.9 thread, new active development will be produced in 3.x thread only, and 3.0.1 is released as first of it's. Changes sinse 2.9.21: * For devops: - paramiko

Re: [openstack-dev] [oslo.db] [CC neutron] CIDR overlap functionality and constraints

On 07/21/2016 02:43 PM, Carl Baldwin wrote: None of these operations are expected to be very contentious and performance hasn't really been a concern yet. If it were a big concern, I'd be very interested in the GiST index solution because, as I understand it, detecting overlap without that

[openstack-dev] [nova][neutron] neutron port duplication

Hi, nova and neutron teams, While booting new instance nova requests port for that instance in the neutron. It's possible to have a situation when neutron doesn't response due timeout or connection break and nova retries port creation. It definitely results in ports duplication for instance [1].

[openstack-dev] [Cinder] Logo survey

Hey all, During the midcycle we discussed a few options for a new logo mascot. I've taken a few of the top choices and created a survey to get more input: https://www.surveymonkey.com/r/G7JRNQB Please vote as soon as possible. These are first come, first served, so we should decide soon and get

Re: [openstack-dev] [daisycloud-core] IRC Meeting Log 20160722

t; that: I thought in the future, when we move to work with OPNFV world, we > will still use this channel to discuss not only daisycloud but also > daisy4nfv. I personaly do not want to maintain two meeting by myself. But > your opinions are more than welcome. > > > > > 2

Re: [openstack-dev] [cinder] [nova] os-brick privsep failures and an upgrade strategy?

On Thu, 21 Jul 2016 at 09:27 Sean Dague wrote: > On 07/12/2016 06:25 AM, Matt Riedemann wrote: > > > We probably aren't doing anything while Sean Dague is on vacation. He's > > back next week and we have the nova/cinder meetups, so I'm planning on > > talking about the grenade

Re: [openstack-dev] [cinder] Volume Drivers unit tests

On 07/21/2016 05:26 PM, Knight, Clinton wrote: > Nate, you have to press Ctrl-C to see the in-progress test, that’s why you > don’t > see it in the logs. The bug report shows this and points to the patch where > it > appeared to begin. https://bugs.launchpad.net/cinder/+bug/1578986 > >

Re: [openstack-dev] [Congress] Congress horizon plugin - congressclient/congress API auth issue - help

Thanks Anusha! I will retest this today. I guess I need to learn more about Horizon as well - thanks for pointing me in the right direction. aimee On Fri, Jul 22, 2016 at 6:30 AM, Anusha Ramineni wrote: > Hi Aimee, > > I think devstack by default configured horizon to

Re: [openstack-dev] [Neutron][networking-ovn][networking-odl] Syncing neutron DB and OVN DB

Thanks for the comments Amitabha. Please see comments inline On Fri, Jul 22, 2016 at 5:50 AM, Amitabha Biswas wrote: > Hi Numan, > > Thanks for the proposal. We have also been thinking about this use-case. > > If I’m reading this accurately (and I may not be), it seems that

[openstack-dev] [murano] PTL on vacation

Hi team, I’d like to inform you, that I would be on vacation during next week and a half and would like to appoint some of my deputies =) During this cycle I’m acting as a release liaison, so in my absence I would like Victor Ryzhenkin (freerunner) to act as one and be responsible for

Re: [openstack-dev] [Congress] Congress horizon plugin - congressclient/congress API auth issue - help

Hi Aimee, I think devstack by default configured horizon to use v3 . For V2 authentication, from the logs , auth_url doesn't seem to be set explicitly to v2 auth_url . I have always set explicit v2 auth which worked fine. For eg:- auth_url = 'http://:5000/v2.0' , for V2 authentication I have

Re: [openstack-dev] [ironic][neutron][nova] Sync port state changes.

Kevin, thanks for reply, On Fri, Jul 22, 2016 at 11:50 AM, Kevin Benton wrote: > Hi, > > Once you solve the issue of getting the baremetal ports to transition to > the ACTIVE state, a notification will automatically be emitted to Nova of > 'network-vif-plugged' with the port

Re: [openstack-dev] [kolla][vote] Applying for stable-follows tag

+1 too From: Mauricio Lima [mailto:mauricioli...@gmail.com] Sent: Tuesday, July 19, 2016 5:29 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [kolla][vote] Applying for stable-follows tag +1 2016-07-19 12:23

Re: [openstack-dev] [horizon] Midcycle Summary

On 22/07/16 09:38, Rob Cresswell wrote: > We didn't discuss it explicitly, but I don't believe the decision has > changed. We can remove it, but last I checked the patches in line to > handle testing after deprecation still needed work. If they've been > updated etc. I can look again. > > Rob >

[openstack-dev] [daisycloud-core] IRC Meeting Log 20160722

. But your opinions are more than welcome. 20160722 Agenda === 1) roll call 2) Agenda bashing 3) Approved Wei (kong.w...@zte.com.cn) as daisycloud core reviewer 4) daisycloud status update 5) daisy4nfv status update and disscussion in daisycloud channel Log === ? daisycloud-core

Re: [openstack-dev] [magnum] Discuss the idea of manually managing the bay nodes

Hi Hongbin, This is really a good idea, because it will mitigate much of the job of implementing loop and conditional branch in Heat ResourceGroup. But as Kevin pointed out in below mail, it need a careful upgrade/migration path. Meanwhile, as for the blueprint of supporting multiple flavor

Re: [openstack-dev] [neutron] [tooz] DLM benchmark results

Yes, the backends were deployed in cluster configuration (the configurations are available in the appendix). I'll make a change to the doc to make sure this is reflected properly. On Fri, Jul 22, 2016 at 11:29 AM, Kevin Benton wrote: > Were the backends (zookeeper, etcd)

Re: [openstack-dev] [neutron] [tooz] DLM benchmark results

Were the backends (zookeeper, etcd) deployed in a cluster configuration? I can't quite tell from the doc. On Fri, Jul 22, 2016 at 12:58 AM, John Schwarz wrote: > You're right Joshua. > > Tooz HEAD points to 0f4e1198fdcbd6a29d77c67d105d201ed0fbd9e0. > > With regards to etcd

Re: [openstack-dev] [oslo.db] [CC neutron] CIDR overlap functionality and constraints

I think the one use case you missed is the bug for which it was being developed to fix: https://review.openstack.org/#/c/314054/ Currently we check for overlapping subnets on the same network in a lookup before creating the subnet, so two requests can race and get overlapping subnets committed to

Re: [openstack-dev] [Neutron] Proposing Jakub Libosvar for testingcore

+1 From: Oleg Bondarev To: "OpenStack Development Mailing List (not for usage questions)" Date: 22/07/2016 09:13 Subject:Re: [openstack-dev] [Neutron] Proposing Jakub Libosvar for testing

Re: [openstack-dev] [Neutron] Proposing Jakub Libosvar for testing core

+1 On Fri, Jul 22, 2016 at 2:36 AM, Doug Wiegley wrote: > +1 > > On Jul 21, 2016, at 5:13 PM, Kevin Benton wrote: > > +1 > > On Thu, Jul 21, 2016 at 2:41 PM, Carl Baldwin wrote: > >> +1 from me >> >> On Thu, Jul 21, 2016 at

Re: [openstack-dev] [cinder] [nova] os-brick privsep failures and an upgrade strategy?

Hi, What is the discussion result of privsep issue? When can we release next os-brick? Best wishes Lisa From: Ivan Kolodyazhny [mailto:e...@e0ne.info] Sent: Wednesday, July 13, 2016 9:55 PM To: OpenStack Development Mailing List (not for usage questions)

Re: [openstack-dev] [Neutron][oslo.db] Inspecting sqlite db during unit tests

Now that we have switched to oslo.db for test provisioning the responsibility of choosing a location lands here: https://github.com/openstack/oslo.db/blob/a79479088029e4fa51def91cb36bc652356462b6/oslo_db/sqlalchemy/provision.py#L505 The problem is that when you specify

Re: [openstack-dev] [neutron] [tooz] DLM benchmark results

You're right Joshua. Tooz HEAD points to 0f4e1198fdcbd6a29d77c67d105d201ed0fbd9e0. With regards to etcd and zookeeper's versions, they are: zookeeper-3.4.5+28-1.cdh4.7.1.p0.13.el6.x86_64, etcd-2.2.5-2.el7.0.1.x86_64. John. On Thu, Jul 21, 2016 at 8:14 PM, Joshua Harlow

[openstack-dev] [Horizon] On testing...

Hi all, > 2. We don't have enough higher-level (integration leve) test coverage for our newer angular interfaces. I previously wrote about new horizon integration autotests architecture and parallel mode: https://github.com/sergeychipiga/horizon_autotests. In this automated scope there are many

Re: [openstack-dev] [horizon] Midcycle Summary

We didn't discuss it explicitly, but I don't believe the decision has changed. We can remove it, but last I checked the patches in line to handle testing after deprecation still needed work. If they've been updated etc. I can look again. Rob On 22 July 2016 at 07:52, Matthias Runge

Re: [openstack-dev] [horizon] Midcycle Summary

On 21/07/16 19:40, Rob Cresswell wrote: > Hi everyone, > > We had the Horizon mid cycle meetup last week, and I wanted to highlight > some of the discussion and decisions made. > > Agenda: https://etherpad.openstack.org/p/horizon-newton-midcycle > Notes:

[openstack-dev] [daisycloud-core] Today(20160722)'s weekly meeting agenda

20160722 Agenda 1) roll call 2) Agenda bashing 3) Approved Wei (kong.w...@zte.com.cn) as daisycloud core reviewer 4) daisycloud status update 5) daisy4nfv status update 6) daisy4nfv disscussion in daisycloud channel B.R., Zhijiang ZTE

[openstack-dev] [devstack][neutron] - neutron gate blocked by devstack change

Hi all, The merge of https://review.openstack.org/#/c/343072/ unfortunately broke the linux bridge jobs so Neutron patches are currently blocked. I have a fix for the linux bridge settings ( https://review.openstack.org/345707) that I verified with a test patch in Neutron