21:00:09 <mlavalle> #startmeeting networking
21:00:10 <openstack> Meeting started Mon Apr 30 21:00:09 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:11 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
21:00:13 <openstack> The meeting name has been set to 'networking'
21:00:20 <mlavalle> Hi there!
21:00:25 <janzian> o/
21:00:27 <boden> howdy
21:00:41 <haleyb> hi
21:00:59 <mlavalle> Agenda for today is here:
21:01:06 <mlavalle> #link https://wiki.openstack.org/wiki/Network/Meetings
21:01:07 <pasuder> Hello!
21:01:15 <slaweq> hi
21:01:24 <mlavalle> #topic Announcements
21:02:04 <mlavalle> Our next milestone is Rocky-2, June 4 - 8
21:02:18 <mlavalle> as usual, it will sneak on us before we know it
21:02:28 <pasuder> :D
21:02:34 <hongbin> o/
21:02:42 <mlavalle> The entire Rocky release calendar is here:
21:02:51 <mlavalle> #link https://releases.openstack.org/rocky/schedule.html
21:03:18 <manjeets> hi
21:03:28 <mlavalle> Last week we release neutron-lib 1.14.0:
21:03:33 <njohnston> o/
21:03:42 <mlavalle> #link https://review.openstack.org/#/c/564571
21:03:56 <mlavalle> Thnaks to boden for that :-)
21:04:55 <mlavalle> We are still looking for a volunteer to be our liaison with the QA team
21:05:37 <slaweq> mlavalle: what should such liaison do exactly? Do You have any link to docs or something like that?
21:06:00 <manjeets> mlavalle, the duty explanation would help
21:07:10 <mlavalle> slaweq: mhhh. I don't think we have a doc. The idea is to be aware of what the QA team is doing and communicate those things that might impact the Neutron team
21:08:19 <slaweq> mlavalle: ok
21:08:36 <manjeets> oh working with openstack-qa and infra ?
21:08:39 <mlavalle> actually there is an explanation of the duties here: https://wiki.openstack.org/wiki/CrossProjectLiaisons#QA
21:08:52 <mlavalle> slaweq, manjeets: ^^^^
21:09:43 <mlavalle> Moving on
21:09:58 <slaweq> mlavalle: thx for the link
21:10:01 <slaweq> I will check it
21:10:09 <mlavalle> The Vancouver Summit is a little less than 3 weeks away
21:10:43 <mlavalle> I remind folks that we have 4 Neutron related Forum sessions approved. They are listed in the Agenda wiki
21:11:38 <mlavalle> I also remind folks that we are collecting the names of the Neutron team members attending the Summit in this etherpad:
21:11:46 <mlavalle> #link https://etherpad.openstack.org/p/YVR-neutron-atendees
21:12:00 <mlavalle> We will have a team dinner on Tuesday
21:12:25 <mlavalle> And those are all the announcements that I have
21:12:36 <mlavalle> any other announcements from the team?
21:13:12 <mlavalle> ok, let's move on
21:13:23 <mlavalle> #topic Blueprints
21:14:18 <mlavalle> This is our dashboard of the blueprints / bugs we are targeting for Rocky-2:
21:14:26 <mlavalle> #link https://launchpad.net/neutron/+milestone/rocky-2
21:15:03 <mlavalle> Does anyone want to bring up a blueprint for update?
21:16:15 <mlavalle> I do want to give visibility today to one of our blueprints:
21:16:22 <mlavalle> https://blueprints.launchpad.net/neutron/+spec/strict-minimum-bandwidth-support
21:17:23 <mlavalle> We made very good progress last week with the Neutron and Nova specs. The Neutron spec is here:
21:17:35 <mlavalle> #link https://review.openstack.org/#/c/508149/
21:17:58 <mlavalle> I wen't through it late last week and plan to go over it again today or tomorrow
21:18:27 <mlavalle> IMO there is still one sticking point there, but besides that, it is close to merge
21:18:44 <mlavalle> The Nova side spec already got a +2 late last week:
21:19:00 <mlavalle> #link https://review.openstack.org/#/c/502306/
21:19:18 <mlavalle> I am reviewing it today
21:19:33 <mlavalle> I encourage folks to review the Neutron spec and help refining it
21:20:35 <mlavalle> I remind the team that you can find the OVO adoption backlog here:
21:20:44 <mlavalle> #link https://docs.google.com/spreadsheets/d/1Mz7V40GSdcUH_aBoNWjsFaNRp4wf-duz1GFWligiNXc/edit#gid=1051788848
21:21:15 <mlavalle> If you have bandwidth available, please check it out and pick a task to implement
21:21:38 <mlavalle> Any thing else on blueprints today?
21:22:15 <mlavalle> OK, moving on
21:22:27 <mlavalle> #topic Community goals
21:24:24 <mlavalle> Regarding wsgi support, we have a patch close to merge:
21:24:45 <mlavalle> #link https://review.openstack.org/#/c/555608/
21:24:51 <mlavalle> please take a look
21:25:03 <mlavalle> and help us close that community goal
21:25:52 <mlavalle> as you can see, we closed already two this cycle: enable mutable configuration and mox3 removal
21:27:24 <mlavalle> In regards to the python 3.5 support, I want to highlight a ML thread that outlines the coummnity big picture plan as far as moving completely to Python 3 and dropping completaly Python 2.7
21:27:44 <mlavalle> #link  http://lists.openstack.org/pipermail/openstack-dev/2018-April/129866.html
21:28:03 <mlavalle> I thinbk it is healthy that the team is aware of the big picture in this regard
21:28:45 <mlavalle> Anything else on community goals today?
21:29:09 <pasuder> No :)
21:29:23 <mlavalle> ok, moving on
21:29:28 <mlavalle> #topic Bugs
21:29:34 <pasuder> mlavalle it seems that you are the only one voice in this room for last few minutes
21:29:41 <pasuder> but finally bugs :D
21:30:07 <mlavalle> The deputy report from pasuder is here: http://lists.openstack.org/pipermail/openstack-dev/2018-April/129988.html
21:30:16 <pasuder> I was the bug deputy for last week and here is the summary: http://lists.openstack.org/pipermail/openstack-dev/2018-April/129988.html and apendix: http://lists.openstack.org/pipermail/openstack-dev/2018-April/130042.html
21:30:26 <pasuder> oh, too slow I am :)
21:30:40 <mlavalle> well, I wasn't aware of the apendix :-)
21:31:00 <pasuder> :) it was added minutes ago
21:31:15 <mlavalle> I was aware of the bug, though
21:31:18 <pasuder> I would like to highlight one bug
21:31:31 <pasuder> https://bugs.launchpad.net/neutron/+bug/1766812
21:31:32 <openstack> Launchpad bug 1766812 in neutron "the machine running dhcp agent will have very high cpu load when start dhcp agent after the agent down more than 150 seconds" [Undecided,New]
21:31:47 <pasuder> Should be reproduced somehow?
21:32:07 <pasuder> And regarding https://bugs.launchpad.net/neutron/+bug/1767028 I have a question: how to link with other project?
21:32:08 <openstack> Launchpad bug 1767028 in neutron "loadbalancer can't create with chinese character name" [Undecided,New] - Assigned to xuchaochao (xuchaochao)
21:32:09 <mlavalle> we can give it a try
21:32:24 <mlavalle> as far as trying to reproduce it
21:32:34 <pasuder> uhm
21:32:36 <mlavalle> I saw that the submitter was using devstack
21:32:51 <pasuder> Not sure..
21:33:11 <mlavalle> I have a multinode configuration with Vagrant: https://github.com/miguellavalle/dvrvagrant
21:33:20 <mlavalle> it has two network nodes
21:33:25 <pasuder> "all-in-one environment" - not sure if this was devstack
21:33:48 <pasuder> Aha, nice mlavalle
21:34:05 <mlavalle> there is a network node
21:34:19 <mlavalle> and there is an allinone node, that is also a network node
21:34:56 <mlavalle> so I thonk with some additional bash scripts we could replicate the situation
21:35:15 <pasuder> ok, understand
21:35:27 <mlavalle> pasuder: if you want to play with it, just don't pay attention to the readme
21:35:40 <mlavalle> it apllies to another configuration. I haven't updated it
21:35:51 <pasuder> OK, I will see, if I will be able
21:36:02 <mlavalle> pasuder: if you get stuck, ping me
21:36:11 <pasuder> OK, thx mlavalle
21:36:29 <pasuder> From my site, that
21:36:32 <pasuder> 's all
21:37:04 <mlavalle> haleyb: https://bugs.launchpad.net/neutron/+bug/1766812 reminded me of the situation we had with the OVS agent and concurrency
21:37:05 <openstack> Launchpad bug 1766812 in neutron "the machine running dhcp agent will have very high cpu load when start dhcp agent after the agent down more than 150 seconds" [Undecided,New]
21:37:59 <haleyb> mlavalle: yes, i thought of the same thing, but it was mitaka.  i have a question i'm posting in it now actually
21:38:16 <haleyb> oh, actually, sorry, was looking at another, but yes, it is suspicious
21:39:08 * pasuder will slowly go sleep :)
21:39:14 <mlavalle> thanks, haleyb
21:39:57 <mlavalle> pasuder: thanks for the update and your very thorough work / email
21:40:50 <mlavalle> This week the deputy is hongbin
21:41:50 <hongbin> yes
21:41:54 <mlavalle> I also want to remind the team that I roll-over the calendar in https://wiki.openstack.org/wiki/Network/Meetings#Bug_deputy
21:42:08 <mlavalle> rolled-over^^^
21:42:22 <mlavalle> so please take note of your next bugs deputy date
21:43:29 <mlavalle> #topic Neutron Docs
21:43:48 <mlavalle> boden indicated that there are no updates here, so we are moving on
21:43:58 <mlavalle> #topic neutron-lib
21:44:30 <pasuder> bye! ;)
21:44:54 <mlavalle> We arlready mentioned the release of neutron-lib 1.14.0
21:45:26 <mlavalle> and boden want to remind people to keep reviewing neutron-lib patches
21:46:38 <mlavalle> #topic CLI / SDK
21:47:05 <mlavalle> amotoki along with the rest of Japan is enjoying a week long holiday
21:47:17 <mlavalle> so I don't think he is around
21:47:32 <mlavalle> does anybody have anything to comment about this topic?
21:48:10 <mlavalle> ok, let's move on
21:48:27 <mlavalle> #topic On demand agenda
21:49:01 <mlavalle> Last week, haleyb made an good suggestion about the release of stable branches
21:49:12 <mlavalle> do you want to comment about it, haleyb?
21:49:48 <haleyb> well, someone had noticed a bug in 12.0.1 so my question was around how often we release
21:50:11 <haleyb> i think the answe we came up with was we should release stable branches at our upstream milestones
21:50:39 <mlavalle> yeah, I think that is a good approach
21:50:47 <haleyb> we can always release more often of course, but at least then we'll always be moving forward
21:50:57 <mlavalle> exactky
21:50:59 <slaweq> haleyb++
21:51:14 <haleyb> i proposed https://review.openstack.org/#/c/564748/ for 12.0.2 (stable/queens)
21:51:35 <haleyb> i guess i should also propose for stable/pike, etc
21:51:47 <mlavalle> that's a good point
21:52:33 <mlavalle> so let's adopt the convention that we release to stable branches the week after each milestone
21:52:53 <haleyb> mlavalle: i did have a question - sean asked about stable team review, who is that besides us?  meaning: you, ihar and i are on the team i believe
21:53:25 <mlavalle> there is an OpenStack overall stable team
21:53:25 <haleyb> mlavalle: and ack on that ^^^, wonder if there is a place in our docs to put that
21:53:48 <mlavalle> I think he is refering to that
21:54:01 <mlavalle> let me clarify with him
21:54:10 <mlavalle> and yes, we can update our docs
21:54:16 <haleyb> mlavalle: but i don't think there is differentiation between the stable neutron team and the stable team, unless i'm mis-remembering
21:54:30 <mlavalle> that might be the case
21:54:33 * haleyb looks at his groups
21:54:42 <mlavalle> that's is why I want to clarify
21:55:18 <haleyb> mlavalle: so i'm probably wrong, my extra group is neutron-stable-maint
21:55:30 <mlavalle> we'll find out
21:55:43 * mlavalle doubts haleyb is wrong
21:56:09 <mlavalle> anything else we need to discuss today?
21:56:45 <mlavalle> ok, thanks for attending
21:56:50 <mlavalle> #endmeeting