14:01:29 <mlavalle> #startmeeting networking
14:01:29 <openstack> Meeting started Tue Oct 23 14:01:29 2018 UTC and is due to finish in 60 minutes.  The chair is mlavalle. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:01:30 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:01:33 <openstack> The meeting name has been set to 'networking'
14:01:39 <slaweq> hi
14:01:44 <amotoki> hi
14:01:49 <longkb> hi :)
14:01:54 <rubasov> o/
14:02:10 <tidwellr> hi
14:02:13 <hongbin> o/
14:02:21 <mlavalle> #topic Announcements
14:03:10 <mlavalle> This week we reached the Stein-1 milestone
14:04:13 <mlavalle> And we are a little more than two weeks away from the Berlin Summit
14:04:34 <mlavalle> Any other announcements to share with the team?
14:04:52 <njohnston> o/
14:05:12 <mlavalle> ok, let's move on
14:05:21 <mlavalle> #topic Blueprints
14:05:40 <lajoskatona_> Hi
14:05:56 <mlavalle> These are the blueprints we are targeting: https://launchpad.net/neutron/+milestone/stein-1
14:06:09 <mlavalle> Does anybode have an update or request?
14:06:37 <mlavalle> regarding blueprints
14:07:19 <mlavalle> amotoki: all good to cut the milestone?
14:07:35 <amotoki> mlavalle: yeah. I will prepare a release patch around Thu
14:07:53 <mlavalle> amotoki: are we also releasing the neutron stable branches?
14:08:17 <amotoki> mlavalle: we can, but it depends on pending patches.
14:08:38 <amotoki> i haven't checked the status. I need to sync with you.
14:08:57 <mlavalle> amotoki: ok
14:09:20 <mlavalle> Last week I was approached by someone asking a Queens release
14:09:29 <mlavalle> so let's do it
14:09:40 <amotoki> agree
14:09:52 <mlavalle> ok, moving on
14:10:04 <mlavalle> #topic Community goals
14:10:19 <mlavalle> amotoki: any updates with policy in code?
14:10:42 <amotoki> regarding policy-in-code, I just pushed a new patch set. sorry for late, but I believe neutron side will be in good shape.
14:11:04 <mlavalle> do you have the pointer handy?
14:11:26 <amotoki> https://review.openstack.org/585037
14:11:34 <mlavalle> Thanks amotoki :-)
14:11:53 <amotoki> I think I am in limited bandwidth, so once I prepared neutron-fwaas patch, I would like to gather volunteers for other stadium projects.
14:12:03 <amotoki> * to make the progress fast
14:12:26 <amotoki> neutron-fwaas patch would be a good example for other projects.
14:13:00 <mlavalle> do we need a volunteer for each Stadium project?
14:13:29 <amotoki> I don't think we need each per project
14:14:03 <mlavalle> ok, let us know when the fwaas patch is ready and we can use it as a model
14:14:10 <amotoki> sure
14:14:14 <mlavalle> and to request volunteers
14:14:21 <mlavalle> thanks for the update
14:14:37 <mlavalle> njohnston: anything on py3?
14:15:45 <njohnston> Nothing at present; there has been a thread on openstack-dev about how to handle py35 vs py36 vs py37, and so I have been waiting to make sure the aproach is not going to change.  I think a relative consensus has been reached.
14:16:08 <njohnston> So I am revisiting some of those changes this morning.
14:16:32 <mlavalle> Thanks for the update, njohnston
14:17:07 <amotoki> this thread is related to python3 future http://lists.openstack.org/pipermail/openstack-dev/2018-October/135892.html
14:17:25 <amotoki> this is just FYI
14:17:37 <njohnston> Thanks amotoki, I was just looking for the link
14:17:49 <mlavalle> slaweq: anything worth mentioning on Support Pre Upgrade Checks?
14:18:10 <slaweq> only that patch https://review.openstack.org/#/c/608444/ with base cli tool is ready for review
14:18:45 <slaweq> next step will be for me to add support for checks to be loaded using stevedore that e.g. stadium projects or some 3rd party plugins will be able to add own checks there
14:20:00 <mlavalle> ok, I will take a look at this patch today. Thanks
14:20:07 <slaweq> thx mlavalle
14:20:48 <mlavalle> #topic Bugs
14:21:03 <mlavalle> haleyb was our bugs deputy last week
14:21:16 <mlavalle> He sent this update to the ML: http://lists.openstack.org/pipermail/openstack-dev/2018-October/135969.html
14:23:53 <mlavalle> I thought we had gotten rid of this one a couple of weeks ago: https://bugs.launchpad.net/neutron/+bug/1798688
14:23:53 <openstack> Launchpad bug 1798688 in neutron "iptables_hybrid tests tempest.api.compute.servers.test_servers_negative.ServersNegativeTestJSON.test_shelve_shelved_server failed " [Undecided,Incomplete]
14:24:48 <mlavalle> I will take a look at it
14:24:52 <slaweq> mlavalle: few weeks ago it was visible mostly in dvr tests
14:24:55 <slaweq> IIRC
14:25:02 <mlavalle> yes
14:25:11 <slaweq> and then You couldn't reproduce it
14:25:22 <slaweq> but it looks that it still happen from time to time
14:26:31 <mlavalle> yeah, I will look again
14:27:04 <mlavalle> any other comments on the bugs report?
14:27:59 <mlavalle> ok, this week, our deputy is armax, so we are covered
14:28:24 <mlavalle> and next week the deputy is Zhao Bo. I will send him an email to make sure he is ready
14:28:46 <mlavalle> moving on
14:28:52 <mlavalle> #topic os-ken
14:29:12 <mlavalle> hongbin: any updates on this?
14:29:21 <hongbin> hi
14:29:35 <hongbin> so last week, there are a couple of progress on os-ken
14:29:55 <hongbin> 1. the pep8 job is setup: https://review.openstack.org/#/c/609121/
14:30:08 <hongbin> 2. the unit test is setup: https://review.openstack.org/#/c/609148/
14:30:33 <hongbin> 3. the lower constratnt is setup: https://review.openstack.org/#/c/609100/
14:30:43 <hongbin> 4. the doc building job is under review
14:30:53 <hongbin> #link https://review.openstack.org/#/q/project:openstack/os-ken
14:31:09 <hongbin> for the requirement side, we have a patch up for review
14:31:14 <amotoki> hongbin: I added a minor question on doc fix patch https://review.openstack.org/#/c/610706/4/doc/source/snort_integrate.rst@90
14:31:26 <hongbin> #link https://review.openstack.org/#/c/609018/
14:31:45 <hongbin> amotoki: thanks, i will get back to it
14:32:07 <amotoki> i am okay to merge this as is, but I would like you to check it before it :)
14:32:25 <hongbin> i am fine with it
14:33:11 <hongbin> so, right now, we are basically waiting for the requirement patch
14:33:47 <mlavalle> should we ping Mathew?
14:34:07 <hongbin> sure, we can ping him to look at it again
14:34:13 <mlavalle> ok
14:34:34 <mlavalle> anything else?
14:34:40 <hongbin> nothing else from my side
14:34:52 <mlavalle> Thanks!
14:35:02 <mlavalle> #topic CLI / SDK
14:35:18 <mlavalle> amotoki: any updates on this topic?
14:35:36 <amotoki> nothing from me this week.
14:35:43 <mlavalle> ok, moving on
14:35:50 <mlavalle> #topic neutron-lib
14:36:02 <mlavalle> boden: you are up
14:36:05 <boden> hi
14:36:34 <boden> much of the same as last week; working on the db consumption patches along with the switch to payload style args for callbacks
14:36:50 <boden> a few patches I would like to ask for reviews on that would help keep things moving
14:37:03 <boden> for the db decouple: https://review.openstack.org/#/c/612527/  should be ready
14:37:31 <boden> and for payloads: https://review.openstack.org/#/c/597561/  and https://review.openstack.org/#/c/596959/
14:37:39 <boden> if folks get time, it would help to keep these moving :)
14:37:51 <boden> that's all the exciting news I have for neutron-lib unless others have something
14:38:32 <mlavalle> added all of them to my pile
14:38:48 <slaweq> I wanted to ask about one thing
14:38:52 <mlavalle> I think we need to ask amotoki to take a look at https://review.openstack.org/#/c/596959/
14:38:58 <mlavalle> don't we?
14:39:14 <slaweq> do we backport patches to stable branches in neutron-lib? or it don't work like that there?
14:39:32 <amotoki> mlavalle: boden: sorry for that... we discussed it with boden and we agree that we can go as-is. will check it.
14:39:44 <mlavalle> amotoki: thanks ;-)
14:40:12 <boden> slaweq is there some bug we need fixed?
14:40:26 <slaweq> boden: I was thinking about backport of https://review.openstack.org/#/c/609633/
14:40:41 <slaweq> but I don't know if that makes sense so I'm asking here :)
14:41:12 <boden> slaweq honestly I'm not sure unless we were to re-release an old version of neutron-lib since everything is pulled from pypi??
14:42:00 <boden> may need ot ask the release team if we do need that backported... not sure we've done this to date that I'm aware of
14:42:20 <mlavalle> I don't think we have done it
14:42:37 <slaweq> that's why I'm asking, I saw stable/XXX branches in neutron-lib repo but I'm not sure if we are releasing such stable releases with bugfixes only
14:43:15 <amotoki> in theory, if we have bug fixes worth backported in neutorn-lib stable branches, we can backport and release it.
14:43:33 <amotoki> we didn't have such so far, but we can if needed.
14:43:49 <boden> I think we can, but woudl be a minor release (of whatever version we released for rocky say) right???
14:44:08 <amotoki> it would be a patch release
14:44:21 <amotoki> it means only Z can be incremented in X.Y.Z
14:44:28 <slaweq> ok, so that would be more question to stable core team then, if this patch is worth to be backported :)
14:44:33 <boden> yes, that's what I Was trying to say
14:45:02 <boden> slaweq do you need me to follow-up with them, or you will?
14:45:35 <slaweq> mlavalle: can You take a look at this patch and check if that is worth to be backported? :)
14:45:49 <mlavalle> slaweq: sure
14:45:56 <slaweq> thx
14:46:25 <mlavalle> anything else on neutron-lib
14:46:27 <mlavalle> ?
14:46:31 <boden> not from me
14:46:38 <mlavalle> ok, let's move on
14:46:44 <mlavalle> #topic On demand agenda
14:46:56 <mlavalle> anything else we should bring up to the team today?
14:47:30 <mlavalle> ok, thanks for attending
14:47:37 <mlavalle> Have a great week!
14:47:41 <mlavalle> #endmeeting