14:00:58 #startmeeting networking 14:00:59 Meeting started Tue Apr 24 14:00:58 2018 UTC and is due to finish in 60 minutes. The chair is jlibosva. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:01:01 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:01:01 hello friends 14:01:02 hi 14:01:03 The meeting name has been set to 'networking' 14:01:06 o/ 14:01:09 hi 14:01:12 o/ 14:01:19 #link https://wiki.openstack.org/wiki/Network/Meetings 14:01:25 this is the agenda for the meeting 14:01:31 hi 14:01:32 #topic Announcements 14:02:06 we got a first milestone cut last week 14:02:35 o/ 14:03:01 neutron-lib is planned to be released this week 14:03:02 o/ 14:03:27 next announcement is that we're looking for a QA liaison! 14:03:30 #link https://wiki.openstack.org/wiki/CrossProjectLiaisons#QA 14:03:54 * mlavalle filling that gap for the time being 14:04:01 mlavalle++ 14:04:34 the next announcements are related to the next upcoming Summit in May 14:04:49 we got approved some topics at The Forum 14:05:11 first is about the future of RYU library 14:05:12 #link http://forumtopics.openstack.org/cfp/details/136 14:05:28 I don'Not necessarilly approved yet. They were proposed 14:05:32 aaah 14:05:34 sorry 14:06:02 np 14:06:30 ok, next proposed topic at the forum is the traditional nova-neutron + ops cross project session 14:06:31 #link http://forumtopics.openstack.org/cfp/details/124 14:06:31 hi 14:06:36 bcafarel: hi 14:06:54 and next two are about logging api 14:06:56 #link http://forumtopics.openstack.org/cfp/details/143 14:06:58 and fwaas 14:07:07 l7 filtering 14:07:12 #link http://forumtopics.openstack.org/cfp/details/144 14:07:39 also there is an etherpad with Vancouver summit participants 14:07:41 #link https://etherpad.openstack.org/p/YVR-neutron-atendees 14:07:54 if you plan to arrive to this great event, please sign up your name there 14:08:04 There will be a team dinner on Tuesday of that week 14:08:31 Traditionally we do it on Thursday, but this time the event end on Thursday, so many folks might be gone that night 14:08:32 I recommend to go there as it's usually fun and you meet your fellas there :) 14:09:05 that URL is missing a "t" :) 14:09:43 bcafarel: LOL.... thanks for the review. it's my fault 14:09:45 bcafarel: nitpicker :) 14:10:07 always :) 14:10:54 last announcement from me is that Rocky TC elections has begun today so you should have got your voting billet in your mailbox :) 14:11:00 mlavalle: do you have anything else? 14:11:15 Nope, thanks! 14:11:48 ok, let's move on 14:11:56 unless anybody else has anything to add 14:12:12 #topic Blueprints 14:12:24 we're now in the rocky-2 milestone 14:12:39 #link https://launchpad.net/neutron/+milestone/rocky-2 14:13:17 does anybody want to give an update on any rfe being worked on? 14:13:26 any issues that are worth attention of the team? 14:13:37 Just an update on multiple port bindings 14:14:26 Yesteday we acomplished the first change of backend in history for a port using multiple port bindings 14:14:49 *clap clap clap* 14:14:52 in my test environment. I moved a port from a binding with OVS to Linux bridge 14:15:13 and the port's dataplane continued comunicating normally 14:15:38 so I think we are very close to merge the big ML2 patch that I've been working for the past few months 14:16:02 That will enable the NOva team to conduct their testing 14:16:07 nice 14:16:51 I will also create a fullstack test. I've been using namespaces in my testing to simulate instances, so that will probably translate easily to a full stack test 14:17:09 that's all on that update 14:17:11 nice 14:17:18 mlavalle: if you'll need any help with fullstack, let me know :) 14:17:29 you bet... Thanks 14:18:24 annp: do you want to give an update about your wsgi work? I think you have some success there too, don't you? 14:19:23 jlibosva, we have community goal session right? 14:19:42 annp: right, sorry I mixed it with rfe :) 14:19:48 * mlavalle wants to ask a question after others are done with their blueprints updates 14:19:49 So please go ahead, I will update something In there. 14:20:12 mlavalle: seems like they are :) 14:20:52 Yesterday, while reviewing progress on blueprints I realized that https://blueprints.launchpad.net/neutron/+spec/get-policy-from-neutron-lib doesn't have an assignee 14:21:14 I think the asignee should be amotoki and someone else should be the approver (maybe me) 14:21:20 is amotoki around? 14:21:35 mlavalle: hi 14:21:47 amotoki: ^^^^ 14:22:07 do you think you should be the assignee? 14:22:15 yeah, I think so 14:22:25 ok, I will the approver then 14:22:32 thanks 14:22:56 I just noticed the previous assignee cleared him. 14:23:35 Done 14:24:03 ok, I think we can move on then 14:24:12 #topic Community goals 14:24:24 can we go back to brluprints? 14:24:35 #undo 14:24:36 Removing item from minutes: #topic Community goals 14:24:40 THanks! 14:24:59 I want to highlight the OVO work that is going on 14:25:41 The OVO team maintains a very well organized spreadsheet of work done, in progress and pending: 14:25:48 #link https://docs.google.com/spreadsheets/d/1Mz7V40GSdcUH_aBoNWjsFaNRp4wf-duz1GFWligiNXc/edit#gid=1051788848 14:26:17 Please take a look and if you find something you want to work on and is open, please pick it up and add your name to it 14:26:50 They also meet every Thursday at 1400UTC. They'll be happy to welcome you in their weekly meeting 14:27:15 #link http://eavesdrop.openstack.org/#Neutron_Upgrades_Meeting 14:27:32 lujinluo does a great job chairing that meeting 14:27:47 That's it. Thanks 14:27:55 thanks for updates 14:28:09 now jumping to the next topic :) 14:28:11 #topic Community goals 14:29:00 so as I see in the logs from the last week meeting, slaweq has completed the "Enable mutable configuration" goal, right? 14:29:05 should we remove it from wiki then? 14:29:33 not yet. there was some concern about the impact for subprojects 14:29:34 slaweq, ++ 14:29:59 slaweq was going to follow up with amessage to the ML, which I haven't seen 14:30:03 ok 14:30:05 * mlavalle maybe just missed it 14:30:28 But in any case, great job slaweq. for the most part, it is done 14:31:11 slaweq++ 14:32:07 this mail? http://lists.openstack.org/pipermail/openstack-dev/2018-April/129442.html 14:32:53 yamamoto: yeap, that's it 14:33:06 so we are done with this community goal 14:33:50 I think we need to wait for landing subproject patches before completing it. 14:34:05 * mlavalle slaps himself for doubting slaweq followed up 14:34:07 dynamic-routing patch lands. 14:34:19 that sounds fair 14:34:40 i think neutron-lbaas is better to be tracked. 14:34:50 good point amotoki 14:34:51 we can ping johnsom for neutron-lbaas :) 14:35:06 Hi 14:35:30 mmm... neutron-lbaas slaweq patch on mutable config has abandoned. 14:35:57 johnsom: we were talking about this http://lists.openstack.org/pipermail/openstack-dev/2018-April/129442.html 14:37:00 does neutron-lbaas need to followed up on this regard? 14:37:17 the current consensus seems neutron-lbaas is deprecated so no feature is coming. 14:37:33 Ah, yes. Since we have gone into feature freeze on neutron-lbaas this was kind of on the line. The main API will of course inherit support from neutron, this was just adding it to two sub-processes. 14:37:45 support mutable config only in octavia sounds reasonable to me. 14:38:13 s/support/supporting/ 14:38:15 Yes, Octavia certainly needs it. 14:38:55 I hadn't noticed it was abandoned, I wanted to get some other core opinions on the neutron-lbaas patch. I will bring it up at this week's meeting. 14:38:55 johnsom: ok, you decide what you want to do with neutron-lbaas. just a heads up 14:39:05 Yep, no problem 14:39:06 ++ 14:39:12 thanks for clarification! 14:39:44 looking at the projects listed in http://lists.openstack.org/pipermail/openstack-dev/2018-April/129442.html, we've done it :) 14:40:30 cool 14:40:46 is there anything worth mentioning regarding community goals? 14:40:52 we have done mox-removal too. 14:40:52 hi 14:40:55 we have 20 minutes left 14:41:00 i updated the storyboard status 14:41:08 https://storyboard.openstack.org/#!/story/2001546 14:41:31 it seems we can drop these two from the wiki 14:41:39 annp: go ahead 14:41:46 amotoki, thanks 14:41:49 In order to support deploying neutron-api under wsgi, We need to 2 patches: 14:41:49 https://review.openstack.org/#/c/555608/ 14:41:50 https://review.openstack.org/#/c/473718/ 14:42:03 The first patch: allow neutron-api load conf files from wsgi, and also allow neutron-rpc-server aware plugin extension. Currently, I have tested in my local environment, Everything seems work fines with provider network and tenant network, I can create vm, subnet, router, … So I think this patch is ready for review. Could you please have a look at it? 14:42:24 nova and other worked. I have to deal with time out problem of some tempest test http://logs.openstack.org/18/473718/11/check/tempest-full/0077b98/testr_results.html.gz, and also have to deal with how to start neutron-api, neutron-roc in neutron-grenade job instead of q-svc. So Could you please have a look at it and give me advice when you have time :). That’s all update for run neutron under wsgi 14:42:49 The second patch: WSGI integration in devstack, currently I switched from mod_wsgi to uwsgi as nova and other worked. I have to deal with time out problem of some tempest test http://logs.openstack.org/18/473718/11/check/tempest-full/0077b98/testr_results.html.gz, and also have to deal with how to start neutron-api, neutron-roc in neutron-grenade job instead of q-svc. So Could you please have a look at it and give me advice when you have 14:42:49 time :). That’s all update for run neutron under wsgi 14:42:57 amotoki: mlavalle I'll strike those two out on the wiki 14:43:07 jlibosva: +++ 14:43:24 annp: thanks for updates, I hope it'll get reviews soon :) 14:43:32 annp: thanks for the update. will take a look at the patches 14:43:32 annp: great progress. I will test them 14:43:57 let's move on, we're running out of time a bit 14:44:04 jlibosva, amotoki, mlavalle, thanks in advance. :) 14:44:09 #topic Bugs 14:44:46 yamamoto was deputy and he sent out the summary on the ML 14:44:55 hi 14:45:01 #link http://lists.openstack.org/pipermail/openstack-dev/2018-April/129777.html 14:45:19 the update is http://lists.openstack.org/pipermail/openstack-dev/2018-April/129781.html 14:45:41 thank you 14:45:48 one critical bug https://bugs.launchpad.net/neutron/+bug/1765008 14:45:49 Launchpad bug 1765008 in tripleo "Tempest API tests failing for stable/queens branch" [Critical,In progress] - Assigned to Gabriele Cerami (gcerami) 14:46:00 i think it still needs a little more work 14:47:02 what need to be done is to move the shim extension to the segment service plugin? 14:47:24 that's my understanding 14:47:32 yamamoto: i will submit another patch for that 14:47:42 thank you 14:47:45 i think so too 14:47:46 yamamoto: thanks for catching this issue 14:48:45 thanks yamamoto for update 14:49:04 deputy for this week should be pasuder 14:49:15 but he doesn't seem online now 14:49:20 * mlavalle will rollover the bugs deputy calendar in the wiki this week 14:49:47 jlibosva: he is aware of his duty week. he was asking questions yesterday in the Neutron channel 14:49:48 maybe slaweq will know how to contact him and make sure he's aware of being a bug deputy :) 14:49:57 mlavalle: ok, good then :) 14:50:22 moving on then 14:50:24 #topic Docs 14:50:40 boden: hi, do you have any updates re docs? 14:51:03 nothing doc related I’m aware of worth noting 14:51:08 thanks :) 14:51:13 #topic neutron-lib 14:51:18 boden: how about neutron-lib? :) 14:51:38 quickly; I noticed you mentioned the release of lib we want to do this week already 14:51:54 yeap 14:52:02 there’s still 1 patch we need to land from my POV… can be found here https://review.openstack.org/#/q/project:openstack/neutron-lib+comment:1.14.0-release-candidate 14:52:36 also let me note that the periodic dashboard that we use to see the health of neutron-lib/master with other projects was broken until yesterday; it’s now fixed 14:52:38 the docs links? 14:52:42 mlavalle yes 14:53:05 however we still have 1 periodic failure to address http://logs.openstack.org/periodic/git.openstack.org/openstack/networking-bgpvpn/master/openstack-tox-py35-with-neutron-lib-master/1eb92ef/job-output.txt.gz 14:53:14 I’m looking now, but may need to create a bug 14:53:51 boden: just pushed it in 14:53:52 so IMO we need (a) to land that doc fix patch and (b) figure out whats up with bgpvpn periodic before we can propose a safe release 14:53:54 jlibosva: mlavalle: hi 14:54:01 mlavalle thank you 14:54:06 slaweq: hi 14:54:07 and hi to everyone else :) 14:54:11 boden: it seems to be caused by horizon change. I will take care of it. 14:54:16 that’s all I have.. I nkow we are short on time 14:54:21 boden: thanks for updates 14:54:21 pasuder is for sure aware of being on bug debuty :) 14:54:22 amotoki awesome thank you 14:54:29 slaweq: oki :) thanks 14:54:36 #topic CLI/SDK 14:54:38 bgpvpn repo contains horizon dashboard too. 14:54:42 amotoki: do you have any updates re clisdk? 14:54:47 nothing from me on this topic 14:54:52 thanks 14:54:56 #topic Open Discussion 14:55:03 does anybody have a topic he'd like to discuss here? 14:55:06 we have 5 minutes left 14:55:59 seems like we do not have a topic 14:56:09 thanks everyone for showing up, keep up the good work :) 14:56:13 o/ 14:56:15 o/ 14:56:17 #endmeeting