Re: [openstack-dev] [stable][octavia] Backport patch adding new configuration options

On Mon, Oct 8, 2018 at 12:34 PM Matt Riedemann wrote: > > On 10/8/2018 11:05 AM, Carlos Goncalves wrote: > > The Octavia team merged a patch in master [1] that fixed an issue where > > load balancers could be deleted whenever queue_event_streamer driver is > > enabled and RabbitMQ goes down [2].

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

On Mon, Aug 27, 2018 at 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 have

Re: [openstack-dev] [neutron] neutron ipv6 radvd sends out link-local or nothing as def gw (L3 HA issue?)

On Mon, Aug 20, 2018 at 6:06 AM, Tobias Urdin wrote: > When I removed those ips and set accept_ra to 0 on the backup router: > > ip netns exec qrouter-0775785e-a93a-4501-917b-be92ff03f36a sysctl -w > net.ipv6.conf.qr-7fad6b1b-c9.accept_ra=0 > ip netns exec

Re: [openstack-dev] [tc][all] A culture change (nitpicking)

On Tue, May 29, 2018 at 12:41 PM, Mathieu Gagné wrote: > Hi Julia, > > Thanks for the follow up on this topic. > > On Tue, May 29, 2018 at 6:55 AM, Julia Kreger > wrote: >> >> These things are not just frustrating, but also very inhibiting for >> part time contributors such as students who may

Re: [openstack-dev] [neutron] [OVN] L3 traffic

On Tue, Feb 13, 2018 at 11:24 PM, Numan Siddique <nusid...@redhat.com> wrote: > > > On Wed, Feb 14, 2018 at 4:19 AM, Assaf Muller <as...@redhat.com> wrote: >> >> I'm not aware of plans for OVN to supported distributed SNAT, therefor >> a networking node wil

Re: [openstack-dev] [neutron] [OVN] L3 traffic

I'm not aware of plans for OVN to supported distributed SNAT, therefor a networking node will still be required for the foreseeable future. On Mon, Jan 15, 2018 at 2:18 AM, wenran xiao wrote: > Hey all, > I have found Network OVN will support to distributed floating ip >

Re: [openstack-dev] [neutron] Generalized issues in the unit testing of ML2 mechanism drivers

On Wed, Dec 13, 2017 at 7:30 AM, Michel Peterson wrote: > Through my work in networking-odl I've found what I believe is an issue > present in a majority of ML2 drivers. An issue I think needs awareness so > each project can decide a course of action. > > The issue stems from

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

On Fri, Dec 15, 2017 at 2:01 PM, Armando M. wrote: > Hi neutrinos, > > To some of you this email may not come as a surprise. > > During the past few months my upstream community engagements have been more > and more sporadic. While I tried hard to stay committed and fulfill my

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

On Thu, Dec 7, 2017 at 2:55 AM, Sławomir Kapłoński wrote: > Hi, > > Thanks all of You for support. I'm very happy to be part of the team. Congratulations Slawek, and job well done! > > — > Best regards > Slawek Kaplonski > sla...@kaplonski.pl > > >> Wiadomość napisana przez

Re: [openstack-dev] [Networking-OVN] Unable to run OVN functional tests

On Sat, Aug 19, 2017 at 3:02 PM, Trinath Somanchi wrote: > Hi- > > > > Using [1] I have enabled devstack setup. > > > > Now that when I try dvsm-functional tests, I get all tests failed. > > > > Please find the error log [2] help me resolve this issue. > > > > Also,

Re: [openstack-dev] [neutron][l3] Conntrackd in L3 HA ?

On Fri, Apr 14, 2017 at 3:16 AM, zhi wrote: > hi, all. > > I have a question about conntrackd in L3 HA. I read document about L3 HA > at [1] and I find " conntrack " in L3 HA diagram . Does neutron L3 HA > support conntrackd currently? If so, how > can I find the

Re: [openstack-dev] [tripleo] pingtest vs tempest

On Wed, Apr 5, 2017 at 4:49 PM, Emilien Macchi wrote: > Greetings dear owls, > > I would like to bring back an old topic: running tempest in the gate. > > == Context > > Right now, TripleO gate is running something called pingtest to > validate that the OpenStack cloud is

Re: [openstack-dev] [Neutron] Alternative approaches for L3 HA

On Wed, Feb 22, 2017 at 1:40 PM, Miguel Angel Ajo Pelayo wrote: > I have updated the spreadsheet. In the case of RH/RDO we're using the same > architecture > in the case of HA, pacemaker is not taking care of those anymore since the > HA-NG implementation. > > We let systemd

