[openstack-dev] [neutron] Bug deputy report week of October 15th

Hi, I was Neutron bug deputy last week. Below is a short summary about reported bugs. Note: I will not be at the team meeting this morning, sorry for the late notice. -Brian Critical bugs - None High bugs - * https://bugs.launchpad.net/neutron/+bug/1798472 -

Re: [openstack-dev] [neutron][stable] Stable Core Team Update

+1 from me :) -Brian On 10/02/2018 11:41 AM, Miguel Lavalle wrote: Hi Stable Team, I want to nominate Bernard Cafarrelli as a stable core reviewer for Neutron and related projects. Bernard has been increasing the number of stable reviews he is doing for the project [1]. Besides that, he is

Re: [openstack-dev] [neutron] subnet pool can not delete prefixes

On 09/26/2018 10:11 PM, wenran xiao wrote: Relation bug: https://bugs.launchpad.net/neutron/+bug/1792901 Any suggestion is welcome! Removing a prefix from a subnetpool is not supported, there was an inadvertent change to the client that made it seem possible. We are in the process of

Re: [openstack-dev] [neutron] Core status

On 09/19/2018 02:19 PM, Gary Kotton wrote: Hi, I have recently transitioned to a new role where I will be working on other parts of OpenStack. Sadly I do not have the necessary cycles to maintain my core responsibilities in the neutron community. Nonetheless I will continue to be involved.

Re: [openstack-dev] Appointing Slawek Kaplonski to the Neutron Drivers team

Congrats Slawek! On 08/27/2018 12:42 PM, Miguel Lavalle wrote: Dear Neutron team, In order to help the Neutron Drivers team to perform its very important job of guiding the community to evolve the OpenStack Networking architecture to meet the needs of our current and future users [1], I

Re: [openstack-dev] [neutron] Stable review

On 07/12/2018 02:53 AM, Takashi Yamamoto wrote: hi, queens branch of networking-midonet has had no changes merged since its creation. the following commit would tell you how many gate blockers have been accumulated. https://review.openstack.org/#/c/572242/ it seems the stable team doesn't have

[openstack-dev] [neutron] Bug deputy report

Hi, I was Neutron bug deputy last week. Below is a short summary about reported bugs. Critical bugs - None High bugs - * https://bugs.launchpad.net/neutron/+bug/1777908 - Ensure _get_changed_synthetic_fields() return updatable fields - breaks consumers - Boden

Re: [openstack-dev] [StarlingX] StarlingX code followup discussions

