14:00:47 <slaweq> #startmeeting networking
14:00:48 <openstack> Meeting started Tue Nov 19 14:00:47 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:49 <slaweq> hi
14:00:50 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:00:52 <openstack> The meeting name has been set to 'networking'
14:00:53 <njohnston_> o/
14:01:51 <bcafarel> howdy
14:02:16 <ralonsoh> hi
14:03:08 <slaweq> ok, lets start than
14:03:26 <slaweq> #topic Announcements
14:03:45 <slaweq> we have quite many announcements for today
14:03:50 <slaweq> Shanghai PTG summary: http://lists.openstack.org/pipermail/openstack-discuss/2019-November/010702.html and also on http://kaplonski.pl/blog/shanghai_ptg_summary/ (with photos from team dinner)
14:04:52 <slaweq> if You would like to have follow up discussion about some of the topics from this summary, please open new thread on ML for that
14:04:56 <slaweq> ok, next ona
14:04:58 <slaweq> *one
14:05:05 <slaweq> Today I sent emails about "new daddies need" for few projects:
14:05:11 <slaweq> neutron-fwaas: http://lists.openstack.org/pipermail/openstack-discuss/2019-November/010929.html
14:05:18 <slaweq> networking-bagpipe/bgpvpn: http://lists.openstack.org/pipermail/openstack-discuss/2019-November/010930.html
14:05:25 <slaweq> neutron-vpnaas: http://lists.openstack.org/pipermail/openstack-discuss/2019-November/010931.html
14:05:57 <liuyulong> hi
14:05:57 <slaweq> lets now wait if there will be any volunteers to maintain those projects
14:06:02 <slaweq> hi liuyulong
14:07:27 <slaweq> for now amotoki talked with dkushwaha who is Tacker PTL and he will take care of networking-sfc
14:07:40 <slaweq> so we already found "new daddy" for one stadium project :)
14:07:52 <njohnston> \o/
14:08:10 <bcafarel> glad for networking-sfc :)
14:08:24 <slaweq> and today lajoskatona offered on IRC that Ericsson can take care of networking-bgpvpn and bagpipe
14:08:57 <njohnston> nice!
14:09:04 <slaweq> yeah :)
14:09:26 <slaweq> lets now wait few more weeks to see how it will be
14:09:35 <slaweq> ok, next announcement
14:09:37 <slaweq> Removing of neutron-interconnection from stadium project is in progress: https://review.opendev.org/#/q/branch:master+topic:neutron-interconnection-retire
14:09:57 <slaweq> I need to add some proper releasse note to one of those patches
14:10:44 <slaweq> and I saw that Thomas vote -1 on https://review.opendev.org/#/c/694480/ as he wants to move the repo to x/ namespace
14:11:18 <slaweq> but that can be done later as separate step, at least that's how I understood this procedure
14:11:24 <slaweq> njohnston: am I right?
14:11:30 <slaweq> or am I missing something there?
14:11:59 <njohnston> yes, I think fungi's suggestion is the best way http://lists.openstack.org/pipermail/openstack-discuss/2019-November/010893.html
14:12:08 <rubasov> late o/
14:12:34 <njohnston> which would not change your patches, he would just revert the code removal change once he imported the code into the new x/ repo
14:13:06 <slaweq> yes, ok. So I understood this procedure correctly
14:13:20 <slaweq> it's quite complicated process to remove such repo
14:13:44 <slaweq> ok, lets move on
14:13:48 <slaweq> next announcement
14:13:52 <slaweq> I added "review-priority" vote to gerrit, details about it can be found at http://lists.openstack.org/pipermail/openstack-discuss/2019-November/010825.html
14:14:35 <njohnston> Should we come to a general agreement as to what constitutes an "important change"?
14:14:45 <njohnston> otherwise it's rather subjective
14:14:47 <slaweq> basically core reviewers can now add +2, +1 or -1 vote to this new category and in dashboard
14:14:49 <slaweq> https://review.opendev.org/#/dashboard/?title=Neutron+Priorities+Dashboard&foreach=%2528project%253Aopenstack%252Fneutron+OR%250Aproject%253Aopenstack%252Fneutron%252Dlib+OR%250Aproject%253Aopenstack%252Fneutron%252Dtempest%252Dplugin+OR%250Aproject%253Aopenstack%252Fpython%252Dneutronclient+OR%250Aproject%253Aopenstack%252Fneutron%252Dspecs+OR%250Aproject%253Aopenstack%252Fnetworking%252Dbagpipe+O
14:14:51 <slaweq> R%250Aproject%253Aopenstack%252Fnetworking%252Dbgpvpn+OR%250Aproject%253Aopenstack%252Fnetworking%252Dmidonet+OR%250Aproject%253Aopenstack%252Fnetworking%252Dodl+OR%250Aproject%253Aopenstack%252Fnetworking%252Dovn+OR%250Aproject%253Aopenstack%252Fnetworking%252Dsfc+OR%250Aproject%253Aopenstack%252Fneutron%252Ddynamic%252Drouting+OR%250Aproject%253Aopenstack%252Fneutron%252Dfwaas+OR%250Aproject%253A
14:14:53 <slaweq> openstack%252Fneutron%252Dfwaas%252Ddashboard+OR%250Aproject%253Aopenstack%252Fneutron%252Dvpnaas+OR%250Aproject%253Aopenstack%252Fneutron%252Dvpnaas%252Ddashboard+OR%250Aproject%253Aopenstack%252Fos%252Dken+OR%250Aproject%253Aopenstack%252Fovsdbapp%2529+status%253Aopen&High+Priority+Changes=label%253AReview%252DPriority%253D2&Priority+Changes=label%253AReview%252DPriority%253D1&Blocked+Reviews=lab
14:14:55 <slaweq> el%253AReview%252DPriority%253D%252D1 everyone can check what are current top priority patches to review
14:15:08 <maciejjozefczyk> \o sorry for beign late
14:16:02 <slaweq> njohnston: so, IMO "important change" may be some changes which fixes gate failures, or changes which are targeted to milestone which is just around the corner
14:16:17 <ralonsoh> slaweq, can you copy-paste this url in http://paste.openstack.org/?
14:16:45 <slaweq> ralonsoh: sorry, short version is here https://tinyurl.com/vezk6n6
14:16:55 <njohnston> slaweq: OK, I can use that rule of thumb
14:16:59 <ralonsoh> perfect!
14:17:47 <slaweq> njohnston: and also, I hope that as only cores can set those priorities we should be fine as each of us have already some experience and feeling what is "important change" for review
14:18:11 <njohnston> sounds good
14:18:29 <slaweq> maybe also fixes for bugs marked as "critical" can be marked as "high priority" to review
14:18:54 <liuyulong> Some security bug or critical bug should also be important and with higher review priority, IMO。
14:19:05 <slaweq> liuyulong: yes, it can be
14:19:42 <slaweq> so to sumup, I would say: lets use our personal experience and feeling for that and lets see how it will work for us
14:20:22 <slaweq> I will review this dashboard before every neutron team meeting and if there will be anything to discuss, I will raise it during the meeting
14:20:26 <slaweq> ok for You?
14:20:51 <ralonsoh> +1
14:20:55 <liuyulong> +1
14:21:34 <bcafarel> review of the review list? thanks :)
14:22:15 <slaweq> bcafarel: lol, yeah
14:22:55 <slaweq> ok, so one last announcement from me today
14:23:11 <slaweq> last week I prepared some plan of cleaning our CI jobs
14:23:18 <slaweq> I sent it here: http://lists.openstack.org/pipermail/openstack-discuss/2019-November/010838.html
14:23:53 <slaweq> I think we can discuss about it during CI meeting in details but I would also ask everyone from the team to check it and tell me what You think about it
14:24:38 <slaweq> and that's all announcements from me for today
14:24:51 <slaweq> do You have any other things to announce?
14:25:13 <liuyulong> We have qos meeting in next our? Or we will move it to this one?
14:25:20 <liuyulong> s/our/hour
14:26:18 <slaweq> liuyulong: qos meeting is just after this one
14:26:47 <liuyulong> We have any meeting rescheduling announcementa?
14:27:18 <ralonsoh> (there is no agenda for QoS meeting today)
14:27:35 <slaweq> liuyulong: this meeting isn't rescheduled
14:28:28 <liuyulong> slaweq, sure, I remember that the ovn and performance meeting are merged to neutron team meeting, right?
14:28:38 <slaweq> right
14:28:49 <slaweq> I didn't add it to announcements
14:29:02 <slaweq> but I have new item on the meeting agenda for that :)
14:29:11 <liuyulong> OK, no more questions from me then.
14:29:12 <slaweq> but qos meeting isn't changed
14:29:19 <slaweq> ok, so lets move on
14:29:25 <slaweq> #topic Blueprints
14:29:32 <slaweq> Blueprints for Ussuri-1: https://launchpad.net/neutron/+milestone/ussuri-1
14:30:02 <slaweq> I added to this list also RFEs approved recently (or those which we talked about in Shanghai and we want to work on them)
14:30:56 <slaweq> during this week I will contact with people who proposed those rfe if they will work to implement that
14:31:05 <slaweq> and if we can assign it to them
14:31:29 <slaweq> I have also one question about those RFEs: do You think we should have BP opened for each of them?
14:31:37 <slaweq> or RFE is enough?
14:32:10 <ralonsoh> depends on the size of this feature and dependencies
14:32:31 <ralonsoh> if the RFE needs some patches and no dependencies from othre features, a bug is enough
14:32:49 <ralonsoh> BP where used before for nova-neutron features, with n-lib and os-vif dependencies
14:33:01 <ralonsoh> (and OSsdk and OSclient ones)
14:33:04 <njohnston> I think an RFE might be good for the bulk tagging RFE in order to make sure we fully flesh out the API
14:33:17 <njohnston> sorry, a BP might be good for the bulk tagging RFE
14:33:31 <slaweq> ok, I see Your point, You're both right
14:33:55 <slaweq> I will create Blueprints for those which I think that will require such changes around various projects
14:33:59 <ralonsoh> having a BP is not a big overhead
14:34:14 <njohnston> +1 thanks
14:34:23 <ralonsoh> +1
14:34:35 <slaweq> ok
14:35:04 <slaweq> if You have any other BP/RFE which should be target to Ussuri-1 and tracked here, please ping me after the meeting
14:35:09 <slaweq> I can add it to the list
14:36:03 <slaweq> and as for now, do You have any updates about BPs/RFEs from this list?
14:36:11 <slaweq> or can we move on to the next section?
14:37:27 <slaweq> ok, lets move on than :)
14:37:29 <slaweq> #topic Community goals
14:37:40 <slaweq> as for community goals, we have one new on the list
14:37:46 <slaweq> Drop Python 2.7 Support
14:37:56 <slaweq> it is already accepted goal for Ussuri
14:38:13 <slaweq> njohnston - do You want to be "owner" of this one on Neutron's side?
14:38:28 <njohnston> sure!
14:38:33 <slaweq> thx a lot
14:39:04 <slaweq> as for other goals which are proposed, I will add them to this list when will be accepted by TC
14:39:24 <njohnston> for this goal I will be guided by the decisions written down in https://etherpad.openstack.org/p/drop-python2-support from the TC discussion
14:40:24 <slaweq> so I think that this is all about community goals for today
14:40:35 <slaweq> #topic Bugs
14:41:00 <slaweq> As we didn't have this meeting for few weeks, we have 3 different reports to mention:
14:41:11 <slaweq> Bugs report for week of October 28th: http://lists.openstack.org/pipermail/openstack-discuss/2019-November/010521.html
14:41:19 <slaweq> Bugs report for week of November 4th: http://lists.openstack.org/pipermail/openstack-discuss/2019-November/010676.html
14:41:24 <slaweq> Bugs report for week of November 11th: https://docs.google.com/spreadsheets/d/1DdWgFhMWrK67YJHBgzSbnOcFprQbOLFM16WQcPt0RS8/edit#gid=0
14:42:21 * njohnston is ready to go for bug deputy starting the 25th
14:43:40 <slaweq> njohnston: thx, but first this week is mlavalle on bug deputy :)
14:44:31 <slaweq> as for bugs from those reports, I would like to ask L3 subteam to take a look at https://bugs.launchpad.net/neutron/+bug/1851659
14:44:32 <openstack> Launchpad bug 1851659 in neutron "removing a network from a DHCP agent removes L3 rules even if it shouldn't" [High,New]
14:44:45 <slaweq> which is marked as High
14:45:19 <slaweq> we have also gate failure related to networking-sfc: https://bugs.launchpad.net/neutron/+bug/1851500
14:45:19 <openstack> Launchpad bug 1851500 in neutron ""test_show_port_chain" conflicts with Flow Classifier" [Medium,Confirmed]
14:45:40 <slaweq> so I will try to ask dkushwaha if he can take a look at this
14:46:07 <slaweq> and we have https://bugs.launchpad.net/neutron/+bug/1851194 which is related to FWaaS so I'm not sure if there will be anyone to take a look at it
14:46:08 <openstack> Launchpad bug 1851194 in neutron "FWaaSv2 configures iptables with invalid port name" [Medium,New]
14:46:47 <slaweq> any other bugs You want to talk about today?
14:48:26 <slaweq> ok, I will take that as "no" :)
14:48:31 <slaweq> so lets move on
14:48:38 <slaweq> next topic is new in agenda
14:48:41 <slaweq> #topic Networking OVN and ML2+OVS+DVR Convergence
14:48:59 * haleyb waves
14:49:12 <slaweq> as we discussed in Shanghai, I proposed to remove old meeting https://review.opendev.org/694991
14:49:42 <slaweq> now it's haleyb turn - do You have anything else to talk about for today?
14:50:53 <haleyb> slaweq: i will touch base with you regarding sending an email to the ML
14:51:08 <slaweq> haleyb: ok
14:51:17 <haleyb> i will also update the spec one more time...
14:51:26 <slaweq> tbh I forgot about this email :/ sorry for that
14:51:55 <haleyb> np, blame it on jetlag
14:52:06 <slaweq> haleyb: ok :)
14:52:07 <slaweq> thx
14:53:22 <slaweq> anything else related to the ovn for today? or can we move on?
14:54:02 <haleyb> i don't have anything today
14:54:26 <slaweq> ok, so lets move on to the last point for today
14:54:28 <slaweq> #topic On Demand agenda
14:54:43 <slaweq> there is no any topics in meeting agenda
14:54:53 <slaweq> but maybe someone wants to talk about something?
14:55:03 <slaweq> if so, You have about 5 minutes
14:56:37 <slaweq> ok, I guess that there is no more topics for today than
14:56:47 <slaweq> so thx for attending and have a great week
14:56:50 <slaweq> o/
14:56:52 <bcafarel> o/
14:56:53 <slaweq> #endmeeting