14:00:57 #startmeeting networking 14:00:58 Meeting started Tue Dec 3 14:00:57 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:59 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:01:01 The meeting name has been set to 'networking' 14:01:03 o/ 14:01:10 hi 14:01:19 hello 14:01:28 o/ 14:01:36 hi 14:04:26 o/ 14:04:46 ok, let's start 14:04:55 #topic Announcements 14:05:17 We are still looking for new maintainers for some of stadium projects: 14:05:25 neutron-fwaas: http://lists.openstack.org/pipermail/openstack-discuss/2019-November/010929.html 14:05:32 and neutron-vpnaas: http://lists.openstack.org/pipermail/openstack-discuss/2019-November/010931.html 14:05:52 * mlavalle is surprised I didn't miss the annoucements 14:06:15 so if You know anyone interested in this project, please talk to them about it :) 14:06:24 hi 14:06:27 next one 14:06:31 Removing of neutron-interconnection from stadium project is almost done: https://review.opendev.org/#/q/branch:master+topic:neutron-interconnection-retire 14:06:38 We are waiting for last patch https://review.opendev.org/#/c/694480/ to be merged 14:09:33 next one 14:09:35 We started process of moving networking-ovn code into neutron tree 14:09:49 we will cover that topic later today, as we have ovn related section in the agenda 14:10:02 but I just wanted to make sure, people are aware of it 14:10:12 BP is here: https://blueprints.launchpad.net/neutron/+spec/neutron-ovn-merge 14:10:24 Next one 14:10:26 Next week is Ussuri-1 milestone: https://releases.openstack.org/ussuri/schedule.html 14:10:37 time flies :) 14:10:58 do we want to release something next week maybe? 14:11:22 I don't think we have to but maybe You think it's worth to release on U-1 milestone? 14:12:00 stable releases? I don't remember on which milestones we said we would tag new ones 14:12:12 haleyb: do You know? 14:12:47 i added info that we'd tag stable releases each milestone as well 14:12:56 it's in doc/ somewhere :) 14:13:15 ok, so we should tag stable releases next week, right? 14:13:47 yes, so we should look at what's in process and merge what we can 14:14:10 * bcafarel moves "go through stable reviews" up his todo list 14:14:15 bcafarel: can You take a look at it next week than? 14:15:48 ok, lets move on than 14:15:53 slaweq: sure 14:15:58 thx bcafarel :) 14:16:04 last announcement for today: 14:16:06 I proposed patch to add review priority also to stadium projects: https://review.opendev.org/#/c/696628/ 14:16:27 we have it already in neutron so I though that it could be useful to have it also in stadium projects as well 14:16:35 I hope You are fine with that :) 14:17:00 +1 14:17:08 makes sense, especially for important reviews that could benefit from neutron cores (like gate breakages) 14:17:13 +1 14:17:14 especially in neutron-lib 14:17:20 yeah 14:17:38 actually I found that we don't have it for stadium when I wanted to set it for some neutron-lib patches :) 14:17:43 that's why I proposed that 14:17:52 so the relevant dashboard will be updated for them? (or they already include them) 14:18:20 bcafarel: it already should include them 14:18:50 nice, no need to update the bookmark :) 14:19:17 ok, that's all announcements from me 14:19:25 anything else You want to announce today? 14:19:59 one thing the octavia reviews show is a "Backport Candidate" vote, might be useful eventually in neutron, but don't want to add too much stuff to that button 14:20:41 just related to your adding the Importance vote 14:20:48 haleyb: sounds interesting, do You have link to octavia example? 14:21:06 it's new vote category or just anoter value of same vote? 14:21:08 https://review.opendev.org/#/c/687370/ - for example, that's upstream only 14:21:29 * haleyb looks for one with a +2 14:21:56 https://review.opendev.org/#/c/696037/ - e.g. a should-be-backported one 14:22:02 slaweq: it's a vote 14:23:01 it would add yet another vote, and i already click on it by accident :) 14:23:40 thx haleyb 14:24:02 looks interesting but we already have tags in launchpad for that 14:24:16 so I'm not sure if we need yet another vote type for this 14:24:26 they use storyboard :-/ 14:24:29 but I'm open for it if team wants to have it 14:24:35 IMO, we don't 14:25:19 as long as we have no plans to move away from launchpad I think it is unnecessary 14:25:25 oh, you don't want storyboard for sure :) 14:25:30 :) 14:25:46 ok, so lets stick to the launchpad for now and we will be good ;) 14:25:50 +1 :) 14:25:55 and lets move on here to the next topics 14:25:59 #topic Blueprints 14:26:18 we have a lot of BPs scheduled for Ussuri-1: https://launchpad.net/neutron/+milestone/ussuri-1 14:26:47 we will ofcourse not have them finished on milestone 1 14:27:05 but I added them to be able to track RFEs which were accepted recently 14:27:23 good news is that almost all of them got assignee now 14:28:06 do You have maybe any updates about any of those BPs? 14:29:04 I am getting serious about custom ethertypes, working some on it this week 14:29:15 great njohnston 14:29:28 late o/ 14:30:03 I have started working on bulk tagging that was requested by the kuryr guys. You can add it to the dasboard 14:30:38 mlavalle: You mean this one https://blueprints.launchpad.net/neutron/+spec/tagging-on-post ? 14:31:14 yes 14:31:54 ok, I will assign it to You than 14:32:09 mlavalle: nice! i didn't know until two weeks ago the client creates, then adds a tag in a PUT after 14:32:10 mlavalle: after the meeting can we sync on enginefacade? I'd like to keep helping with that, just want to check where we are 14:32:56 njohnston: just not after the meeting. I have something else to do. I will ping you later 14:33:05 mlavalle: +1 thanks 14:34:44 ok, any other updates about blueprints? 14:34:49 if no, lets move on 14:35:17 ok, lets move on quickly 14:35:19 #topic Community goals 14:35:39 njohnston: any updates on dropping py2 support? 14:36:14 I created an etherpad: https://etherpad.openstack.org/p/neutron-train-zuulv3-py27drop 14:36:40 that tracks both py27 support drops as well as the other community goal of moving all jobs to zuulv3 14:37:07 ++ thx njohnston 14:37:16 Anyone who wants to jump in on the fun, please note in the etherpad what you're working on and post links to your changes, and we'll review them 14:37:27 I will try to pick some of points listed there and work on them next week probably 14:38:02 njohnston: what about removing things like six ? 14:38:45 this is a good example of a change to drop py27 testing: https://review.opendev.org/#/c/688278 14:38:51 haleyb: that's not part of the community goal 14:38:55 haleyb: So this is a common point of confusion 14:39:13 njohnston: is that a new etherpad from last week CI meeting's one? I thought I had added a sfc review link then (maybe just my memory though) 14:39:14 the community goal is only to *stop testing py27* 14:39:21 bcafarel: correct 14:39:52 Hi, if I understand well the goal is to stop testing py27, not removing compatibility code :-) 14:39:59 njohnston: not "burn the boats" ? 14:40:10 if a project decides to make it's code hostile to py27 (by removing six and/or other changes) then it's all right to do as long as you are very sure no other projects use your project as a library 14:40:12 haleyb: exactly 14:40:46 for example if neutron was to remove six it would break all the stadium jobs that still import neutron 14:41:18 so in the etherpad there is the cadence for removing py27 support in phases (labelled "retirement phases" 14:41:20 ) 14:41:21 maybe we can try to remove python 2 support completly in next cycle 14:41:21 njohnston: ack, it would take a while to remove things like six anyways 14:41:38 maybe we should start now 14:41:52 that way we do it slowly 14:42:20 fine to start now but keep a workflow minus-one on it until February 14th 14:42:41 ok 14:42:43 njohnston++ 14:42:57 any questions? 14:43:41 it's not a completely straightforward thing because of how projects can affect each other, I have tried to put as much as I know into the etherpad but if you have any problems or questions let me know, any time 14:44:35 that's it for me 14:44:40 thx njohnston for the update and prepare work plan 14:45:03 lets move on than 14:45:04 #topic Bugs 14:45:13 last week bug deputy was njohnston 14:45:23 but I didn't saw any report on ML 14:45:33 njohnston: do You have any bugs You want to discuss with the team? 14:45:37 Ah, I'll send out my notes 14:46:59 slaweq: ISTR you mentioned you wanted tot alk about https://bugs.launchpad.net/neutron/+bug/1853840 14:46:59 Launchpad bug 1853840 in neutron "Neutron fails to create bandwidth providers if CONF.host is set" [High,In progress] - Assigned to Bence Romsics (bence-romsics) 14:48:04 I need to add some tests so I can remove the WIP tag 14:48:16 yes, I was looking into that and I saw rubasov's patch 14:48:56 but despite the WIP feel free to look at it and tell me if you like the approach or not 14:49:10 it's largely as described on the ML 14:49:12 should we set higher review priority for this patch as soon as it will be no WIP anymore? 14:49:51 I'm okay with that 14:50:20 ok, I so lets set this flag once it will be ready for reviews 14:50:28 Other than that I think the only one unassigned yet is only importance medium: https://bugs.launchpad.net/neutron/+bug/1853873 14:50:29 Launchpad bug 1853873 in neutron "The /v2.0/ports/{port_id}/bindings APIs are not documented" [Medium,New] 14:50:56 that one can be assigned to me 14:51:05 thx mlavalle 14:51:19 done 14:51:49 that's all, it was a slow week 14:52:06 I'll send the full bug lish out to the ML right after the meeting 14:52:10 thx njohnston for the update 14:52:19 lets quickly go to the next topic 14:52:27 #topic neutron-lib 14:52:45 I just wanted to say here that I would like to release new neutron-lib version soon 14:52:56 I checked what patches are in review currently 14:53:11 and I think we should merge for patches: 14:53:20 https://review.opendev.org/#/c/695205/ 14:53:21 https://review.opendev.org/#/c/692580/ 14:53:23 https://review.opendev.org/#/c/696308/ 14:53:25 https://review.opendev.org/#/c/696070/ - merged 14:53:27 actually 3 still 14:53:31 and than release new version 14:53:54 as this will "unblock" work for some RFEs on neutron's side 14:54:12 slaweq, how often we do release of neutron-lib? 14:54:27 so please review those 3 patches and maybe check if I didn't missed anything what should also be included 14:54:39 maciejjozefczyk: we are doing it when needed 14:54:48 no specific rules for that 14:55:11 do You have anything else related to neutron-lib? 14:55:52 ok, so lets move on quickly 14:55:59 to the last topic for today 14:56:01 #topic Networking OVN and ML2+OVS+DVR Convergence 14:56:25 As I said at the beginning, we started merging networking-ovn code into neutron repo 14:56:26 Blueprint: https://blueprints.launchpad.net/neutron/+spec/neutron-ovn-merge 14:56:28 Proposed rehome plan: https://ethercalc.openstack.org/networking-ovn-migration 14:56:30 Planning Etherpad https://etherpad.openstack.org/p/neutron-networking-ovn-merge 14:56:32 Spec: https://review.opendev.org/#/c/658414/ 14:56:39 those are important links related to this effort 14:56:51 slaweq, sorry, for now nothing, but I'll have soonish, 14:56:54 haleyb: maciejjozefczyk lucasagomes do You have anything related to ovn for today? 14:57:09 this one might be also useful to folks: https://review.opendev.org/#/q/topic:bp/neutron-ovn-merge+status:open 14:57:26 mlavalle: yes, thx 14:57:31 it's in BP also 14:57:36 slaweq: nothing other than we have a few patches up for review related to the migration if anyone wants to take a look at them 14:57:55 slaweq: just wanted to thank everyone for the quick work, and core's for reviewing the changes 14:58:00 lucasagomes: I just posted the gerrit topic above 14:58:15 mlavalle: thanks! 14:59:15 so in that ethercalc sheet, can I assign an item to me? 14:59:25 mlavalle: sure 14:59:26 absolutely 14:59:27 mlavalle, sure!:) 14:59:43 please sync with maciejjozefczyk and lucasagomes as they are driving it from networking-ovn team :) 15:00:29 ok, I think we are out of time already 15:00:39 FYI we're planning to move OVN Octavia provider driver to separate repository, https://review.opendev.org/#/c/697076/; comments about the ACL configuration are welcome :) 15:00:43 thx for attending and have a great week 15:00:47 #endmeeting