14:00:59 <slaweq> #startmeeting networking 14:01:00 <openstack> Meeting started Tue Oct 8 14:00:59 2019 UTC and is due to finish in 60 minutes. The chair is slaweq. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:01:02 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:01:02 <slaweq> hi 14:01:04 <openstack> The meeting name has been set to 'networking' 14:01:06 <njohnston> o/ 14:01:08 <mlavalle> o/ 14:01:08 <amotoki> o/ 14:01:09 <ralonsoh> hi 14:01:27 <haleyb> hi 14:01:31 <bcafarel> \o 14:01:50 <slaweq> #topic Announcements 14:02:04 <slaweq> Shanghai PTG: 14:02:16 <lajoskatona> hi 14:02:30 <slaweq> planning etherpad https://etherpad.openstack.org/p/Shanghai-Neutron-Planning - just a reminder, if You have any ideas about topic for ptg, please add them to this etherpad 14:02:58 <rubasov> hi 14:03:04 <slaweq> ptg schedule is now ready: https://usercontent.irccloud-cdn.com/file/z9iLyv8e/pvg-ptg-sched-2 14:03:14 <slaweq> we have full 3 days for Neutron 14:04:26 <slaweq> and the last one: 14:04:39 <slaweq> we have accepted one neutron related session for forum: https://www.openstack.org/summit/shanghai-2019/summit-schedule/events/24412/neutron-stadium-projects-the-path-forward 14:05:43 <slaweq> and that's all related to the PTG 14:06:02 <slaweq> next announcements topic is "Train departure" :) 14:06:26 <slaweq> according to the https://releases.openstack.org/train/schedule.html this week is week of last RC releases if needed 14:07:18 <slaweq> I don't think we need to release rc2 for anything, except midonet which we already did last week 14:07:35 <bcafarel> yes deadline is Thursday for last minute release-breaking fixes to get in a rc2 14:07:53 <slaweq> but if You know about any patches which would require such rc2 for any project, please speak about it now :) 14:08:13 <slaweq> or ping me or amotoki on irc later 14:08:57 <bcafarel> coast looks clear from currently open stable/train backports (nothing critical in progress) 14:09:05 <amotoki> note that it applies to all stadium projects. it is not only for neutron repo. 14:09:28 <slaweq> amotoki: exactly :) 14:09:41 <slaweq> bcafarel: thx for info 14:09:50 <haleyb> so i guess it's time to tag the stable branches? we should take a look at the open changes this week bcafarel 14:10:22 <amotoki> haleyb: is it about stable branches like stein or older ones? 14:10:46 <bcafarel> haleyb: I was writing a similar message :) yes I plan to check queens/rocky/stein status today or tomorrow 14:10:48 <haleyb> stein and older, just so there are new tags for downstream 14:11:03 <haleyb> bcafarel: +1 14:11:06 <slaweq> thx haleyb and bcafarel for taking care of it 14:12:15 <slaweq> and the most important announcement: 14:12:25 <slaweq> next week is Train release week finally 14:12:28 <slaweq> :) 14:13:23 <bcafarel> I will miss all the train jokes in 2 weeks 14:13:29 <slaweq> :) 14:13:44 <slaweq> and one last announcement from me for today: 14:13:52 <slaweq> few days ago we merged https://review.opendev.org/#/c/685917/ - so now "mechanial" changes can be approved with 1 x +2 14:14:05 <slaweq> any other announcements from the team? 14:15:33 <slaweq> ok, let's move on 14:15:35 <slaweq> #topic Blueprints 14:16:06 <slaweq> We don't have yet milestone Ussuri-1 created so there is no list of targeted BPs 14:16:18 <slaweq> but maybe anyone wants to talk about any BP now? 14:16:23 <slaweq> any updates maybe? 14:17:19 <mlavalle> I recently sent an email to wwriverrat 14:17:32 <mlavalle> whom I don't see around 14:17:54 <mlavalle> about his blueprint for multiple segments per host in routed networks 14:18:03 <mlavalle> I am interested in continuing that work 14:18:24 <mlavalle> so I amy add it soon to the the next milestone dasboard 14:19:17 <slaweq> mlavalle: thx for update and for volunteering to work on this 14:20:31 <davidsha> For the DSCP + Neutron Classifier integration, I'm just working through refactoring based on comments atm. 14:21:16 <slaweq> davidsha: so this one we probably also should add soon to the next milestone dashboard, right? 14:21:35 <davidsha> Please! 14:21:58 <slaweq> davidsha: sure, I will 14:22:03 <davidsha> Thanks 14:23:43 <slaweq> ok, I think we can move on than 14:23:49 <slaweq> thx for updates about BPs 14:23:59 <slaweq> #topic Community goals 14:24:19 <slaweq> amotoki: I think that generating pdf docs goal is done now, right? 14:24:34 <slaweq> all patches on list https://review.opendev.org/#/q/topic:build-pdf-docs+(status:open+OR+status:merged)+(project:%255Eopenstack/neutron.*+OR+project:%255Eopenstack/networking-.*) are merged 14:24:42 <amotoki> we finished the PDF docs goal :) 14:24:44 <amotoki> https://storyboard.openstack.org/#!/story/2006099 14:25:18 <ralonsoh> well done 14:25:18 <slaweq> \o/ 14:25:23 <bcafarel> \o/ 14:25:28 <davidsha> \o/ 14:25:32 <slaweq> great work amotoki - thx a lot 14:25:32 <njohnston> \o/ 14:25:50 <slaweq> so I will remove this goal from agenda for next meetings, ok? 14:25:51 <mlavalle> Nice! 14:25:52 <amotoki> thanks all for detail feedback :) 14:25:59 <amotoki> yeah, we can drop it 14:26:42 <slaweq> thx 14:27:13 <slaweq> according py3 goal, I updated recently etherpad for stadium projects: https://etherpad.openstack.org/p/neutron_stadium_python3_status 14:27:40 <slaweq> according to our completion criteria, networking-odl should be already done as voting jobs as switched 14:27:58 <lajoskatona> slaweq: yesh, as we discussed last week 14:28:25 <slaweq> for networking-bagpipe, I proposed patch to switch neutron-tempest-plugin job to py3: https://review.opendev.org/#/c/685702/ 14:28:38 <slaweq> and with this patch https://review.opendev.org/#/c/686990/ it should be also fine 14:28:42 <amotoki> AFAIK, legacy-networking-bagpipe-dsvm-fullstack still depends on py27 too. 14:29:13 <slaweq> amotoki: but it is non-voting job, right? 14:29:33 <amotoki> yes, it is non-voting. the job itself is broken now, so it does not matter. 14:30:53 <slaweq> I want for now focus only on voting jobs 14:31:13 <slaweq> as I'm not e.g. bagpipe expert and I don't have time to fix non-voting jobs for this project :/ 14:32:05 <njohnston> +1 14:32:09 <amotoki> agree 14:32:16 <slaweq> so, please review https://review.opendev.org/#/c/686990/ and than https://review.opendev.org/#/c/685702/ if You have some time :) 14:33:08 <slaweq> and also, I saw that haleyb did very important patch for neutron already: https://review.opendev.org/#/c/686833/ 14:33:34 <haleyb> might as well get it started :) 14:33:43 <slaweq> thx haleyb for that - it's small patch for human big step for humanity ;) 14:33:47 <njohnston> networking-ovn is also moving forward: https://review.opendev.org/#/c/686987/ 14:34:08 <haleyb> there is still the py27 job defined elsewhere, that's about it 14:34:22 <haleyb> i'll probably get one out for octavia as well 14:34:31 <bcafarel> this one is common job definition so it will probably stay last? 14:34:41 <amotoki> I think tox-py27 will be dropped when a project template for ussuri is defined. 14:34:55 <slaweq> yes, py27 is comming from template defined by qa team 14:36:19 <njohnston> just as an FYI, not everything is dropping pu27 support. Since tempest is branchless it will need to operate on py27 for some time yet, and so the same extends to neutron-tempest-plugin 14:36:59 <slaweq> I think we should create some new etherpad to coordinate removal of such jobs from all stadium repos 14:37:02 <amotoki> njohnston: yes, templest plugins should work with stable branches, so we need py35 and py27 supports. 14:37:22 <slaweq> njohnston: in neutron-tempest-plugin we are running jobs on py27 for stable branches, and we will keep that still 14:37:38 <slaweq> but jobs for train and master are running on py3 14:39:04 <slaweq> in overall, I think we are in good shape for supporting py3 and dropping support for py2 in Ussuri 14:39:12 <slaweq> ok, lets move on 14:39:33 <slaweq> according to ipv6 only deployments there is no too much progress in last week 14:40:01 <slaweq> gmann proposed new job for neutron-tempest-plugin https://review.opendev.org/#/c/686043/ - I have to review it and check what is missing there still 14:40:14 <slaweq> nothing else on this topic for today 14:40:26 <slaweq> #topic Bugs 14:40:44 <slaweq> bcafarel was bug deputy last week 14:40:56 <slaweq> and he send report which is available at: http://lists.openstack.org/pipermail/openstack-discuss/2019-October/009970.html 14:41:09 <slaweq> it seems like quite week 14:41:19 <slaweq> bcafarel: any bugs You want to highlight now? 14:41:29 <bcafarel> yes, not too many bugs and most have fixes in or in progress 14:41:41 <bcafarel> only one I had doubts on is https://bugs.launchpad.net/neutron/+bug/1846494 14:41:41 <openstack> Launchpad bug 1846494 in neutron "neutron-openvswitch-agent and IPv6" [Medium,Confirmed] 14:42:00 <bcafarel> and some nice PTL came in to comment :) 14:42:22 <slaweq> thx :) 14:42:38 <bcafarel> also I saw https://bugs.launchpad.net/neutron/+bug/1794569 from week before was reopened, tested on ocata this time (dvr issue) 14:42:38 <openstack> Launchpad bug 1794569 in neutron "DVR with static routes may cause routed traffic to be dropped" [Undecided,New] 14:44:06 <bcafarel> One RFE in discussion also for the interested: https://bugs.launchpad.net/neutron/+bug/1846285 14:44:06 <openstack> Launchpad bug 1846285 in neutron "[RFE] routed network for hypervisor" [Undecided,Confirmed] 14:44:11 <bcafarel> and that's it for the highlights 14:44:18 <slaweq> thx bcafarel 14:44:36 <slaweq> according to this rfe, I wanted to ask mlavalle if You can take a look at it 14:44:50 <slaweq> as You are routed networks expert here :) 14:45:03 <mlavalle> I am actually looking at it right now 14:45:20 <bcafarel> I have to catch on latest updates, it is in my toread tabs :) 14:45:22 <slaweq> mlavalle: thx a lot 14:46:30 <slaweq> any other bugs anyone wants to talk about today? 14:47:55 <slaweq> ok, I take that as "no" 14:48:00 <slaweq> #topic On Demand agenda 14:48:08 <slaweq> on demand agenda is empty for today 14:48:21 <slaweq> but maybe You have anything else to talk about? 14:48:48 <njohnston> I have one thing 14:49:08 <njohnston> With other responsibilities I'd like to give someone else a chance to act as the oslo liaison 14:49:37 <njohnston> It takes very little work - just another IRC meeting to attend 14:50:09 <bcafarel> when is the meeting? 14:50:18 <ralonsoh> njohnston, I'll ping you latter to know what is needed 14:50:38 <ralonsoh> what this person needs to do 14:51:04 <njohnston> Mondays; 1500 UTC 14:51:13 <njohnston> ralonsoh: Sure thing 14:51:33 <njohnston> Once you hear, ping slaweq if you want to volunteer 14:51:40 <ralonsoh> ok 14:52:10 <njohnston> that's all for me 14:53:26 <slaweq> thx njohnston for Your work on this so far 14:53:59 <slaweq> and thx bcafarel and ralonsoh for (potentially) volunteering for this role :) 14:54:24 <slaweq> anything else You want to talk today? 14:54:26 <bcafarel> :) reading https://wiki.openstack.org/wiki/CrossProjectLiaisons#Oslo atm, it has some details on role 14:55:08 <ralonsoh> bcafarel++ 14:55:27 <slaweq> thx bcafarel for the link 14:55:42 <slaweq> I think we can finish this meeting now 14:55:56 <slaweq> thx for attending and have a great week! 14:55:57 <slaweq> o/ 14:56:00 <slaweq> #endmeeting