14:00:03 #startmeeting networking 14:00:04 Meeting started Tue Feb 13 14:00:03 2018 UTC and is due to finish in 60 minutes. The chair is jlibosva. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:05 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:07 Hi everybody :) 14:00:08 The meeting name has been set to 'networking' 14:00:09 hi 14:00:18 #topic Announcements 14:00:45 The rc1 has been cut and as far as I understand the master branch is the Rocky branch now 14:01:22 Which means only critical fixes need to go to queens at this stage 14:01:26 o/ 14:01:36 and the release week is at the week of Feb 26 14:01:52 mlavalle: hi, I just updated that we cut rc1 and master is Rocky now. Is that correct? :) 14:02:06 as always, you are correct :-) 14:02:36 thanks for confirmation :) 14:03:16 next announcement is that at the same week, the PTG is happening in Dublin 14:03:28 if you have a topic you want to discuss there, please put it to the etherpad 14:03:30 #link https://etherpad.openstack.org/p/neutron-ptg-rocky 14:03:50 I started arranging the topics by day and hour yesterday 14:03:54 that's all from me :) 14:04:35 as I assign sessions to days and times, please feel free to add your topic to the session that best fits it 14:05:04 if you don't find any that fits, just throw it in the general section at the top and I'll assign it 14:05:31 one note from me: I see that the list of attendees is just mlavalle :) perhaps those attending can write their names down there ;) 14:05:49 also I added yesterday a section at the very top for atendees to register your name 14:06:15 the format is: name (irc nickname) days staying in Dublin 14:06:26 please register if you are going to Dublin 14:06:42 the reason is that we are going to have a social event on Thursday 14:07:08 so I want to have an accurate head count to make a reservation for the group dinner 14:07:18 IO'll send a message to the ML later today 14:07:33 that's it 14:07:35 thanks :) 14:07:49 does anybody have any other announcement? 14:08:08 ok, moving on 14:08:10 #topic Blueprints 14:08:45 I'm looking at the LP: https://launchpad.net/neutron/+milestone/queens-rc1 14:09:00 looks like there are no blueprints that made it to rc, that's good 14:09:45 does anybody have anything to add regarding blueprints here? 14:09:53 there is a bug related to ovsfw 14:10:06 that slaweq was working on 14:10:21 and we wanted jlibosva's opinion on the patch 14:10:32 mlavalle: I think it is merged already 14:10:33 did you have a chance to look at it? 14:10:41 mlavalle: https://review.openstack.org/#/c/542257/ ? 14:10:46 jlibosva approved :) 14:10:46 #topic Bugs 14:10:56 ah perfect 14:10:56 since we're already talking about the bugs :) 14:11:03 thanks slaweq for the patch! 14:11:10 no problem 14:11:19 we want to port it to Queens 14:11:32 and that is what is going to be our RC2 14:11:37 so far 14:11:44 I hope that together with https://review.openstack.org/#/c/542596/ it will make tempest tests green 14:12:03 mlavalle: I will do cherry-picks today 14:12:03 mlavalle: good point, it's a clean cherry-pick https://review.openstack.org/#/c/543944/ 14:12:13 slaweq: oh, sorry, I just tried to click the button and it worked :) 14:12:37 jlibosva: thx 14:12:38 :) 14:12:43 hi I was on bug duty last week, but I have to step away in 1 min for a short bit… the only critical bug I saw come in was https://bugs.launchpad.net/neutron/+bug/1748546 which you just discussed 14:12:46 Launchpad bug 1748546 in neutron "ovsfw tempest tests random fails" [High,Fix committed] - Assigned to Slawek Kaplonski (slaweq) 14:12:46 cool 14:12:51 I think that https://review.openstack.org/#/c/542596/ should be also cherry-picked 14:13:23 yep 14:13:23 boden: yeah, that's the fix we are talking about. Thanks ! 14:13:29 however I see some bugs came in over the past few days so someone prob needs to take a pass through the new ones 14:13:45 I also see there is also one bug scheduled to rc: https://bugs.launchpad.net/neutron/+bug/1713499 14:13:46 Launchpad bug 1713499 in neutron "Cannot delete a neutron network, if the currently configured MTU is lower than the network's MTU" [High,In progress] - Assigned to Reedip (reedip-banerjee) 14:14:15 that one we decided last week that we are going to merge it early in Rocky 14:14:30 actually I am taking it over to make sure we fix it 14:14:48 mlavalle: ack. do you know who can create a rocky milestone at the Launchpad? 14:15:02 and then we will backport it to Queens 14:15:12 jlibosva: I'll take care of that today 14:15:40 thanks, I added queens-backport-potential tag to it 14:15:47 perfect 14:16:05 I will send an email announcing it later today as well 14:16:16 ok 14:16:39 as boden said, we had some incoming bugs that need to be triaged, for this week bug deputy should be janzian 14:16:49 janzian: hi, are you online? 14:17:14 if he is not, I'll ping him later today 14:17:24 He is my Austin neighbor ;-) 14:17:35 nice :) 14:17:44 thanks mlavalle 14:17:52 anything else related to bugs? 14:18:00 before we go on, I have something very important to announce 14:18:10 drum rolls....... 14:18:15 drrrrr 14:18:24 jlibosva just became a Dad 14:18:31 oh, lol 14:18:34 thanks! :D 14:18:37 so please join me in congrtulating him 14:18:45 wow, congratulations!!!!! 14:18:46 mlavalle: how do you know? 14:18:52 boy or girl? 14:18:52 +2 to a little neutronian 14:18:59 mlavalle: also why is it in the bugs section? :D 14:19:06 LOL 14:19:07 mlavalle: it's a girl named Sara 14:19:19 mom a baby ok? 14:19:25 and baby^^^ 14:19:31 they are, thanks :) 14:19:44 haleyb pinged me and let me know 14:19:45 that said, I won't be reachable next few weeks 14:19:50 probably three 14:19:57 so I'll be back after the PTG, hopefully :) 14:20:09 mlavalle: thanks, that was a surprise to me you announced it :D 14:20:17 have fun jlibosva :) 14:20:19 * haleyb buys some diaper stocks 14:20:21 of course, go enjoy your baby 14:20:22 slaweq: thanks :) 14:20:30 ok, moving on :) 14:20:38 #topic Docs 14:20:58 boden: hi, are you still here? 14:21:06 he is not 14:21:15 he is taking kid to school 14:21:19 oh 14:21:23 7:21am his time 14:21:26 he stepped out 14:21:49 he also pinged me on the side 14:21:57 mlavalle: using 'whois' or he is also your neighbour? :) 14:21:59 ah, ok 14:22:11 amotoki: are you still here? 14:22:12 he is my time zone neighbor 14:22:20 he is in the Denver area 14:22:25 everyone is a neighbour of mlavalle :D 14:23:30 seems like it's too late there. does anybody have anything related to the docs? 14:23:55 just to say 14:24:10 that if you have interest in dcos and you are attending the PTG 14:24:23 there will be a docs track the first day day 14:24:26 let me confirm 14:25:00 actually, Monday and Tuesday: 14:25:08 #link https://www.openstack.org/ptg/#tab_schedule 14:25:38 that's it 14:25:56 thanks 14:26:15 jumping to the next topic 14:26:18 #topic Transition to OSC 14:26:50 with amotoki afk, does anybody have anything? 14:27:01 I don't 14:27:18 perhaps https://review.openstack.org/#/c/534085/ should land? 14:27:37 good point 14:27:47 I'll take a look at the end of the meeting 14:28:08 ok, thanks 14:28:10 moving on 14:28:12 #topic neutron-lib 14:28:37 0/ 14:28:41 hey 14:28:48 you made it back, nice 14:28:53 nice :) 14:29:03 I was just about to repeat what was said last week with the api-ref :) 14:29:19 boden: you were fast. I hope you didn't break the speed limit ;) 14:29:31 jlibosva: that shows you some skills that you need to learn now that you are a Dad 14:29:37 lol 14:29:48 now that we are in Rocky mode, things are returning to normal.. you’ll start to see both lib and consumption patches surface again 14:30:35 I’ve also started to “re-kick” the neutron-lib database related specs… I’ve got some PoC patches out there.. I hope we can work through some of these topics in Rocky 14:30:41 yeap, boden pinged yesterday at the first possible moment to make sure we can start merging things. Super diligent ;-) 14:31:19 1 last quick thing on lib 14:32:00 garyk brought up a high-level migration path concern on the LBaaS deprecation work https://review.openstack.org/#/c/542846/ 14:32:11 if anyone has comments please see ^ 14:32:25 that’s it for me unless others have want to add something 14:32:55 boden: thabks for pointing that out 14:33:18 and I just want to highlight the two specs that boden added to the PTG etherpad 14:33:39 #link https://review.openstack.org/#/c/473531 14:34:00 #link https://review.openstack.org/#/c/509564/ 14:34:10 chime in if you have a chance 14:34:32 that's all from me 14:34:48 thanks folks 14:34:56 anybody else has anything related to the lib? 14:35:25 ok, we have plenty of time today :) 14:35:27 #topic On demand agenda 14:35:57 I added one topic to the wiki that slaweq and I want to discuss: https://wiki.openstack.org/wiki/Network/Meetings#On_Demand_Agenda 14:36:21 there was a ML thread earlier in Sept about typo fixing patches: http://lists.openstack.org/pipermail/openstack-dev/2017-September/122472.html 14:36:39 you can see an example of a such patch here: https://review.openstack.org/#/c/540225/ 14:37:33 I wanted to get some consensus about what to do as a core reviewer. as similar patches have some small value, I personally don't think it's worth to load CI with them and I would welcome if such patches come with multiple fixes 14:39:09 what are your opinions? what should we be doing in these cases? just a small note that all similar patches come from the same email domain 14:39:19 I think that if the behavior is recurring, we should probably stop it 14:39:20 and it's just not Neutron 14:40:01 specifically this group from inspur seem to be trying to game the numbers 14:40:50 so I would sugest that if we see that it becomes a recurring behavior, flag it with a -2 14:41:12 and indicate in the comment that it is recurring behavior 14:41:13 do you think it would be healthy to provide an argument to find multiple typos? 14:41:32 like.. I don't know, 20 typos per patch or something :) 14:41:46 jlibosva++ 14:41:51 and in the docs as comments are not operator facing 14:42:39 jlibosva: would you propose a patch to the contributors guide with a policy proposal on this regard? 14:42:46 and related to that, if such patch comes, can we somehow throw it from the check queue? 14:42:50 mlavalle: yes, that's a good idea 14:42:54 that way we can discuss / refine it in gerrit 14:43:11 I agree with that 14:43:20 * jlibosva nods 14:43:29 thanks for help on that :) 14:43:31 that way we have a formal guideline 14:43:51 and also, when we reject patches, we can point to a policy in the comment 14:43:57 I read the whole thread on the ML but there doesn't seem to be any consensus, so we can solve it at least on a project level this way 14:44:07 yeap 14:44:27 alright, we have a next step then. does anybody have any other topic to discuss? 14:44:45 just to let the team know that this meeting 14:44:53 will be cancelled in two weeeks 14:45:03 because we will be in Dublin in the PTG 14:45:19 enjoy the PTG folks :) 14:45:32 so next Tuesday meeting will be on March 13th 14:45:57 that's all I had 14:46:06 thanks 14:46:17 and thanks everyone for coming 14:46:20 #endmeeting