Re: [openstack-dev] [Neutron] Alternative approaches for L3 HA

On Fri, Feb 10, 2017 at 12:27 PM, Anna Taraday wrote: > Hello everyone! > > In Juno in Neutron was implemented L3 HA feature based on Keepalived (VRRP). > During next cycles it was improved, we performed scale testing [1] to find > weak places and tried to fix them.

Re: [openstack-dev] [Neutron][Dynamic Routing] Plans for scenario testing?

the driver interface somehow. I'm > open to suggestions as to how to approach this. > > -Ryan > > -Original Message- > From: Assaf Muller [mailto:as...@redhat.com] > Sent: Tuesday, December 06, 2016 2:36 PM > To: OpenStack Development Mailing List (not for usage que

[openstack-dev] [Neutron][Dynamic Routing] Plans for scenario testing?

Hi all, General query - Is there anyone in the Dynamic Routing community that is planning on contributing a scenario test? As far as I could tell, none of the current API tests would fail if, for example, the BGP agent was not running. Please correct me if I'm wrong. Thank you.

[openstack-dev] [neutron] Stepping down as testing lieutenant and from the core & drivers teams

Hi all, For the past few months I've been gaining more responsibilities within Red Hat. I have less time to dedicate to personal contribution and it's had a considerable tole on my ability to perform my duties upstream to the degree of effectiveness I am satisfied with. To that end, I've decided

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

On Thu, Nov 17, 2016 at 1:42 PM, Carl Baldwin wrote: > Neutron (and Openstack), > > It is with regret that I report that my work situation has changed such that > I'm not able to keep up with my duties as a Neutron core reviewer, L3 > lieutenant, and drivers team member. My

Re: [openstack-dev] [neutron]Do we need to rfe to implement active-active router?

On Wed, Nov 16, 2016 at 10:42 AM, huangdenghui wrote: > hi > Currently, neutron support DVR router and legacy router. For high > availability, there is HA router in reference implementation of legacy mode > and DVR mode. I am considering whether is active-active router

Re: [openstack-dev] [neutron] Ocata End user and operator feedback recap

On Tue, Nov 8, 2016 at 12:57 AM, Oleg Bondarev wrote: > > > On Tue, Nov 8, 2016 at 12:22 AM, Carl Baldwin wrote: >> >> Ocata End user and operator feedback recap >> >> >> The purpose of this

Re: [openstack-dev] [neutron] bug deputy report

