21:00:22 #startmeeting networking 21:00:22 Meeting started Mon Aug 20 21:00:22 2018 UTC and is due to finish in 60 minutes. The chair is mlavalle. Information about MeetBot at http://wiki.debian.org/MeetBot. 21:00:23 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 21:00:25 The meeting name has been set to 'networking' 21:00:29 o/ 21:01:12 quite day today, it seems 21:01:30 hi 21:01:32 hi o/ 21:01:35 #topic Announcements 21:02:22 Agenda for today is here: https://wiki.openstack.org/wiki/Network/Meetings 21:02:48 and the first announcements is a follow up to a conversation slaweq and amotoki had last week 21:03:14 we are supposed to tag the neutron tempest plugin 21:03:34 I am in agreements with doing it 21:03:45 that's the expectation of the community 21:04:30 cool 21:04:51 and the employer of all the people who raised their hand indicating they are in attendance of this meeting also requires it 21:05:14 :) 21:05:16 so let's do it and support our downstream pckagers 21:05:24 +1 21:06:08 we don't have any reason not to tag it, right? 21:06:23 nothing I can think of 21:06:25 o/ 21:06:43 after all, a tag is easy to ignore should one wish to do so 21:07:05 only if you really prefer to see a git hash instead of a pretty version 21:07:32 ok, I assume amotoki will read the log of this meeting and will help us with the tagging process 21:08:35 The other thing is that we have merged a few thinks in stable rocky over the past week 21:09:15 I guess we should update our tag for that branch as well, before the release 21:09:21 any objections? 21:10:04 mlavalle: so RC2? 21:10:51 mhhhh, yeah you are right. I'll check with the release guys to se what they think 21:11:12 what I had in mind was this https://review.openstack.org/#/c/590580/ 21:11:54 which is the cherry on top port forwarding... thanks hongbin 21:12:03 I'll check with them 21:12:12 I am happy with our RC-1 21:12:28 but maybe we could merge also few other fixes before releasing RC2 (if that will be the case here) 21:12:49 here is full list of opened patches now: https://review.openstack.org/#/q/status:open+project:openstack/neutron+branch:stable/rocky 21:12:58 ok, I'll check with the release guys and if they are ok with it, will do it 21:13:07 for example fixes for logging API are maybe worth to include them 21:13:16 ++ 21:14:17 The final announcement I have is the PTG 21:14:42 Please remember that we are collecting topics in this etherpad: https://etherpad.openstack.org/p/neutron-stein-ptg 21:15:23 and I'm lloking forward to see you all in Denver in 3 weeks 21:15:49 any other announcements? 21:16:36 ok, let's move on 21:16:45 #topic Blueprints 21:17:08 I think we already cover this topic when we talked about above about the possible rc-2 21:17:24 does anybody have anything else to say on blueprints? 21:18:34 ok, moving on 21:18:44 #topic Community goals 21:19:10 I updated this section with the community goals relevant for Stein 21:19:48 njohnston: please note I updated the python 3 one with the heading and the point to the goal escription in Stein 21:19:58 I did notice that :-) 21:20:41 I also added the other community goal for Stein, "Support Pre Upgrade Checks" 21:20:52 it is looking for a volunteer 21:21:26 I'll let it there until next week,. If nobody claims it, I'll volunteer myself 21:22:17 mlavalle: I will take a look at this goal for Stein 21:22:22 anything else to mention today on community goals for Stein? 21:22:29 slaweq: yes, feel free 21:22:35 thx 21:23:00 ok, let's move on 21:23:08 #topic Bugs 21:23:31 our bugs deputy last week was pasuder 21:24:08 here's his update to the mailing list: http://lists.openstack.org/pipermail/openstack-dev/2018-August/133494.html 21:25:04 so it seems it was a relatively quiet week 21:25:46 He marked those potential RFEs correctly. I'll triage them further 21:26:04 I'll also take a look at the DNS extension one 21:26:50 slaweq: you gave me a bug this morning but I meesed up my browser tabs. Was it https://bugs.launchpad.net/neutron/+bug/1787420? 21:26:50 Launchpad bug 1787420 in neutron "Floating ip association to router interface should be restricted" [Undecided,Triaged] 21:27:31 no, I was asking You to take a look at https://bugs.launchpad.net/neutron/+bug/1786272 21:27:31 Launchpad bug 1786272 in neutron "Connection between two virtual routers does not work with DVR" [Medium,New] - Assigned to Brian Haley (brian-haley) 21:27:50 slaweq: ok, I'll do it most likely tomorrow morning 21:28:00 no problem :) 21:28:02 thx 21:28:30 anything on bugs or pasuder's report that I am missing? 21:29:40 ok 21:29:58 our deputy for this week is hongbin 21:30:06 yes, i am on it 21:30:09 so we are well covered 21:30:36 moving on 21:30:46 #topic Ryu support 21:31:48 hongbin: I suspect you have an update here. I know there was discussion on the naming 21:31:57 mlavalle: yes 21:32:01 #link https://review.openstack.org/#/c/588358/ 21:32:27 above is the governanent patch and the feedback from reviewers is to pick a better name for the library 21:32:52 toshi made the point that the original developer doesn't want us to use "Ryu" in any way, right? 21:32:54 the original proposed name is 'os-ryu' and the reviewers had concerns about this name 21:33:17 mlavalle: yes 21:33:42 so we need to pick another name for the library? 21:34:00 any suggestions? 21:34:07 I have one 21:34:11 "Ken" 21:34:23 that's good, but why? 21:34:24 as it was friend of Ryu from Street Fighteer game :) 21:34:31 https://en.wikipedia.org/wiki/Ryu_(Street_Fighter) 21:34:38 https://en.wikipedia.org/wiki/List_of_Street_Fighter_characters 21:34:50 that's actually a pretty good suggestion 21:35:32 what do you think hongbin? 21:35:45 mlavalle: sure, i think it is good name :) 21:35:58 wow, these Neutrinos are so smart 21:36:12 :) 21:36:29 what was the origin of ryu name? (and +1 on picking up another SF fighter) 21:36:32 so would it be os-ken? I see there is already a ken on pypi (not surprising) https://pypi.org/project/ken/ 21:37:00 os-ken sounds good to me 21:37:10 +1 21:37:10 ryu was some game character 21:37:31 iwamoto_: ah ok, so we are in the same wavelength 21:37:48 good so os-ken would keep the tradition then 21:38:08 it makes perfect sense, because our fork will always be friends with Ryu 21:38:11 and ryu is "flow" in japanese 21:38:43 mlavalle: that's why I was looking for friend of Ryu from this game :) 21:38:47 ken is also an english noun, meaning "one's range of knowledge or sight" 21:39:29 which is not bad 21:39:35 dang, we came up with a name full of meaning and mythology. I'm excited 21:39:52 :) 21:40:17 hongbin: you can point to this discussion in the patch to convey why we chose this name 21:40:27 mlavalle: sure, i will do that 21:40:50 anything else on the Ryu effort today? 21:41:11 have we talked about ryu ci? 21:41:32 hongbin: you'll do CI adaption for openstack? 21:41:38 iwamoto_: no, we didn't 21:42:13 iwamoto_: about ci adaption, i need to investigate on it, originally, i will try to add some pep8 and py3 tests 21:42:16 one minor issue is i'm not plannig to go ptg, but i think we can discuss later 21:42:18 iwamoto_: we haven't yet, but yes, we understand it has to be done 21:42:45 hongbin: I can help with that if You want 21:42:53 +1 to help 21:42:55 slagle: great. thanks 21:43:04 slagle: sure, wrong person 21:43:10 LOL 21:43:25 * hongbin blames auto-completion 21:43:37 hongbin: I suggest having a conversation in channel with iwamoto_ and then probably discuss it in the PTG 21:43:37 3rd try will be a charm 21:43:54 mlavalle: ack, i can do that 21:44:17 mlavalle: if I can join online that would be great 21:44:19 please add it to the therpad 21:44:42 iwamoto_: I'll see what we can do. I'll keep you posted 21:44:59 * iwamoto_ will miss train horns 21:45:11 LOL 21:45:20 anything else? 21:46:08 ok, let's move on 21:46:14 #topic neutron-lib 21:46:33 I don't think boden is around/ Are you? 21:47:13 ok, let's move on 21:47:20 #topic Open Agenda 21:47:26 slaweq: you have a topic 21:47:32 yes, thx 21:47:54 I just wanted to say that I would like to use again script https://github.com/openstack/neutron/blob/master/tools/abandon_old_reviews.sh 21:48:13 to abandon some old patches without any acitvity for some long time 21:48:39 I know that it was used by Kevin and (probably) armax in the past 21:49:05 yeah I recall some messages by armax like that 21:49:13 Just to note, that would abandon old patches in all repos covered under neutron's governance according to the governance repo, so all stadium projects. IIUC. 21:49:29 and I wanted to ask if anyone see any reason why we shouldn't maybe do it 21:49:31 I think it might actually date to mestery's days, not sure 21:50:11 Let's send a message to the ML 21:50:13 do other project do that? 21:50:36 with a proper heads-up for stadium (and neutrinos), +1 for restarting this 21:50:38 don't know, but traditionally we have done it 21:50:46 iwamoto_: I saw recently similar changes in Mistral IIRC 21:50:48 I think it is a great idea; the oldest change we have still active in neutron was last updated 2016-05-30 21:51:09 yeah, let's warn the Stadium 21:51:12 (that is change 322158 BTW) 21:51:17 that this is coming 21:52:02 ok, I will send email with information about that to ML 21:52:29 let's highlight it includes the Stadium 21:52:39 mlavalle: ok, I will do that 21:52:46 and thanks for taking charge of this slaweq 21:52:51 I will send it tomorrow morning 21:53:05 or can I also call you slagle? 21:53:50 mlavalle: LOL, I think You can, but I don't know what will original slagle tell about it ;) 21:54:09 ok cool 21:54:21 any other topics to discuss today? 21:54:31 Did we miss the section on OVO/upgrades? 21:54:51 we did, it's the jet lag 21:54:58 any updates on that? 21:55:16 We are progressing slowly, right now the team seems to be lujinluo, TuanVC, hungvp, lajoskatona, hongbin, slaweq, and myself 21:55:32 We recently expanded our scope to include database decorators 21:56:35 how does this play with finalizing the adoption of the DB facade? 21:57:00 maybe we can discuss this coming Thusday? 21:57:12 Yes, let's definitely do that. 21:57:30 ok, I'll attend the meeting this coming Thursday 21:57:38 And I would say that if anyone is looking for a fertile ground for contribution, there is still a lot of work to do in the upgrades project. 21:57:41 and we talk about it 21:57:55 cool 21:58:00 thanks! 21:58:05 thanks for the update njohnston 21:58:21 ok, have great week team 21:58:26 #endmeeting