On 05/23/2018 02:00 PM, Jeremy Stanley wrote: On 2018-05-22 17:41:18 -0400 (-0400), Brian Haley wrote: [...] I read this the other way - the goal is to get all the forked code from StarlingX into upstream repos. That seems backwards from how this should have been done (i.e. upstream first

Re: [openstack-dev] [StarlingX] StarlingX code followup discussions

On 05/22/2018 04:57 PM, Jay Pipes wrote: Warning: strong opinions ahead. On 05/22/2018 02:54 PM, Dean Troyer wrote: Developers will need to re-create a repo locally in order to work or test the code and create reviews (there are more git challenges here). It would be challenging to do

[openstack-dev] [neutron] Bug deputy report

Hi, I was Neutron bug deputy last week. Below is a short summary about reported bugs. Critical bugs - None High bugs - * https://bugs.launchpad.net/bugs/1753504 - Remove mox/mox3 usage from testing Multiple people have taken ownership of fixing this *

Re: [openstack-dev] [tripleo] [neutron] Current containerized neutron agents introduce a significant regression in the dataplane

On 02/13/2018 05:08 PM, Armando M. wrote: On 13 February 2018 at 14:02, Brent Eagles > wrote: Hi, The neutron agents are implemented in such a way that key functionality is implemented in terms of haproxy, dnsmasq, keepalived

[openstack-dev] [neutron][all] nova_metadata_ip removal

Hi, As part of the normal deprecate/removal process, the 'nova_metadata_ip' option is being removed from neutron as it was replaced with 'nova_metadata_host' in the Pike cycle, https://review.openstack.org/#/c/518836/ Codesearch did find various repos still using the old value, so I posted

Re: [openstack-dev] [neutron] Metering can't count traffic for floating ip, or internal ip.

On 01/04/2018 09:50 PM, wenran xiao wrote: hi all， neutron metering can only count traffic that we send to *remote_ip*(egress), and *remote_ip* send to us(ingress), I think we should add method to count the traffic for floating ip or internal ip. Any suggestions is welcome. Neutron metering

Re: [openstack-dev] [neutron] performance issue between virtual networks

On 12/27/2017 08:39 AM, Kim-Norman Sahm wrote: Hi, i've detected a performance issue by accessing an floating ip in a different openstack network (same tenant). example: i have one tenant with two internal networks. each network has its own vrouter which is connectet to the extnet. the

Re: [openstack-dev] [TripleO] Tis the season...for a cloud reboot

On 12/19/2017 04:00 PM, Ben Nemec wrote: On 12/19/2017 02:43 PM, Brian Haley wrote: On 12/19/2017 11:53 AM, Ben Nemec wrote: The reboot is done (mostly...see below). On 12/18/2017 05:11 PM, Joe Talerico wrote: Ben - Can you provide some links to the ovs port exhaustion issue for some

Re: [openstack-dev] [TripleO] Tis the season...for a cloud reboot

On 12/19/2017 11:53 AM, Ben Nemec wrote: The reboot is done (mostly...see below). On 12/18/2017 05:11 PM, Joe Talerico wrote: Ben - Can you provide some links to the ovs port exhaustion issue for some background? I don't know if we ever had a bug opened, but there's some discussion of it in

Re: [openstack-dev] [neutron] Stepping down from core

Armando, It is sad to see you step down, just wanted to thank you for your leadership and hard work, both upstream and downstream, it's definitely made neutron a better project for everyone. Good luck wherever life takes you. -Brian On 12/15/2017 02:01 PM, Armando M. wrote: Hi neutrinos,

Re: [openstack-dev] [Neutron] Propose Slawek Kaplonski for Neutron core

+1 from me! On 11/29/2017 02:21 PM, Miguel Lavalle wrote: Hi Neutron Team, I want to nominate Slawek Kaplonski (irc: slaweq) to Neutron core. Slawek has been an active contributor to the project since the Mitaka cycle. He has been instrumental in the development of the QoS capabilities in

Re: [openstack-dev] [puppet][qa][ubuntu][neutron] Xenial Neutron Timeouts

On 10/30/2017 05:46 PM, Matthew Treinish wrote: From a quick glance at the logs my guess is that the issue is related to this stack trace in the l3 agent logs:

Re: [openstack-dev] [Neutron] Denver Team Dinner

+1 On 09/12/2017 10:44 PM, Ihar Hrachyshka wrote: +1 On Tue, Sep 12, 2017 at 9:44 PM, Kevin Benton wrote: +1 On Tue, Sep 12, 2017 at 8:50 PM, Sławek Kapłoński wrote: +1 — Best regards Slawek Kaplonski sla...@kaplonski.pl Wiadomość napisana

Re: [openstack-dev] [devstack] [ironic] [nova] Trying again on wait_for_compute in devstack

On 08/02/2017 07:17 AM, Sean Dague wrote: The 3 node scenarios in Neutron (which are still experimental nv) are typically failing to bring online the 3rd compute. In cells v2 you have to explicitly add nodes to the cells. There is a nova-manage command "discover-hosts" that takes all the compute

[openstack-dev] [all] Proposal to change integrated neutron grenade gate job to multi-node

Hi, While looking at ways to reduce the number of jobs we run in the Neutron gate, I found we ran two very similar jobs for some projects: gate-grenade-dsvm-neutron-ubuntu-xenial (single-node job) gate-grenade-dsvm-neutron-multinode-ubuntu-xenial (2-node job) We talked about this in the

[openstack-dev] [neutron][l3][dvr] Pike tasks and meeting consolidation

At the Summit a few of us met (Miguel, Swami and myself) to talk about our Pike tasks now that we have lost some resources. We came up with this short list, which can also be found on https://etherpad.openstack.org/p/neutron-l3-subteam : 1. Support for configuring Floating IPs on Centralized

Re: [openstack-dev] [neutron][all] So long, and thanks for all the fish

John, Thanks so much for all your work on a number of L3 items that wouldn't exist without you, IPv6 PD comes to mind :) It's been great working with you, good luck! -Brian On 05/02/2017 06:07 AM, John Davidge wrote: Friends and colleagues, It is with a heavy heart that I write to say my

Re: [openstack-dev] [neutron][networking-odl][qa] What's the recommended behavior for SG Rules with ethertype='IPv6' and protocol='icmp' ?

On 04/03/2017 09:23 PM, Ghanshyam Mann wrote: On Sun, Mar 26, 2017 at 9:31 PM, Sridhar Gaddam <sgad...@redhat.com <mailto:sgad...@redhat.com>> wrote: On Fri, Mar 24, 2017 at 7:27 PM, Brian Haley <haleyb@gmail.com <mailto:haleyb@gmail.com>> wrote:

Re: [openstack-dev] [neutron] - Adding Miguel Lavalle to neutron-drivers team

+1 for Miguel! On 03/30/2017 05:11 PM, Kevin Benton wrote: Hi, I would like to add Miguel Lavalle (mlavalle) to the Neutron drivers team [1]. Miguel has been instrumental in implemented features across Neutron and Nova (routed networks, DNS, etc) and is now leading the L3 team. He has a very

[openstack-dev] [neutron] No DVR meeting today

Both chairs have conflicts today, will resume the DVR meeting next week. Current work items and bugs can be found on the meeting page as usual, https://wiki.openstack.org/wiki/Meetings/Neutron-DVR -Brian __ OpenStack

Re: [openstack-dev] [neutron][networking-odl][qa] What's the recommended behavior for SG Rules with ethertype='IPv6' and protocol='icmp' ?

On 03/24/2017 06:41 AM, Ghanshyam Mann wrote: Hi All, Tempest is testing SG rule creation and pinging scenario tests with ethertype='IPv6' and protocol='icmp' [0]. In case of ethertype='IPv6', currently neutron accept protocol type as 'icmp', 'icmpv6' and 'ipv6-icmp' which again seems like

Re: [openstack-dev] [all] [goals] proposing a new goal: "Control Plane API endpoints deployment via WSGI"

On 01/12/2017 08:40 PM, Emilien Macchi wrote: Greetings OpenStack community, I have been looking for a Community Goal [1] that would directly help Operators and I found the "run API via WSGI" useful. So I've decided to propose this one as a goal for Pike but I'll stay open to postpone it to

Re: [openstack-dev] [neutron] proposing Miguel Lavalle as neutron core and Brian Haley as L3 Lt

and DHCP. At the same time, I'd like to propose Brian Haley as our next Chief L3 Officer. Both of them have worked with Carl Baldwin extensively and that can only be a guarantee of quality. Cheers, Armando [1] https://review.openstack.org/#/c/411531

Re: [openstack-dev] [neutron] proposing Ryan Tidwell and Nate Johnston as service LTs

+1 On 12/15/2016 06:58 PM, Armando M. wrote: Hi neutrinos, I would like to propose Ryan and Nate as the go-to fellows for service-related patches. Both are core in their repos of focus, namely neutron-dynamic-routing and neutron-fwaas, and have a good understanding of the service framework,

[openstack-dev] [Neutron][DVR] - No IRC Meeting until 2017

Hi Folks, We will not have another DVR sub-team meeting until 2017, resuming on January 4th, to accommodate those that will be away. Enjoy the break! -Brian __ OpenStack Development Mailing List (not for usage

Re: [openstack-dev] [neutron] Proposing Abhishek Raut as neutronclient core

+1 On 12/13/16 8:22 PM, Armando M. wrote: Hi folks, Abhishek Raut's recent involvement in OSC and python-neutronclient has helped moving a few efforts along in the right direction. I would like to suggest we double down on core firepower for the neutronclient repo alongside Akihiro [1]. This

Re: [openstack-dev] [neutron][tricircle]DVR issue in cross Neutron networking

Best Regards Chaoyi Huang (joehuang) From: Brian Haley [brian.ha...@hpe.com] Sent: 06 December 2016 10:29 To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [neutron][tricircle]DVR issue in cross Neutron networking

[openstack-dev] [Neutron][DVR] - No IRC Meeting this week

Hi Folks, We will not have a DVR sub-team meeting this week since neither Swami nor myself will be there to chair it. We will resume our meetings next week on December 14th. If you have any questions please ping us on IRC or send an email to the list.

Re: [openstack-dev] [neutron][tricircle]DVR issue in cross Neutron networking

On 12/5/16 3:03 AM, joehuang wrote: Hello, Hi Chaoyi, Comments inline below. Tricircle plans to provide L2 network across Neutron to ease supporting high availability of application: For example, in the following figure, the application is consisted of instance1 and instance2, these

Re: [openstack-dev] [neutron][octavia] Neutron LBaaS governance change and Octavia to the big tent

On 12/01/2016 08:54 AM, Ihar Hrachyshka wrote: Armando M. wrote: Hi folks, A few hours ago a governance change [1] has been approved by TC members. This means that from now on, the efforts for Load Balancing as a Service efforts rest officially in the hands of the Octavia

Re: [openstack-dev] [Neutron] Stepping down from core

Hi Carl, Thanks for all the hard work, Neutron is definitely better because of it. Hope to work with you again some day. Good luck with your new endeavor! -Brian On 11/17/2016 01:42 PM, Carl Baldwin wrote: Neutron (and Openstack), It is with regret that I report that my work situation

Re: [openstack-dev] [neutron] OVS agent reports error "ovs-ofctl: br-int is not a bridge or a socket"

On 11/17/2016 03:14 AM, zhi wrote: Hi, all I build a devstack which code from master branch. By default the OVS version is 2.0.2 when install devstack. So I reinstall the OVS 2.6.0. I meet an exception in OVS agent when all OVS services runs okay. Exception shows below: 2016-11-17

Re: [openstack-dev] [neutron][trunk-port] OVS tbr bridge wasn't be created by OVS agent

On 11/15/16 5:12 AM, zhi wrote: Sorry, I forgot to say my local environment is Liberty. :) According to the blueprint and reviews this didn't land until Newton, maybe some in Mitaka, so I wouldn't expect it to work in Liberty. -Brian 2016-11-15 18:07 GMT+08:00 zhi

Re: [openstack-dev] [neutron] HostNotCompatibleWithFixedIps exception happens when setting router's gateway.

Hi Zhi, Thanks for the report, comment below. On 10/27/2016 05:04 AM, zhi wrote: Hi, all. I installed a devstack in my local environment. All the code from master branch. After the installation, I have to show you some problems which I met. First of all, I create an external network

Re: [openstack-dev] [all] running non-devstack jobs in Python projects aka "it works outside devstack"

On 10/14/2016 05:53 PM, Clark Boylan wrote: On Thu, Oct 13, 2016, at 05:47 PM, Emilien Macchi wrote: Greetings OpenStack, == Background Since the beginning of OpenStack (or almost), devstack has been used as a common tool to deploy OpenStack in CI environment. Most of OpenStack projects (if

Re: [openstack-dev] floating IP is DOWN

On 09/22/2016 10:19 AM, Barber, Ofer wrote: when i assign a floating IP to a server, i see that the status of the floating IP is "down" why is that so ? *_code:_* LOG.info("\n<== float IP address: %s and status: %s ==>" % (float_ip['floating_ip_address'],float_ip['status']))

Re: [openstack-dev] [Neutron] Adding ihrachys to the neutron-drivers team

Congrats Ihar! -Brian On 09/17/2016 12:40 PM, Armando M. wrote: Hi folks, I would like to propose Ihar to become a member of the Neutron drivers team [1]. Ihar wide knowledge of the Neutron codebase, and his longstanding duties as stable core, downstream package whisperer, release and oslo

Re: [openstack-dev] [infra][neutron] IPv6 gate issue in OSIC cloud

On 08/24/2016 04:52 PM, Brian Haley wrote: Hi, Starting sometime earlier in the week, gate jobs started failing that were running in the OSIC cloud, due to a loss of connectivity to VMs running there when Neutron L3 was configured. I wanted to send some information out on what we found in case

[openstack-dev] [infra][neutron] IPv6 gate issue in OSIC cloud

Hi, Starting sometime earlier in the week, gate jobs started failing that were running in the OSIC cloud, due to a loss of connectivity to VMs running there when Neutron L3 was configured. I wanted to send some information out on what we found in case other deployment tools trip over the

Re: [openstack-dev] [all] devstack changing to neutron by default RSN

On 08/05/2016 02:32 PM, Armando M. wrote: > > Looking at the health trend for DVR [1], the test hasn't failed in a > while, so I wonder if this is induced by the proposed switch, even > though I can't correlate it just yet (still waiting for caffeine to kick

Re: [openstack-dev] [all] devstack changing to neutron by default RSN

On 08/05/2016 08:59 AM, Sean Dague wrote: On 08/04/2016 09:15 PM, Armando M. wrote: So glad we are finally within the grasp of this! I posted [1], just to err on the side of caution and get the opportunity to see how other gate jobs for Neutron might be affected by this change. Are there any

Re: [openstack-dev] [Neutron] stable/liberty busted

On 08/04/2016 03:25 PM, Brian Haley wrote: On 08/04/2016 03:16 PM, Rick Jones wrote: On 08/04/2016 12:04 PM, Kevin Benton wrote: Yeah, I wasn't thinking when I +2'ed that. There are two use cases for the pinger, one for ensuring continuous connectivity and one for eventual connectivity. I

Re: [openstack-dev] [Neutron] stable/liberty busted

On 08/04/2016 03:16 PM, Rick Jones wrote: On 08/04/2016 12:04 PM, Kevin Benton wrote: Yeah, I wasn't thinking when I +2'ed that. There are two use cases for the pinger, one for ensuring continuous connectivity and one for eventual connectivity. I think the revert is okay for a quick fix, but

Re: [openstack-dev] [Neutron] stable/liberty busted

On 08/04/2016 01:36 PM, Armando M. wrote: Hi Neutrinos, I have noticed that Liberty seems to be belly up [1]. I wonder if anyone knows anything or has the time to look into it. Many thanks, Armando [1] https://review.openstack.org/#/c/349039/ This could be due to this backport;

Re: [openstack-dev] [neutron][dvr][fip] fg device allocated private ip address

Wrote: Yes, as Brian says this will be covered by the follow-up patch to [2] which I¹m currently working on. Thanks for the question. John On 8/1/16, 3:17 PM, "Brian Haley" <brian.ha...@hpe.com> wrote: >On 07/31/2016 06:27 AM, huangdenghui wrote: &g

Re: [openstack-dev] [nova] Belated nova newton midcycle recap (part 2)

On 08/01/2016 10:15 PM, Matt Riedemann wrote: Starting from where I accidentally left off: We also talked a bit about live migration with Neutron. There has been a fix up for live migration + DVR since Mitaka: https://review.openstack.org/#/c/275073 It's a bit of a hacky workaround but

Re: [openstack-dev] [neutron][dvr][fip] fg device allocated private ip address

On 07/31/2016 06:27 AM, huangdenghui wrote: Hi Now we have spec named subnet service types, which provides a capability of allowing different port of a network to allocate ip address from different subnet. In current implementation of DVR, fip also is distributed on every compute node,

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

+1 On 07/22/2016 04:12 AM, Oleg Bondarev wrote: +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

[openstack-dev] [Neutron][DVR] - No IRC Meeting today

Hi Folks, Sorry for the late notice, but we will not have a DVR sub-team meeting today since neither Swami nor myself will be there to chair it. We will resume our meetings next week on July 20th. If you have any questions please ping us on IRC or send an email to the list.

[openstack-dev] [Neutron][DVR] - No IRC Meeting this week

Hi Folks, We will not have a DVR sub-team meeting this week since neither Swami nor myself will be there to chair it. We will resume our meetings next week on July 6th. If you have any questions please ping us on IRC or send an email to the list.

Re: [openstack-dev] [Neutron] Question about service subnets spec

Thanks Carl for bringing this up, comments below. On 05/26/2016 02:04 PM, Carl Baldwin wrote: Hi folks, Some (but not all) of you will remember a discussion we had about service subnets at the last mid-cycle. We've been iterating a little bit on a spec [1] and we have just one issue that we'd

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

On 05/24/2016 11:17 AM, Ihar Hrachyshka wrote: On 17 May 2016, at 13:07, 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): mitaka: 19 reviews;

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

Ihar, Thanks for the nomination, I'll just chime-in below. On 05/19/2016 03:13 PM, Ihar Hrachyshka wrote: On 19 May 2016, at 13:18, Tony Breeds wrote: On Thu, May 19, 2016 at 10:49:26AM +0200, Ihar Hrachyshka wrote: On 19 May 2016, at 02:12, Tony Breeds

Re: [openstack-dev] Timeframe for naming the P release?

On 05/02/2016 02:53 PM, Shamail Tahir wrote: Hi everyone, When will we name the P release of OpenStack? We named two releases simultaneously (Newton and Ocata) during the Mitaka release cycle. This gave us the names for the N (Mitaka), N+1 (Newton), and N+2 (Ocata) releases. If we were to

Re: [openstack-dev] [neutron] Social at the summit

+1 On 4/25/16 1:07 PM, Kyle Mestery wrote: OK, there is enough interest, I'll find a place on 6th Street for us and get a reservation for Thursday around 7 or so. Thanks folks! On Mon, Apr 25, 2016 at 12:30 PM, Zhou, Han wrote: +1 :) Han Zhou Irc: zhouhan On Monday,

Re: [openstack-dev] [Neutron] Proposing Hirofumi Ichihara to Neutron Core Reviewer Team

+1 On 4/8/16 6:58 AM, Henry Gessau wrote: +1, Hirofumi will make a great addition. Akihiro Motoki wrote: Hi Neutrinos, As the API Lieutenant of Neutron team, I would like to propose Hirofumi Ichihara (irc: hichihara) as a member of Neutron core reviewer team mainly

Re: [openstack-dev] [Neutron] Segments, subnet types, and IPAM

at tags are pretty new and are a moving target. Another reason I was hesitant is that tags were designed to be user facing. As I recall, we didn't want the tags to affect code behavior. But, maybe I misunderstood that. We want service types to affect IPAM, at least. Brian Haley is going to put up a spec

Re: [openstack-dev] [all] Maintaining httplib2 python library

On 03/17/2016 06:04 PM, Doug Wiegley wrote: Here is the non comprehensive list of usages based on what trees I happen to have checked out (which is quite a few, but not all of OpenStack for sure). I think before deciding to take over ownership of an upstream lib (which is a large commitment

Re: [openstack-dev] [Heat][Neutron] Mitaka RC1 available

On 03/17/2016 09:13 PM, Armando M. wrote: On 18 March 2016 at 00:16, Jeremy Stanley > wrote: On 2016-03-17 09:44:59 +0530 (+0530), Armando M. wrote: > Unfortunately, Neutron is also going to need an RC2 due to > upstream CI issues

[openstack-dev] [Neutron][DVR] No Meeting tomorrow

Sorry for the late notice, but I need to cancel the DVR meeting for tomorrow the 9th as a few of us have a conflict. We'll resume again next week on the 16th. -Brian __ OpenStack Development Mailing List (not for usage

Re: [openstack-dev] [devstack] stack.sh keeps failing with RTNETLINK answers: Network is unreachable

On 02/26/2016 03:48 AM, Paul Carlton wrote: Sean Don't think unstack failed, when I manually create the device ( sudo ovs-vsctl --no-wait -- --may-exist add-br br-ex) unstack.sh removes it. sudo ip route show default via 172.18.20.1 dev eth0 169.254.169.254 via 172.18.20.2 dev eth0

Re: [openstack-dev] [Neutron] Intra-column wrapping in python-neutronclient

On 2/24/16 3:58 PM, Steve Baker wrote: On 25/02/16 06:23, Carl Baldwin wrote: Hi, I've noticed a new behavior from the python-neutronclient which disturbs me. For me, this just started happening with my latest build of devstack which I built yesterday. It didn't happen with another recent

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

configurations as an in-tree test. Brian Haley has a patch up from Dec. that was trying to clean it up: https://review.openstack.org/#/c/239868/ I just updated that to mark six of the eight tests as "slow" per your previous comment, such that only the dual-NIC/dual-stack tes

Re: [openstack-dev] [neutron] gate-neutron-dsvm-api failures

On 01/14/2016 05:42 PM, John Davidge (jodavidg) wrote: The neutron.tests.api.admin.test_floating_ips_admin_actions.FloatingIPAdminTestJSON test has been consistently failing for patch https://review.openstack.org/#/c/258754/ and I don’t see how they can be related. This patch has been trying to

Re: [openstack-dev] [neutron] Testing Neutron with latest OVS

On 1/14/16 9:28 AM, Russell Bryant wrote: The consensus I'm picking up roughly is that for those working on the features, testing with source builds seems to be working fine. It's just not something anyone wants to gate the main Neutron repo with. That seems quite reasonable. If the features

Re: [openstack-dev] [OpenStack-Infra] Gerrit Upgrade to ver 2.11, completed.

On 2015-12-16 16:24, openstack-dev-requ...@lists.openstack.org wrote: Thanks to everyone for their patience while we upgraded to Gerrit 2.11. I'm happy to announce that we were able to successfully completed this task at around 21:00 UTC. You may hack away once more. If you encounter any

Re: [openstack-dev] [openstack]host not reachable with iptables reject after init

On 11/09/2015 09:55 AM, Wilence Yao wrote: Hi all, After I run devstack/stack.sh completely, I found that api is not reachable. After some check, I found some iptables rules cause the problem: ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 state NEW tcp

[openstack-dev] [Neutron] Weekly DVR Meeting starting next week

A few of us had a discussion this week at Summit and decided to re-start the weekly Neutron Distributed Virtual Router (DVR) meeting. The goal is to help: - Stabilize DVR - fix the bugs - Address performance/scalability issues - Get the DVR jobs voting again Meetings will be on Wednesdays

Re: [openstack-dev] [neutron] PTL Non-Candidacy

On 09/12/2015 01:14 PM, Armando M. wrote: On 12 September 2015 at 18:38, Gary Kotton > wrote: Thanks! You did a great job. Looking back you made some very tough and healthy decisions. Neutron has a new lease on life! It is tradition

Re: [openstack-dev] [Neutron][L3] [API]: API to get the list of router ports

On 08/13/2015 04:04 AM, Padmanabhan Krishnan wrote: Hello, Is there a Neutron public API to get the list of router ports? Something similar to what the command neutron router-port-list {tenant} gives. router-port-list takes a router as an argument, not a tenant. I wasn't able to find one in

Re: [openstack-dev] [Neutron] What are problems of Distributed SNAT?

On 07/24/2015 08:17 AM, Miyagishi, Takanori wrote: Dear Carl, Thank you for your information! I checked the etherpad, and I propose a new idea of Distributed SNAT implementation. Following figure is my idea, Shared SNAT Address per Tenant per Compute Node. I think this is the One IP Address

Re: [openstack-dev] [Neutron] Proposing Cedric Brandily to Neutron Core Reviewer Team

+1 On 07/15/2015 02:47 PM, Carl Baldwin wrote: As the Neutron L3 Lieutenant along with Kevin Benton for control plane, and Assaf Muller for testing, I would like to propose Cedric Brandily as a member of the Neutron core reviewer team under these areas of focus. Cedric has been a long time

Re: [openstack-dev] [neutron] - Proposing Miguel Angel Ajo for the Control Plane core team

Big +1 On 07/06/2015 06:02 AM, Kevin Benton wrote: Hello! As the Lieutenant of the built-in control plane[1], I am proposing to add Miguel Angel Ajo to the control plane core reviewer team. His review stats are inline with the other core reviewers[2], and his work on improving the

Re: [openstack-dev] Proposing Brian Haley to Neutron L3 Core Reviewer Team

. Carl On Wed, Jun 10, 2015 at 1:11 PM, Carl Baldwin c...@ecbaldwin.net mailto:c...@ecbaldwin.net wrote: Folks, As the Neutron L3 Lieutenant [1] under the PTL, Kyle, I'd like to propose Brian Haley as a member of the Neutron L3 core reviewer team. Brian

Re: [openstack-dev] [neutron] - dnsmasq 'dhcp-authoritative' option broke multiple DHCP servers

On 05/26/2015 01:12 PM, Salvatore Orlando wrote: From the bug Kevin reported it seems multiple dhcp agents per network have been completely broken by the fix for bug #1345947, so a revert of patch [1] (and stable backports) should probably be the first thing to do - if nothing else because the

Re: [openstack-dev] [nova][neutron]Fail to communicate new host when the first host for a new instance fails

On 05/14/2015 05:29 AM, Neil Jerram wrote: Hi all, this is about a problem I'm seeing with my Neutron ML2 mechanism driver [1]. I'm expecting to see an update_port_postcommit call to signal that the binding:host_id for a port is changing, but I don't see that. The scenario is launching a new

Re: [openstack-dev] [Neutron] Success of the IPv6 Subteam - Proposal to disband

On 05/04/2015 08:37 PM, Sean M. Collins wrote: It is a bittersweet moment - I am proposing that due to the amazing success that we have had as a subteam, that because we have accomplished so much, that it makes sense for our team to disband and re-integrate with other subteams (the L3 subteam

Re: [openstack-dev] [Neutron] Deprecating the use_namespaces option - Now's the time to speak up!

On 03/20/2015 02:57 PM, Assaf Muller wrote: Hello everyone, The use_namespaces option in the L3 and DHCP Neutron agents controls if you can create multiple routers and DHCP networks managed by a single L3/DHCP agent, or if the agent manages only a single resource. Are the setups out

Re: [openstack-dev] [neutron] OpenFlow security groups (pre-benchmarking plan)

On 02/25/2015 08:52 AM, Miguel Ángel Ajo wrote: I’m writing a plan/script to benchmark OVS+OF(CT) vs OVS+LB+iptables+ipsets, so we can make sure there’s a real difference before jumping into any OpenFlow security group filters when we have connection tracking in OVS. The plan is to keep all

Re: [openstack-dev] [neutron] IPv6 Status

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/05/2015 05:38 AM, Ihar Hrachyshka wrote: On 02/05/2015 09:14 AM, Andreas Scheuring wrote: Hi, is there a central place where I can find a matrix (or something similar) that shows what is currently supposed to work in the sense of IPv6

Re: [openstack-dev] [neutron] high dhcp lease times in neutron deployments considered harmful (or not???)

, Feb 2, 2015 at 8:57 AM, Brian Haley brian.ha...@hp.com mailto:brian.ha...@hp.com wrote: Kevin, I think we are finally converging. One of the points I've been trying to make is that users are playing with fire when they start playing with some of these port attributes

Re: [openstack-dev] [neutron] high dhcp lease times in neutron deployments considered harmful (or not???)

. I'm fine with adding Option 58, even though it only lessens the effect of this problem, doesn't truly fix it, and might not work with all clients (like in Cirros). -Brian On Fri, Jan 30, 2015 at 8:00 AM, Brian Haley brian.ha...@hp.com mailto:brian.ha...@hp.com wrote: Kevin, The only thing

Re: [openstack-dev] [neutron] high dhcp lease times in neutron deployments considered harmful (or not???)

-time I am proposing, you are still opposed to setting it to anything low because of logging and the ~24 bps background DHCP traffic per VM? On Thu, Jan 29, 2015 at 7:11 PM, Brian Haley brian.ha...@hp.com mailto:brian.ha...@hp.com wrote: On 01/29/2015 05:28 PM, Kevin Benton wrote

Re: [openstack-dev] [neutron] high dhcp lease times in neutron deployments considered harmful (or not???)

On 01/29/2015 03:55 AM, Kevin Benton wrote: Why would users want to change an active port's IP address anyway? Re-addressing. It's not common, but the entire reason I brought this up is because a user was moving an instance to another subnet on the same network and stranded one of their

Re: [openstack-dev] [neutron] high dhcp lease times in neutron deployments considered harmful (or not???)

the secondary keyword on Cisco devices. Or just the ip addr add command on linux. On Thu, Jan 29, 2015 at 1:34 PM, Brian Haley brian.ha...@hp.com mailto:brian.ha...@hp.com wrote: On 01/29/2015 03:55 AM, Kevin Benton wrote: Why would users want to change an active port's IP address anyway

Re: [openstack-dev] [neutron] high dhcp lease times in neutron deployments considered harmful (or not???)

Hi Kevin, On 01/28/2015 03:50 AM, Kevin Benton wrote: Hi, Approximately a year and a half ago, the default DHCP lease time in Neutron was increased from 120 seconds to 86400 seconds.[1] This was done with the goal of reducing DHCP traffic with very little discussion (based on what I can

Re: [openstack-dev] [neutron] iptables routes are not being injected to router namespace

On Thu, Jan 22, 2015 at 9:07 AM, Brian Haley brian.ha...@hp.com mailto:brian.ha...@hp.com wrote: On 01/22/2015 10:17 AM, Carl Baldwin wrote: I think this warrants a bug report. Could you file one with what you know so far? Carl, Seems as though a recent change

Re: [openstack-dev] [neutron] iptables routes are not being injected to router namespace

. Then the change in the other patchset could be applied, along with a test that triggers exceptions so this gets caught. Thanks, -Brian On Thu, Jan 22, 2015 at 10:32 AM, Brian Haley brian.ha...@hp.com mailto:brian.ha...@hp.com wrote: On 01/22/2015 01:06 PM, Kevin Benton wrote: There was a bug

Re: [openstack-dev] [neutron] iptables routes are not being injected to router namespace

On Wed, Jan 21, 2015 at 2:24 PM, Brian Haley brian.ha...@hp.com wrote: On 01/21/2015 02:29 PM, Xavier León wrote: On Tue, Jan 20, 2015 at 10:32 PM, Brian Haley brian.ha...@hp.com wrote: On 01/20/2015 09:20 AM, Xavier León wrote: Hi all, we've been doing some tests with openstack kilo

Re: [openstack-dev] [neutron] iptables routes are not being injected to router namespace

On 01/21/2015 02:29 PM, Xavier León wrote: On Tue, Jan 20, 2015 at 10:32 PM, Brian Haley brian.ha...@hp.com wrote: On 01/20/2015 09:20 AM, Xavier León wrote: Hi all, we've been doing some tests with openstack kilo and found out a problem: iptables routes are not being injected to the router

Re: [openstack-dev] [neutron] iptables routes are not being injected to router namespace

On 01/20/2015 09:20 AM, Xavier León wrote: Hi all, we've been doing some tests with openstack kilo and found out a problem: iptables routes are not being injected to the router namespace. Scenario: - a private network NOT connected to the outside world. - a router with only one

Re: [openstack-dev] [nova] Networks are not cleaned up in build failure

On 01/15/2015 12:55 PM, Andrew Laski wrote: On 01/15/2015 09:33 AM, Brian Haley wrote: On 01/14/2015 02:15 PM, Andrew Laski wrote: On 01/14/2015 12:57 PM, Murray, Paul (HP Cloud) wrote: Hi All, I recently experienced failures getting images from Glance while spawning instances. This step

Re: [openstack-dev] [nova] Networks are not cleaned up in build failure

On 01/14/2015 02:15 PM, Andrew Laski wrote: On 01/14/2015 12:57 PM, Murray, Paul (HP Cloud) wrote: Hi All, I recently experienced failures getting images from Glance while spawning instances. This step comes after building the networks in the guild sequence. When the Glance failure

  1   2   >