On Mon, Oct 3, 2016 at 10:15 AM, Ihar Hrachyshka wrote: > Hi all, > > I was serving as a bug deputy for the last two weeks. (Well, I planned to > serve for one week only, but then I forgot to set new deputies in the last > meeting I chaired, so the 2nd week was my punishment

Re: [openstack-dev] [QA][infra][all] Measuring code coverage in integration tests

On Thu, Sep 29, 2016 at 5:27 AM, milanisko k <vetri...@gmail.com> wrote: > > > út 27. 9. 2016 v 20:12 odesílatel Assaf Muller <as...@redhat.com> napsal: > >> On Tue, Sep 27, 2016 at 2:05 PM, Assaf Muller <as...@redhat.com> wrote: >> >>> >>&

Re: [openstack-dev] [QA][infra][all] Measuring code coverage in integration tests

On Tue, Sep 27, 2016 at 2:05 PM, Assaf Muller <as...@redhat.com> wrote: > > > On Tue, Sep 27, 2016 at 12:18 PM, Timur Nurlygayanov < > tnurlygaya...@mirantis.com> wrote: > >> Hi milan, >> >> we have measured the test coverage for OpenStack components

Re: [openstack-dev] [QA][infra][all] Measuring code coverage in integration tests

On Tue, Sep 27, 2016 at 12:18 PM, Timur Nurlygayanov < tnurlygaya...@mirantis.com> wrote: > Hi milan, > > we have measured the test coverage for OpenStack components with > coverage.py tool [1]. It is very easy tool and it allows measure the > coverage by lines of code and etc. (several metrics

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

Well deserved is an understatement! Ihar is consistently integral to the Neutron project. Ihar has wide knowledge not only of Neutron but of OpenStack workings and is a key factor to Neutron playing nice with other projects. Ihar has shown consistent good judgement of priorities and will in no

Re: [openstack-dev] [neutron] neutronclient check queue is broken

On Thu, Aug 25, 2016 at 6:58 AM, Ihar Hrachyshka wrote: > Akihiro Motoki wrote: > >> In the neutronclient check queue, >> gate-neutronclient-test-dsvm-functional is broken now [1]. >> Please avoid issuing 'recheck'. >> >> [1]

Re: [openstack-dev] [Neutron][LBaaS][heat] Removing LBaaS v1 - are weready?

On Thu, Aug 25, 2016 at 7:35 AM, Gary Kotton wrote: > Hi, > At the moment it is still not clear to me the upgrade process from V1 to V2. > The migration script https://review.openstack.org/#/c/289595/ has yet to be > approved. Does this support all drivers or is this just

Re: [openstack-dev] [neutron][networking-ovs-dpdk] conntrack security group driver with ovs-dpdk

+ Jakub. On Wed, Aug 10, 2016 at 9:54 AM, wrote: > Hi, >> [Mooney, Sean K] >> In ovs 2.5 only linux kernel conntrack was supported assuming you had a 4.x >> kernel that supported it. that means that the feature was not available on >> bsd,windows or with

Re: [openstack-dev] [Neutron] SFC stable/mitaka version

On Thu, Jul 28, 2016 at 3:02 PM, Cathy Zhang wrote: > Hi Ihar and all, > > Yes, we have been preparing for such a release. We will do one more round of > testing to make sure everything works fine, and then I will submit the > release request. > There is a new patch on

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

gt;> On Jul 21, 2016, at 5:13 PM, Kevin Benton <ke...@benton.pub >>> <mailto:ke...@benton.pub>> wrote: >>> >>> +1 >>> >>> On Thu, Jul 21, 2016 at 2:41 PM, Carl Baldwin <c...@ecbaldwin.net >>> <mailto:c...@ecba

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

As Neutron's so called testing lieutenant I would like to propose Jakub Libosvar to be a core in the testing area. Jakub has demonstrated his inherent interest in the testing area over the last few years, his reviews are consistently insightful and his numbers [1] are in line with others and I

Re: [openstack-dev] [lbaas]HA for lbaas v2 agent

o implementations you're going with. There's a bunch of summit sessions about Octavia you can look in to. > > Thanks > Akshay > > On Thu, Jun 23, 2016 at 1:00 AM, Assaf Muller <as...@redhat.com> wrote: >> >> On Wed, Jun 22, 2016 at 3:17 PM, Akshay Kumar Sanghai >

Re: [openstack-dev] [lbaas]HA for lbaas v2 agent

On Wed, Jun 22, 2016 at 3:17 PM, Akshay Kumar Sanghai wrote: > Hi, > I have a multinode openstack installation (3 controller, 3 network nodes, > and some compute nodes). > Like l3 agent, is high availability feature available for the lbaas v2 > agent? It is not. Nir

Re: [openstack-dev] [openstack-ansible] L3HA problem

On Wed, Jun 22, 2016 at 12:02 PM, fabrice grelaud <fabrice.grel...@u-bordeaux.fr> wrote: > > Le 22 juin 2016 à 17:35, fabrice grelaud <fabrice.grel...@u-bordeaux.fr> a > écrit : > > > Le 22 juin 2016 à 15:45, Assaf Muller <as...@redhat.com> a écrit : > >

Re: [openstack-dev] [openstack-ansible] L3HA problem

On Wed, Jun 22, 2016 at 9:24 AM, fabrice grelaud wrote: > Hi, > > we deployed our openstack infrastructure with your « exciting » project > openstack-ansible (mitaka 13.1.2) but we have some problems with L3HA after > create router. > > Our infra (closer to the

Re: [openstack-dev] [TripleO] Consolidating TripleO validations with Browbeat validations

On Mon, Jun 20, 2016 at 12:43 PM, Joe Talerico wrote: > On Mon, Jun 20, 2016 at 12:41 PM, Ihar Hrachyshka wrote: >> >>> On 20 Jun 2016, at 18:37, Joe Talerico wrote: >>> >>> Hello - It would seem there is a little bit of overlap

Re: [openstack-dev] [kolla] our 3 voting processes in detail

On Fri, Jun 17, 2016 at 9:41 PM, Gerard Braad wrote: > Thanks Steve, > > > Very useful. Would be great if for future reference we would only need > to pint people to an URL on the Wiki for instance... what do you > think? I would recommend in-tree policies .rsts instead of Wiki

Re: [openstack-dev] [Neutron] Stable/liberty breakage

On Wed, Jun 15, 2016 at 2:59 PM, Ihar Hrachyshka wrote: > >> On 15 Jun 2016, at 20:18, Gary Kotton wrote: >> >> Hi, >> The following patch breaks stable liberty drivers - >> https://review.openstack.org/#/c/238745/ >> This means that plugins will need to

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

On Wed, Jun 15, 2016 at 2:01 PM, Peters, Rawlin wrote: > On Tuesday, June 14, 2016 6:27 PM, Kevin Benton (ke...@benton.pub) wrote: >> >which generates an arbitrary name >> >> I'm not a fan of this approach because it requires coordinated assumptions. >> With the OVS hybrid

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

On Mon, Jun 13, 2016 at 4: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 not, there is a spec and a fair number of patches in >>

Re: [openstack-dev] [qa] Tempest unstable interfaces in plugins

On Sat, Jun 11, 2016 at 4:04 PM, Ken'ichi Ohmichi <ken1ohmi...@gmail.com> wrote: > 2016-06-10 17:01 GMT-07:00 Assaf Muller <as...@redhat.com>: >> On Fri, Jun 10, 2016 at 12:02 PM, Andrea Frittoli >> <andrea.fritt...@gmail.com> wrote: >>> Dear all, >&g

Re: [openstack-dev] [qa] Tempest unstable interfaces in plugins

On Fri, Jun 10, 2016 at 12:02 PM, Andrea Frittoli wrote: > Dear all, > > I'm working on making the client manager in Tempest a stable interface, so > that in future it may be used safely by plugins to easily gain access > service clients [0]. > > This work inevitably

Re: [openstack-dev] [neutron][networking-ovn] OVN vs. OpenDayLight

On Thu, Jun 9, 2016 at 5:06 PM, Kyle Mestery <mest...@mestery.com> wrote: > On Thu, Jun 9, 2016 at 2:11 PM, Assaf Muller <as...@redhat.com> wrote: >> On Thu, Jun 9, 2016 at 1:48 PM, Ben Pfaff <b...@ovn.org> wrote: >>> On Thu, Jun 09, 2016 at 10:28:31AM

Re: [openstack-dev] [neutron][networking-ovn] OVN vs. OpenDayLight

On Thu, Jun 9, 2016 at 1:48 PM, Ben Pfaff wrote: > On Thu, Jun 09, 2016 at 10:28:31AM -0700, rezroo wrote: >> I'm trying to reconcile differences and similarities between OVN and >> OpenDayLight in my head. Can someone help me compare these two technologies >> and explain if they

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

On Mon, Jun 6, 2016 at 1:59 PM, 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][DevStack] Do we still need the neutron-debug command?

On Thu, May 19, 2016 at 11:36 AM, Sean M. Collins wrote: > Ryan Moats and I chatted a week or so ago about neutron-debug in the > context of DevStack. > > Ryan pushed a patch to see what it actually does[1]. > > Currently, it's not clear what it is used for, and in some

Re: [openstack-dev] [neutron]Get one network's usage

On Mon, May 16, 2016 at 4:38 AM, zhi wrote: > hi, all > > Many times we want to get one network's usage. Like this command: > "neutron get-network-usage". We can get how many ports were used in this > network. Besides, we can get floatingips usage from external

Re: [openstack-dev] [Neutron][QA] Call to action - Neutron/Tempest API tests dedup

org/developer/neutron/devref/development.environment.html#id3 The plugin was contributed by Daniel Mellado and we use it at the gate: https://github.com/openstack-infra/project-config/blob/master/jenkins/jobs/neutron.yaml#L34 > > > Thanks > Zhi Chang > > 2016-05-14 6:53 GMT+08:00 Assaf Mulle

[openstack-dev] [Neutron][QA] Call to action - Neutron/Tempest API tests dedup

TL;DR: I'm looking for volunteers for tasks 1, 2 and 3 listed below. Help would be hugely appreciated and %(local_drink)s will be bought in Barcelona. I've posted example patches that demonstrate the idea. Needless to say I'm here to provide reviews and to answer questions. Additionally, most of

Re: [openstack-dev] [Neutron] Diagnostics & troubleshooting design summit summary and next steps

st / knowledge in the space and it would be nice if they could work > together on developing the content. That's good input. For future reference I think you will find that if you reach out to session chairs, no one will say no :) > > > On 5/6/16 2:38 PM, Assaf Muller wrote: >> It

[openstack-dev] [Neutron] Diagnostics & troubleshooting design summit summary and next steps

It is my personal experience that unless I do my homework, design summit discussions largely go over my head. I'd guess that most people don't have time to research the topic of every design session they intend to go to, so for the session I lead I decided to do the unthinkable and present the

Re: [openstack-dev] [neutron][stable] - exception for stable/kilo DVR back-ports

On Wed, May 4, 2016 at 4:54 PM, Kevin Benton wrote: > Hello, > > I would like to propose a freeze exception for > https://review.openstack.org/#/c/312253/ and > https://review.openstack.org/#/c/312254/ . They address a bug in DVR that > causes floating IPs to eventually break

Re: [openstack-dev] [neutron][tc] Neutron stadium evolution from Austin

On Mon, May 2, 2016 at 3:18 PM, Gal Sagie wrote: > Maybe it can help if instead of trying to define criteria to which projects > dont fit into > the stadium, try to define in your spec what IT IS, and for what purpose its > there. Well said. This came up multiple times in

Re: [openstack-dev] [Neutron][Infra] Post processing of gate hooks on job timeouts

On Mon, Apr 11, 2016 at 1:56 PM, Clark Boylan wrote: > On Mon, Apr 11, 2016, at 10:52 AM, Jakub Libosvar wrote: >> On 04/11/2016 06:41 PM, Clark Boylan wrote: >> > On Mon, Apr 11, 2016, at 03:07 AM, Jakub Libosvar wrote: >> >> Hi, >> >> >> >> recently we hit an issue in

Re: [openstack-dev] [Neutron][Infra] Post processing of gate hooks on job timeouts

On Mon, Apr 11, 2016 at 9:39 AM, Morales, Victor wrote: > > > > > > On 4/11/16, 5:07 AM, "Jakub Libosvar" wrote: > >>Hi, >> >>recently we hit an issue in Neutron with tests getting stuck [1]. As a >>side effect we discovered logs are not collected

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

On Fri, Apr 8, 2016 at 3:37 PM, Doug Wiegley <doug...@parksidesoftware.com> wrote: > >> On Apr 8, 2016, at 1:28 PM, Sean M. Collins <s...@coreitpro.com> wrote: >> >> Assaf Muller wrote: >>> I do want to say that ML2's "mechanism_drivers" opti

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

On Fri, Apr 8, 2016 at 11:57 AM, Sean M. Collins wrote: > Edgar Magana wrote: >> This is a very solid plan. Maybe to fair on the current state of the >> devstack with neutron functionality, what will be the disadvantage(s) of >> this change from your perspective? >> > > A

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

+1 On Fri, Apr 8, 2016 at 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

Re: [openstack-dev] [neutron] OVSDB native interface as default in gate jobs

On Tue, Apr 5, 2016 at 12:35 PM, Sean M. Collins wrote: > Russell Bryant wrote: >> because they are related to two different command line utilities >> (ovs-vsctl vs ovs-ofctl) that speak two different protocols (OVSDB vs >> OpenFlow) that talk to two different daemons on the

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

On Fri, Apr 1, 2016 at 7:58 PM, Edgar Magana wrote: > Congratulations Assaf! > > From: "Armando M." > Reply-To: "OpenStack Development Mailing List (not for usage questions)" > > Date: Thursday, March 31, 2016 at

[openstack-dev] [All][Neutron] Improving development and review velocity - Is it time for a drastic change?

Have you been negatively impacted by slow development and review velocity? Read on. OpenStack has had a slow review velocity for as long as I can remember. This has a cascading effect where people take up multiple tasks, so that they can work on something while the other is being reviewed. This

Re: [openstack-dev] [Neutron][LBaaS][heat] Removing LBaaS v1 - are weready?

On Thu, Mar 24, 2016 at 1:48 AM, Takashi Yamamoto wrote: > On Thu, Mar 24, 2016 at 6:17 AM, Doug Wiegley > wrote: >> Migration script has been submitted, v1 is not going anywhere from >> stable/liberty or stable/mitaka, so it’s about to

Re: [openstack-dev] [neutron][stable] proactive backporting

On Wed, Mar 23, 2016 at 12:52 PM, Ihar Hrachyshka wrote: > Hey folks, > > some update on proactive backporting for neutron, and a call for action from > subteam leaders. > > As you probably know, lately we started to backport a lot of bug fixes in > latest stable branch

Re: [openstack-dev] [Neutron]Debug with Pycharm

On Tue, Mar 22, 2016 at 11:36 PM, Nguyen Hoai Nam wrote: > Hi everybody, > Have you configured PyCharm to debug Neutron project. I confuged but it's > not ok. If you have any archive, could you please share it with openstacker > ?

Re: [openstack-dev] [neutron] CI jobs take pretty long, can we improve that?

On Tue, Mar 22, 2016 at 9:31 AM, Kevin Benton wrote: > Thanks for doing this. I dug into the test_volume_boot_pattern test to see > what was going on. > > On the first boot, Nova called Neutron to create a port at 23:29:44 and it > took 441ms to return the port to Nova.[1] >

Re: [openstack-dev] [neutron] CI jobs take pretty long, can we improve that?

On Mon, Mar 21, 2016 at 9:26 PM, Clark Boylan <cboy...@sapwetik.org> wrote: > On Mon, Mar 21, 2016, at 06:15 PM, Assaf Muller wrote: >> On Mon, Mar 21, 2016 at 8:09 PM, Clark Boylan <cboy...@sapwetik.org> >> wrote: >> > On Mon, Mar 21, 2016, at 01:23 PM, Sean Da

Re: [openstack-dev] [neutron] CI jobs take pretty long, can we improve that?

On Mon, Mar 21, 2016 at 8:09 PM, Clark Boylan wrote: > On Mon, Mar 21, 2016, at 01:23 PM, Sean Dague wrote: >> On 03/21/2016 04:09 PM, Clark Boylan wrote: >> > On Mon, Mar 21, 2016, at 11:49 AM, Clark Boylan wrote: >> >> On Mon, Mar 21, 2016, at 11:08 AM, Clark Boylan wrote:

Re: [openstack-dev] [QA][all] Propose to remove negative tests from Tempest

On Wed, Mar 16, 2016 at 10:41 PM, Jim Rollenhagen wrote: > On Wed, Mar 16, 2016 at 06:20:11PM -0700, Ken'ichi Ohmichi wrote: >> Hi >> >> I have one proposal[1] related to negative tests in Tempest, and >> hoping opinions before doing that. >> >> Now Tempest contains

Re: [openstack-dev] [Neutron] [neutron-lib] adding a new flag to neutron-lib

On Mon, Mar 14, 2016 at 1:27 PM, Gary Kotton wrote: > Hi, > It would be nice if we could get a little more reviews in the neutron-lib. > I think that we should maybe strive to cut a new version prior to the > release. > Thanks > Gary > > On 3/14/16, 6:17 PM, "Venkata Anil"

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

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 >> wrote: >> I have written a sample neutron agent which subscribe for the

Re: [openstack-dev] Mitaka, Xenial, OVS Firewall Driver, DPDK, VXLAN and Provider Networks

On Sat, Feb 27, 2016 at 6:55 PM, Martinx - ジェームズ wrote: > Hey guys! > > Next Ubuntu and Mitaka are promising something ultra mega cool! > > Look at this! > > --- > root@mitaka-1:~# apt install neutron-openvswitch-agent > Reading package lists... Done > Building

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

On Wed, Feb 17, 2016 at 2:16 PM, Armando M. wrote: > > > On 17 February 2016 at 11:12, Armando M. wrote: >> >> Hi folks, >> >> It looks like something slipped in and how we got persistent failures on >> functional/fullstack jobs [1]. Has anyone triaged? I

Re: [openstack-dev] [QA][Tempest]Run only multinode tests in multinode jobs

On Tue, Feb 16, 2016 at 2:52 PM, Matthew Treinish wrote: > On Tue, Feb 16, 2016 at 10:07:19AM +0100, Jordan Pittier wrote: >> Hi list, >> I understood we need to limit the number of tests and jobs that are run for >> each Tempest patch because our resources are not

Re: [openstack-dev] [QA][Tempest]Run only multinode tests in multinode jobs

On Tue, Feb 16, 2016 at 12:26 PM, Clark Boylan wrote: > On Tue, Feb 16, 2016, at 01:07 AM, Jordan Pittier wrote: >> Hi list, >> I understood we need to limit the number of tests and jobs that are run >> for >> each Tempest patch because our resources are not unlimited. >> >>

Re: [openstack-dev] [all][tc] Proposal: Separate design summits from OpenStack conferences

On Fri, Feb 12, 2016 at 8:43 AM, Ihar Hrachyshka wrote: > Eoghan Glynn wrote: > >> >> [...] * much of the problem with the lavish parties is IMO related to the *exclusivity* of certain shindigs, as opposed to devs socializing at

Re: [openstack-dev] [neutron][stable] Request to do stable point releases more often if there are going to be a lot of backports

On Tue, Feb 9, 2016 at 5:10 PM, Matt Riedemann wrote: > While reviewing the neutron 7.0.2 stable/liberty point release, I noticed > there were a lot of changes since 7.0.1. [1] > > There are 48 non-merge commits by my count. > > While there is no rule about how many

Re: [openstack-dev] [Neutron] Being more aggressive with our defaults

I'm generally sympathetic to what you're saying, and I agree that we need to do something about disabled-by-default features, at the very least on the testing front. Comments in-line. On Mon, Feb 8, 2016 at 4:47 PM, Sean M. Collins wrote: > Hi, > > With the path_mtu issue -

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

On Thu, Feb 4, 2016 at 5:55 PM, Sean M. Collins <s...@coreitpro.com> wrote: > On Thu, Feb 04, 2016 at 04:20:50AM EST, Assaf Muller wrote: >> I understand you see 'Dragonflow being part of the Neutron stadium' >> and 'Dragonflow having high visibility' as tied together.

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

On Thu, Feb 4, 2016 at 8:33 AM, Gal Sagie wrote: > As i have commented on the patch i will also send this to the mailing list: > > I really dont see why Dragonflow is not part of this list, given the > criteria you listed. > > Dragonflow is fully developed under

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

On Thu, Feb 4, 2016 at 10:20 AM, Assaf Muller <amul...@redhat.com> wrote: > On Thu, Feb 4, 2016 at 8:33 AM, Gal Sagie <gal.sa...@gmail.com> wrote: >> As i have commented on the patch i will also send this to the mailing list: >> >> I really dont see why Dragonflo

Re: [openstack-dev] [Neutron][L3] Orphaned process cleanup

On Wed, Jan 27, 2016 at 4:52 PM, Sean M. Collins <s...@coreitpro.com> wrote: > On Wed, Jan 27, 2016 at 04:24:00PM EST, Assaf Muller wrote: >> On Wed, Jan 27, 2016 at 4:10 PM, Sean M. Collins <s...@coreitpro.com> wrote: >> > Hi, >> > >> > I st

Re: [openstack-dev] [Neutron][L3] Orphaned process cleanup

On Wed, Jan 27, 2016 at 5:20 PM, Sean M. Collins <s...@coreitpro.com> wrote: > On Wed, Jan 27, 2016 at 05:06:03PM EST, Assaf Muller wrote: >> >> RDO systemd init script for the L3 agent will send a signal 15 when >> >> 'systemctl restart neutron-l3-agent' is execu

Re: [openstack-dev] [Neutron][L3] Orphaned process cleanup

On Wed, Jan 27, 2016 at 4:10 PM, Sean M. Collins wrote: > Hi, > > I started poking a bit at https://bugs.launchpad.net/devstack/+bug/1535661 > > We have radvd processes that the l3 agent launches, and if the l3 agent > is terminated these radvd processes continue to run. I

Re: [openstack-dev] [neutron] questions about uni test

On Mon, Jan 25, 2016 at 10:05 AM, Gareth wrote: > Hey neutron guys > > What will happen if I remove this line[0]? > > When running unit test, do we create tables in real database? > > [0] >

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

On Thu, Jan 14, 2016 at 9:28 AM, Russell Bryant wrote: > On 01/13/2016 11:51 PM, Tony Breeds wrote: >> The challenge for you guys is the kernel side of things but if I >> understood correctly you can get the kenrel module from the ovs >> source tree and just compile it against

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

On Wed, Jan 13, 2016 at 4:50 AM, Jakub Libosvar wrote: > Hi all, > > recently I was working on firewall driver [1] that requires latest > features in OVS, specifically conntrack support. In order to get the > driver tested, we need to have the latest OVS kernel modules on

Re: [openstack-dev] [OpenStack-dev][Neutron] Is there a tool of generating network topology?

Check it out: https://github.com/jbenc/plotnetcfg On Mon, Dec 21, 2015 at 11:22 PM, Gareth wrote: > Hi, networking guys, > > For example, we could use it to generate a png file or print ascii in > command line. Is there something like this? > > -- > Gareth > > Cloud

Re: [openstack-dev] [Neutron][QA] New testing guidelines

e it if a Rally dev could send the patch and add me as a reviewer. > > Best regards, > Boris Pavlovic > > On Wed, Dec 16, 2015 at 7:00 AM, Fawad Khaliq <fa...@plumgrid.com> wrote: >> >> Very useful information. Thanks, Assaf. >> >> Fawad Khaliq

Re: [openstack-dev] [neutron][taas] neutron ovs-agent deletes taas flows

SFC are going to hit this issue as well. Really any out of tree Neutron project that extends the OVS agent and expects things to work :) On Tue, Dec 15, 2015 at 9:30 AM, Ihar Hrachyshka wrote: > Soichi Shigeta wrote: > >> >> Hi, >> >> We

Re: [openstack-dev] neutron metadata-agent HA

a routers? Should you still run > more then one? > > Thanks, > Kevin > ________ > From: Assaf Muller [amul...@redhat.com] > Sent: Saturday, December 12, 2015 12:44 PM > To: OpenStack Development Mailing List (not for usage questions) > Subject:

Re: [openstack-dev] neutron metadata-agent HA

M, Gary Kotton <gkot...@vmware.com> wrote: >> >> >> >> >> >> >> On 12/12/15, 10:44 PM, "Assaf Muller" <amul...@redhat.com> wrote: >> >> >The neutron metadata agent is stateless. It takes requests from the >> >meta

Re: [openstack-dev] neutron metadata-agent HA

The neutron metadata agent is stateless. It takes requests from the metadata proxies running in the router namespaces and moves the requests on to the nova server. If you're using HA routers, start the neutron-metadata-agent on every machine the L3 agent runs, and just make sure that the

[openstack-dev] [Neutron][QA] New testing guidelines

Today we merged [1] which adds content to the Neutron testing guidelines: http://docs.openstack.org/developer/neutron/devref/development.environment.html#testing-neutron The document details Neutron's different testing infrastructures: * Unit * Functional * Fullstack (Integration testing with

[openstack-dev] [Neutron] DVR + L3 HA + L2pop - Mapping out the work

There's a patch up for review to integrate DVR and L3 HA: https://review.openstack.org/#/c/143169/ Let me outline all of the work that has to happen before that patch would be useful: In order for DVR + L3 HA to work in harmony, each feature would have to be stable on its own. DVR has its share

Re: [openstack-dev] [Neutron] Call for review focus

On Mon, Nov 23, 2015 at 7:02 AM, Rossella Sblendido <rsblend...@suse.com> wrote: > > > On 11/20/2015 03:54 AM, Armando M. wrote: >> >> >> >> On 19 November 2015 at 18:26, Assaf Muller <amul...@redhat.com >> <mailto:amul...@redhat.com>> wr

Re: [openstack-dev] [Neutron] Call for review focus

On Wed, Nov 18, 2015 at 9:14 PM, Armando M. wrote: > Hi Neutrites, > > We are nearly two weeks away from the end of Mitaka 1. > > I am writing this email to invite you to be mindful to what you review, > especially in the next couple of weeks. Whenever you have the time to

Re: [openstack-dev] [stable][neutron] How we handle Kilo backports

On Wed, Nov 18, 2015 at 12:38 PM, Carl Baldwin wrote: > On Wed, Nov 18, 2015 at 9:44 AM, Ihar Hrachyshka wrote: >> Hi all, >> >> as per [1] I imply that all projects under stable-maint-core team >> supervision must abide the stable policy [2] which limits

Re: [openstack-dev] Couldn't ping/ssh cirros instance using its floating ip

You will have a much better time on ask.openstack.org - It's a super active Q site for questions exactly like this one. You posted your question to a developers mailing list where we choose release names and make other ultra important mission critical decisions. On Mon, Nov 9, 2015 at 6:34 PM,

Re: [openstack-dev] [stable][infra][neutron] ZUUL_BRANCH not set for periodic stable jobs

On Mon, Nov 9, 2015 at 5:30 PM, Ihar Hrachyshka wrote: > Jeremy Stanley wrote: > >> On 2015-11-09 17:31:00 +0100 (+0100), Ihar Hrachyshka wrote: >> [...] >>> >>> From the failure log, I determined that the tests fail because they >>> assume >>>

Re: [openstack-dev] [neutron][stable] proactive backporting

On Fri, Oct 16, 2015 at 5:32 PM, Kevin Benton wrote: > We can't put in code and just hope for testing later. The tests are even > more important in back-ports because there could be unexpected differences > in the stable branch that make the patch not work correctly. > >

  1   2   >