14:00:16 <mlavalle> #startmeeting networking
14:00:17 <openstack> Meeting started Tue Feb 26 14:00:16 2019 UTC and is due to finish in 60 minutes.  The chair is mlavalle. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:00:18 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:00:20 <openstack> The meeting name has been set to 'networking'
14:00:32 <haleyb> hi
14:00:38 <lajoskatona> o/
14:00:41 <njohnston> o/
14:01:02 <mlavalle> How are y'all?
14:01:22 <amotoki> o/
14:01:24 <slaweq> hi
14:01:26 <tidwellr> o/
14:02:24 <njohnston> mlavalle: Splendid, and you?
14:02:34 <mlavalle> Great
14:02:42 <mlavalle> let's get going
14:03:22 <mlavalle> #topic Announcements
14:03:46 <mlavalle> We almost made it to the end of the Stein cycle
14:03:56 <mlavalle> Our Stein-3 milestones is next week
14:05:04 <mlavalle> Also, for those of you planning to attend the Summit in Denver, please remember that this week is the end of the "earlybird" registration period
14:05:24 <mlavalle> That includes your contributos discount codes
14:05:41 <mlavalle> don't let the price hike catch you by surprise
14:05:59 * mlavalle registered last week and made hotel / air reservations
14:06:07 <amotoki> precisely speaking, the deadline is February 27, 2019 at 11:59pm PST
14:06:33 <mlavalle> so that's tomorrow
14:06:51 * slaweq registered to PTG only already
14:07:16 <mlavalle> Finally, please remember that there is a TC election going on
14:07:31 <mlavalle> follow the questions and be ready to cast your votes
14:08:13 <mlavalle> any other annoucements?
14:08:21 <davidsha> o/
14:08:43 <amotoki> although the next week is stein-3, we cut stein beta for neutron stadium.
14:08:54 <amotoki> https://review.openstack.org/#/c/636869/
14:09:15 <amotoki> I originally thought we can discuss it here, but it has been merged a bit ago
14:09:52 <amotoki> we can align our deliverables in Stein together :)
14:09:56 <mlavalle> LOL
14:10:38 <mlavalle> so what follows amotoki in terms of deliverables?
14:11:03 <mlavalle> the final deliverables after feature freeze?
14:11:14 <mlavalle> amotoki: ^^^^
14:11:19 <amotoki> i think we will also cut Stein-3 next week
14:11:42 <amotoki> the above patch does not include networking-ovn/odl/bgpvpn/bagpipe
14:11:57 <mlavalle> ok, cool
14:11:58 <amotoki> I believe we will have stein-3 for all of stadium projects next week
14:12:22 <mlavalle> let's move on
14:12:41 <mlavalle> #topic Blueprints
14:13:25 <mlavalle> These are the blueprints that we are tracking https://launchpad.net/neutron/+milestone/stein-3
14:14:11 <tidwellr> mlavalle: subnet onboard is ready to go, thanks goes to Mike Bayer for helping get https://review.openstack.org/#/c/348080/ over the hump with the DB enginefacade issues
14:14:24 <mlavalle> As suggested last week by slaweq< i raised the priority of blueprints that require attention
14:14:57 <njohnston> For bulk ports, I think https://review.openstack.org/#/c/624815/ is very very close.  But slaweq noticed that the OVN test job had a few failures, so I am investigating that.
14:15:51 <mlavalle> tidwellr: you had a faulure in a tox job
14:16:18 <tidwellr> the lower-contstraints job, which I thought was a widespread thing....
14:16:33 <tidwellr> I'll rebase and see where it's at
14:16:41 <mlavalle> perfect
14:16:59 <mlavalle> added it to the reviews I have to do over the next couple of days
14:17:26 <mlavalle> njohnston: I'll also keep an eye on yours
14:17:35 <njohnston> mlavalle: thanks!
14:17:40 <mlavalle> Thanks tidwellr and njohnston for your hard work
14:18:15 <mlavalle> lajoskatona: anything to say on https://blueprints.launchpad.net/neutron/+spec/strict-minimum-bandwidth-support?
14:18:28 <lajoskatona> mlavalle:yes
14:19:02 <lajoskatona> we have still a few patches for review, I think the most critical is the batch of rubasov's: https://review.openstack.org/#/q/topic:minimum-bandwidth-allocation-placement-api+(status:open+OR+status:merged)+status:open++owner:%22Bence+Romsics+%253Cbence.romsics%2540ericsson.com%253E%22
14:19:37 <lajoskatona> mlavalle: and I have a batch in various projects (tempest, novaclient....): https://review.openstack.org/#/q/topic:minimum-bandwidth-allocation-placement-api+(status:open+OR+status:merged)+status:open++owner:%22Lajos+Katona+%253Clajos.katona%2540ericsson.com%253E%22
14:20:10 <mlavalle> lajoskatona: do we only need review attention? or is there anything else missing?
14:20:14 <lajoskatona> Those are not mandatory for the feature (perhaps the one in novaclient is the exception)
14:20:44 <lajoskatona> mlavalle: yeap that would be good to push the few remaining patch to go in
14:21:17 <amotoki> lajoskatona: how is novaclient related to this blueprint? do we have some change in nova side?
14:21:50 <lajoskatona> amotoki: in nova there will be a new compute microversion (2.70 as of now) and to boot VM we have to enable that in novaclient
14:22:03 <mlavalle> yeap
14:22:19 <mlavalle> that's what super gibi has been working on
14:22:26 <lajoskatona> amotoki: without that you cannot boot from CLI, of course that is nova area, but anyway
14:22:35 <lajoskatona> mlavalle: exactly
14:22:41 <amotoki> lajoskatona: thanks for clarification!
14:22:58 <lajoskatona> amotoki: your welcome
14:23:23 <mlavalle> In regards to https://blueprints.launchpad.net/neutron/+spec/network-segment-range-management
14:24:07 <mlavalle> I spent time revieiwing the patches:
14:24:09 <mlavalle> https://review.openstack.org/#/c/624708
14:24:23 <mlavalle> https://review.openstack.org/#/c/624709
14:24:52 <mlavalle> https://review.openstack.org/#/c/638386
14:25:11 <mlavalle> thanks slaweq and liuyulong for merging the last one
14:25:31 <mlavalle> liuyulong and I made comments on the first two
14:25:33 <slaweq> this was the easy one :)
14:26:04 <mlavalle> IMO, after addressing those comments, they will be ready
14:26:12 <mlavalle> liuyulong: what do you think?
14:26:52 <liuyulong> There are very positive feedback from Kailun Qin, I think it is very close.
14:27:06 <mlavalle> slaweq: yeah, the first one is massive. I spent a whole Saturday afternoon looking at it
14:28:04 <mlavalle> ok, let's go over them again and approve if they are ready
14:28:07 <slaweq> I will also go to them this week
14:28:38 <mlavalle> thanks slaweq, liuyulong!
14:29:53 <mlavalle> I think we are in good shape in the blueprints we are targeting for Stein-3
14:30:39 <mlavalle> davidsha: have you heard of our compadres xubozhang and igor in regards to https://blueprints.launchpad.net/neutron/+spec/openflow-based-dvr?
14:31:24 <davidsha> They're still working on them, but no update besides that I'm afraid, last time I was talking to them was last Monday.
14:32:07 <mlavalle> davidsha: can I ask you a favor? Please make sure they realize we have moved the L3 meeting to Wednesday 1400 utc
14:32:32 <davidsha> I've let Xubo know already, I'll email Igor now.
14:32:42 <mlavalle> davidsha: thanks!
14:32:52 <mlavalle> anything else on blueprints?
14:32:52 <davidsha> Np!
14:34:02 <mlavalle> #topic Community goals
14:34:27 <mlavalle> Do we have anything to say about python3?
14:35:01 <slaweq> not too much
14:35:33 <slaweq> regarding neutron, last job to switch is neutron-tempest-dvr-ha-multinode job
14:35:35 <njohnston> I pushed a change to use python 3 for a few jobs for ovsdbapp
14:35:36 <slaweq> patch is here https://review.openstack.org/#/c/638626/
14:36:29 <njohnston> I will be taking a sweep of stadium projects to look at the state of things.  Obviously the autogenerated mass-push changes took care of unit tests but checking for functiona, fullstack, etc.
14:36:29 <mlavalle> is it good to go?
14:36:56 <slaweq> mlavalle: which one? thix https://review.openstack.org/#/c/638626/ ?
14:37:18 <mlavalle> yes, asking about that one
14:37:55 <slaweq> yes, it's good to go
14:37:59 <mlavalle> cool
14:38:05 <mlavalle> thanks njohnston!
14:38:07 <slaweq> still as legacy job but with py3
14:38:13 <mlavalle> ok, let's move on
14:38:20 <mlavalle> #topic Bugs
14:38:53 <mlavalle> Last week, the deputy was zhaobo. I pinged him in WeChat and he responded that he was working on it
14:39:03 <mlavalle> did anybody see a report from him?
14:39:44 <slaweq> I didn't
14:39:57 <mlavalle> I don't find anything in the discuss list
14:40:07 <mlavalle> nor my inboxes
14:41:04 <amotoki> me either
14:41:24 * mlavalle looking at https://bugs.launchpad.net/neutron/+bugs?orderby=-datecreated&start=0
14:42:53 <mlavalle> It seems that over the past week, evrything High is in progress
14:43:37 <mlavalle> 3 fwaas / octavia bugs that need triaging
14:44:03 <amotoki> I will take care of them. ocatavia bugs need to be forwarded to storyboard
14:44:21 <boden> i also have one bug that may be worth noting if we have time
14:44:30 <mlavalle> I will triage https://bugs.launchpad.net/neutron/+bug/1817219
14:44:30 <openstack> Launchpad bug 1817219 in neutron "Failed to list security group tags" [Undecided,New]
14:44:39 <mlavalle> boden: please go ahead
14:44:45 <boden> https://bugs.launchpad.net/tricircle/+bug/1816644
14:44:45 <openstack> Launchpad bug 1816644 in Tricircle "tempest-dsvm jobs don't pull required projects from source" [Undecided,New]
14:45:21 <boden> so it seems a handful or consumers that use "required projects" (aka "siblings") with legacy devstack based jobs are broken
14:45:41 <boden> long story short, I have a solution, but IMO it's not a good one... trying to get QA to engauge, but has been slow
14:46:06 <boden> those impacted projects have broken jobs (IIUC) until we resolve this
14:46:30 <mlavalle> boden: is there anything I / we can help with?
14:46:53 <boden> mlavalle well if we could get someone from QA to look at https://bugs.launchpad.net/tempest/+bug/1817555 it might help
14:46:54 <openstack> Launchpad bug 1817555 in tempest "No way to pull requirements from source in devstack jobs" [Undecided,New]
14:47:12 <mlavalle> boden: ok, I'll ping them today
14:47:19 <boden> mlavalle thanks
14:47:22 <amotoki> boden: you can ask gmann
14:47:29 <boden> amotoki I have
14:47:33 <boden> no response yet
14:48:05 <amotoki> he recently moved to Canada last week, so he might be busy somehow..
14:48:12 <gmann> boden: i will check, it is legacy job issue ?
14:48:20 <boden> gmann yes
14:48:38 <boden> gmann I sent you an email not too long ago :)
14:48:46 <gmann> amotoki: morning time here so I am ok :)
14:48:57 <mlavalle> gmann: https://bugs.launchpad.net/tempest/+bug/1817555
14:48:58 <openstack> Launchpad bug 1817555 in tempest "No way to pull requirements from source in devstack jobs" [Undecided,New]
14:49:03 <amotoki> regarding this, I cut networking-sfc stein b1, so we can change requirements
14:49:05 <amotoki> it might help us
14:49:09 <gmann> boden: mlavalle  sure, I will check and get back.
14:49:25 <mlavalle> gmann: thanks!
14:49:42 <mlavalle> ok, our deputy this week is manjeets
14:50:01 <mlavalle> he sent me an ack in the Neutron channel, so he is aware
14:50:16 <mlavalle> ok,
14:50:20 <mlavalle> let's move on
14:50:26 <mlavalle> #topic neutron-lib
14:50:37 <mlavalle> boden: we already covered on of your topics
14:50:45 <mlavalle> please go ahead with the second one
14:51:00 <boden> we need to release neutron-lib for stein
14:51:02 <boden> like today :)
14:51:06 <slaweq> +1 :)
14:51:13 <amotoki> I just proposed a patch neutron-lib 1.25.0 https://review.openstack.org/#/c/639255/
14:51:26 <boden> are there other patches we need?
14:51:32 <boden> I was hoping for https://review.openstack.org/#/c/639117/, but no biggie
14:51:44 <boden> I also say https://review.openstack.org/#/c/635907/
14:51:47 <boden> saw
14:51:52 <mlavalle> well, I might try to get one in myself
14:52:05 <slaweq> what about this one https://review.openstack.org/#/c/636990/ ?
14:52:10 <slaweq> should we get it in also?
14:52:24 <slaweq> it's related to segments range management
14:52:30 <boden> slaweq it depends on neutron patch
14:52:33 <boden> could take awhile like that
14:52:50 <mlavalle> yeah
14:53:06 <slaweq> but now I'm not sure if that depends on is correct
14:53:07 <mlavalle> boden: what is the absolute drop-dead deadline to release?
14:53:19 <mlavalle> Thursday, like you suggested in your email?
14:53:23 <boden> mlavalle I thought tomorrow, but I'm not sure if that's drop-dead
14:53:39 <mlavalle> amotoki: what do you think?
14:53:48 <amotoki> IIUC Thursday is the final deadline
14:54:11 <mlavalle> ok, let's the 3 of us touch base at the end of day tomorrow and see where we stand
14:54:17 <mlavalle> I'll ping you
14:54:28 <mlavalle> is that ok?
14:54:28 <boden> mlavalle ok.. let's try not to push the timeline too much :)
14:54:39 <amotoki> let's update https://review.openstack.org/#/c/639255/ if we have more commits to be included.
14:54:50 <boden> amotoki ack
14:54:53 <mlavalle> amotoki: ack. Thanks!
14:55:06 <boden> sorry, but I have to run guys...
14:55:37 <mlavalle> #topic On demand agenda
14:55:48 <mlavalle> amotoki: we covered what you wanted to discuss, right?
14:55:55 <amotoki> mlavalle: yes
14:56:16 <njohnston> We should probably bring up gmann's mail about the legacy zuul job bionic transition: http://lists.openstack.org/pipermail/openstack-discuss/2019-February/003129.html
14:57:02 <njohnston> Neutron and neutron-lib are in a good state I thing; the issue here is the stadium
14:57:07 <njohnston> *think
14:57:32 <lajoskatona> mlavalle: you mentioned few weeks ago a pad for possible update checks, I am not sure if I missed it, and cant find it in my mailbox
14:57:32 <gmann> njohnston: thanks, it will be good if someone from neutron team can start testing patches and add those in this etherpad - https://etherpad.openstack.org/p/legacy-job-bionic
14:58:14 <slaweq> I can work on it
14:58:14 <mlavalle> njohnston: do we need a volunteer?
14:58:25 <mlavalle> slaweq: Thanks!
14:58:43 <mlavalle> lajoskatona: I'll ping you later in channel
14:58:53 <lajoskatona> mlavalle: thanks
14:59:06 <mlavalle> ok, thanks for attending
14:59:14 <mlavalle> have a great week!
14:59:14 <lajoskatona> bye
14:59:18 <njohnston> o/
14:59:20 <mlavalle> #endmeeting