14:00:05 <slaweq> #startmeeting networking
14:00:07 <slaweq> o/
14:00:12 <openstack> Meeting started Tue Jul 30 14:00:05 2019 UTC and is due to finish in 60 minutes.  The chair is slaweq. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:00:13 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:00:15 <openstack> The meeting name has been set to 'networking'
14:00:18 <mlavalle> o/
14:00:20 <njohnston> o/
14:00:21 <tidwellr> o/
14:00:37 <rubasov> o/
14:00:44 <bcafarel> \o
14:01:13 <slaweq> welcome back bcafarel :)
14:01:21 <haleyb> hi
14:01:30 <slaweq> and welcome back haleyb :)
14:01:31 <lajoskatona> o/
14:01:37 <ralonsoh> hi
14:01:40 <slaweq> ok, I think we can start
14:01:42 <bcafarel> back to full crowd? :)
14:01:43 <slaweq> #topic Announcements
14:02:04 <slaweq> Milestone T-2 was last week
14:02:17 <slaweq> Next milestone is T-3 in week of Sep 09
14:02:22 <slaweq> https://releases.openstack.org/train/schedule.html
14:02:33 <mlavalle> at the end of summer :-)
14:02:46 <amotoki> hi
14:03:17 <slaweq> please note that in next few weeks there will be also time for nominations for TC election and later for PTLs if someone will want to candidate :)
14:03:38 <slaweq> it will be week of Aug 26
14:03:48 <slaweq> next one:
14:03:50 <slaweq> Shanghai PTG planning etherpad:
14:03:55 <slaweq> https://etherpad.openstack.org/p/Shanghai-Neutron-Planning
14:04:09 <slaweq> please add Your name there if You are planning to attend
14:04:21 <slaweq> mlavalle needs this info before Aug 4th
14:04:24 <mlavalle> no cheanges since lastt week
14:04:41 <mlavalle> some it seems we are converging to the answer
14:05:23 <slaweq> Please also free to propose topics. We don't have deadline for this other than the PTG itself
14:05:37 <slaweq> and last reminder on the list:
14:05:39 <slaweq> Train PTG summary: http://lists.openstack.org/pipermail/openstack-discuss/2019-May/006408.html
14:05:53 <slaweq> any other announcements/reminders from the team?
14:06:43 <slaweq> ok, I think we can continue
14:06:52 <slaweq> #topic Blueprints
14:07:14 <slaweq> I moved existing, not finished BPs from T-2 to T-3
14:07:18 <slaweq> list is on https://launchpad.net/neutron/+milestone/train-3
14:07:33 <slaweq> any updates about BPs?
14:08:13 <tidwellr> I added a couple test cases to https://review.opendev.org/#/c/667511/, subnets-different-pools-same-net just needs one last round of reviews
14:08:58 <mlavalle> will review today
14:10:27 <slaweq> tidwellr: thx, I can review it tomorrow morning my time
14:10:49 <njohnston> I am working on the ethertype change for iptables_hybrid; I added a validator last week but I realized last night that it needs to handle some additional scenarios so I'll push a change to that today.  Thanks slaweq for helping me with the fullstack test problem.
14:11:22 <slaweq> njohnston: no problem, I hope that my advice was somehow useful :)
14:12:48 <slaweq> from other blueprints
14:13:02 <slaweq> https://blueprints.launchpad.net/neutron/+spec/multiple-segment-per-network-per-host - spec for this one is ready for review: https://review.opendev.org/#/c/657170 -
14:13:06 <slaweq> please take a look
14:14:03 <slaweq> and I would also want to ask for reviews of patches from rubasov for https://blueprints.launchpad.net/neutron/+spec/improve-extraroute-api - patches are available at https://review.opendev.org/#/q/topic:extraroute+(status:open+OR+status:merged) and IMO at least some of them looks quite good already
14:14:41 <slaweq> that's all from my about blueprints
14:14:46 <slaweq> any other updates from the team?
14:15:45 <slaweq> ok, I will take it as "no"
14:15:47 <slaweq> lets move on
14:15:57 <slaweq> #topic Community goals
14:16:20 <slaweq> amotoki: njohnston any updates on py3 and pdf docs?
14:16:44 <amotoki> on pdf docs, sample neutron.conf causes latex error now.
14:17:02 <amotoki> I am thinking to split sample neutron.conf into more meaningful pieces
14:17:21 <amotoki> and started to look into the current sample config file in detail.
14:17:34 <amotoki> that's the update from me.
14:18:22 <slaweq> thx amotoki
14:18:57 <njohnston> For the python 3 transition, there is outstanding work left to do for networking-bagpipe, networking-midonet, networking-odl, and it looks like amotoki is making good headway on python-neutronclient
14:19:39 <amotoki> njohnston: yes, neutronclient py3 migration will complete by my patch series
14:20:05 <slaweq> that is good news about neutronclient :)
14:20:08 <njohnston> lajoskatona: we usually discuss this in more detail in the neutron CI meeting later, do you want to join to talk about networking-odl?
14:20:10 <slaweq> thx amotoki for working on it
14:20:14 * mlavalle had an internet connection hiccup
14:20:44 <lajoskatona> njohnston: sure, perhaps I will late, as after this meeting I will go home ,and that's take some time
14:21:04 <njohnston> lajoskatona: Would you like to give us your status now, would that be easier?
14:21:58 <lajoskatona> njohnston: yeah, why not. There are a few patches for fixing minor things in networking-odl to make it py3 compatible
14:22:22 <lajoskatona> njohnston: and we started to modernize the jobs / and make them use py3
14:22:46 <lajoskatona> njohnston: so the work is ongoing, some review attention is always helpful :-)
14:22:52 <njohnston> lajoskatona: If you have a common topic or topics for those changes let us know and we can drive extra reviews to it
14:23:01 <amotoki> yeah, zuulv3 migration first would make things easier :)
14:23:28 <slaweq> lajoskatona: or You can add links to patches to the etherpad: https://etherpad.openstack.org/p/neutron_stadium_python3_status
14:23:40 <njohnston> even better
14:23:59 <lajoskatona> slaweq: I add them, I just wanted to ask where can I advertise the ready to review patches
14:24:54 <lajoskatona> I think that's it for networking-odl
14:24:57 <slaweq> lajoskatona: IMO You can add all Your related patches to this etherpad and ask for reviews even on neutron meeting when patches will be ready
14:25:09 <lajoskatona> slaweq: ok, thanks
14:25:12 <njohnston> yamamoto: Any word on midonet py3 updating?
14:25:16 <slaweq> but will be good to have it in etherpad as we are using it to track progress
14:26:20 <njohnston> Thanks all for the updates, I think overall the stadium is looking in really good shape.
14:26:28 <amotoki> slaweq: njohnston: osc-check-pluigns job in python-neutronclient is from openstackclient repo. Is it okay to track it as OSC and to make it out-of-rader of neutron team?
14:26:45 <amotoki> I am taking care of it though.
14:27:21 <slaweq> amotoki: yes, if it's defined in osc repo than I think that it makes sense to not track it here
14:27:33 <njohnston> agreed
14:27:42 <amotoki> thanks for confirmation
14:28:08 <slaweq> from my side I have small update about Support IPv6-Only Deployments
14:28:14 <slaweq> gmann started pushing some patches to various projects
14:29:05 <slaweq> recently he asked me about list of neutron stadium projects which are using some kind of communication between e.g. agents and which will require to have separate jobs defined to cover that
14:29:23 <slaweq> I made list of such projects in http://lists.openstack.org/pipermail/openstack-discuss/2019-July/008084.html
14:29:46 <slaweq> please take a look into it and correct this list if I missed some projects for example
14:31:28 <slaweq> I think we can move on to the next topic then
14:31:35 <slaweq> #topic Bugs
14:31:46 <slaweq> our bug deputy last week was boden
14:32:01 <slaweq> he send summary which is available at http://lists.openstack.org/pipermail/openstack-discuss/2019-July/008089.html
14:33:04 <slaweq> there wasn't too many bugs during last week
14:33:14 <slaweq> one which I would like to mention here is https://bugs.launchpad.net/neutron/+bug/1837552
14:33:15 <openstack> Launchpad bug 1837552 in neutron "neutron-tempest-with-uwsgi job finish with timeout very often" [Medium,Confirmed]
14:33:33 <slaweq> this one don't have assignee yet
14:33:55 <slaweq> so if someone would like to help with uwsgi than this is good place to start :)
14:34:30 <mlavalle> and there is a duplicate in the list also
14:34:39 <slaweq> other than that we have one RFE https://bugs.launchpad.net/neutron/+bug/1837847 -  which is already in good hands of njohnston and mlavalle who asked some questions in comments
14:34:41 <openstack> Launchpad bug 1837847 in neutron "[RFE] neutron-vpnaas OpenVPN driver" [Undecided,New]
14:34:56 <mlavalle> https://bugs.launchpad.net/neutron/+bug/1837916
14:34:57 <openstack> Launchpad bug 1828375 in neutron "duplicate for #1837916 Bulk creation of subports fails with StaleDataError" [Low,In progress] - Assigned to Bence Romsics (bence-romsics)
14:35:11 <slaweq> mlavalle: yes, thx
14:35:15 <mlavalle> rubasov is working on this one
14:35:32 <rubasov> mlavalle, boden: kind of
14:35:47 <rubasov> I think it's a duplicate of a previously fixed one
14:36:03 <mlavalle> thanks for the clarification
14:36:05 <rubasov> but would be nice to get feedback if the fix is working as expected
14:36:55 <slaweq> I will ping dulek to check if Your patch will help him
14:37:23 <rubasov> slaweq: thank you
14:37:36 <slaweq> rubasov: thx for taking care of this bug :)
14:37:44 <rubasov> of course
14:37:49 <slaweq> any other bugs You want to talk about today?
14:39:02 <slaweq> if not, lets move on
14:39:15 <slaweq> our bug deputy this week is haleyb
14:39:20 <slaweq> just after PTO :)
14:39:35 <haleyb> yes, into the deep end of the pool :)
14:39:43 <mlavalle> and lajoskatona won't be available next week, nor the next one
14:39:52 <mlavalle> correct?
14:39:59 <lajoskatona> mlavalle: thanks :-)
14:40:08 <lajoskatona> and the wee kafter that the same
14:40:14 <lajoskatona> week after that
14:40:38 <mlavalle> would amotoki or njohnston be willing to switch with lajoskatona?
14:40:39 <slaweq> LOL, it took me a while to understand what "wee kafter" means :)
14:40:47 <amotoki> i would like to switch
14:41:16 <njohnston> I will also be on PTO during lajoskatona's shift; I traded places with haleyb already because of it :-/
14:41:17 <lajoskatona> amotoki: thanks, that's good for me
14:41:20 <mlavalle> so amotoki does next week and lajoskatona does week of August 26th
14:41:27 <mlavalle> does that work for both?
14:41:38 <amotoki> mlavalle: yes
14:41:39 <slaweq> thx amotoki, so I will update schedule afgter this meeting if it works for You
14:41:56 <mlavalle> slaweq: I say let's leave the schedule as it is
14:41:59 <lajoskatona> mlavalle: yes
14:42:06 <mlavalle> let's not change the order in the roster
14:42:17 <slaweq> mlavalle: ok
14:42:22 <mlavalle> let's just remember the exception this cycle
14:42:31 <mlavalle> rotation that is
14:43:38 <slaweq> ok, lets move on than
14:43:40 <slaweq> next topic
14:43:46 <slaweq> #topic neutron-lib
14:43:55 <slaweq> boden: any updates?
14:43:58 <boden> hi
14:44:17 <boden> mainly just business as usual; with nothing exciting to report
14:44:22 <boden> but I do have 1 question
14:44:46 <boden> does the networking-ovn-tempest-dsvm-ovs-release job for neutron pull ovn from source?
14:45:12 <slaweq> I don't think so
14:45:17 <slaweq> but let me check
14:45:32 <boden> slaweq... maybe I can just ping you later about this.. no need to waste everyones time?
14:46:00 <slaweq> boden: https://opendev.org/openstack/networking-ovn/src/branch/master/zuul.d/networking-ovn-jobs.yaml#L219
14:46:06 <slaweq> this job is using branch 2.11
14:46:15 <slaweq> but is compiling it from source
14:46:54 <boden> slaweq let me ping you about this later... seems like something we can chat about "offline".. is that ok?
14:47:02 <haleyb> slaweq: i have a change to stop doing that (if we're talking about the same thing), but it's dependent on moving to F29
14:47:03 <slaweq> boden: sure
14:47:25 <boden> nothing else for neutron-lib unless others have comments
14:48:05 <slaweq> ok, thx boden for updates
14:48:12 <slaweq> last topic for today
14:48:13 <slaweq> #topic On demand agenda
14:48:33 <slaweq> anything else You want to talk about today?
14:48:59 <slaweq> if not, I will give You back about 10 minutes :)
14:49:47 <slaweq> ok, so lets finish this meeting earlier
14:49:52 <slaweq> thx for attending
14:49:59 <mlavalle> o/
14:50:00 <slaweq> and have a nice week
14:50:01 <slaweq> o/
14:50:03 <amotoki> o/
14:50:04 <lajoskatona> bye
14:50:05 <slaweq> #endmeeting