21:00:05 <slaweq> #startmeeting networking
21:00:06 <openstack> Meeting started Mon Sep 30 21:00:05 2019 UTC and is due to finish in 60 minutes.  The chair is slaweq. Information about MeetBot at http://wiki.debian.org/MeetBot.
21:00:07 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
21:00:09 <openstack> The meeting name has been set to 'networking'
21:00:15 <slaweq> welcome
21:00:18 <mlavalle> o/
21:00:22 <haleyb> hi
21:01:09 <slaweq> let's wait 1 or 2 more minutes for others
21:01:34 <njohnston_> o/
21:02:11 <slaweq> ok, lets start
21:02:13 <slaweq> #topic Announcements
21:02:29 <slaweq> First, Shanghai PTG
21:02:40 <slaweq> 2 things related to this:
21:03:09 <slaweq> planning etherpad https://etherpad.openstack.org/p/Shanghai-Neutron-Planning
21:03:23 <slaweq> please add Your ideas there if You didn't yet :)
21:03:36 <slaweq> and second
21:03:41 <slaweq> schedule: https://usercontent.irccloud-cdn.com/file/z9iLyv8e/pvg-ptg-sched-2
21:03:47 <slaweq> we have full 3 days for neutron
21:04:44 <slaweq> but I saw amotoki's email about it and as he has got horizon sessions on wednesday morning, maybe it would be enough for us to start neutron sessions on wednesday after lunch
21:04:51 <slaweq> that he will be able to join us
21:04:57 <slaweq> what do You think about it?
21:05:08 <slaweq> do You think we really need full 3 days?
21:05:27 <mlavalle> IMO that depends how many topics we have closer to the event itself
21:05:38 <mlavalle> we might need the 3 days
21:06:22 <slaweq> mlavalle: right, that's true
21:06:49 <slaweq> mlavalle: I also heard something (but I'm not sure if that is true) that we should/can do onboarding during ptg sessions
21:06:52 <slaweq> is that correct?
21:06:53 <mlavalle> if we have enough topics for 3 days, we could plan in such a way that the ones we discuss on Wednesday morning are the ones where amotoki doesn't need to be present
21:07:19 <slaweq> yes, I though that I will then try to do it like that
21:07:20 <mlavalle> slaweq: yes, I requested an on-boarding session for Neutron
21:07:40 <slaweq> mlavalle: but is this session during forum or during ptg? do You know?
21:07:55 <mlavalle> but it doesn't have to preclude us from having a full 3 days PTG
21:08:02 <mlavalle> I haven't seen the schedule
21:08:19 <slaweq> ok, we will see details when it will be closer to the event :)
21:08:37 <mlavalle> but again, if it overlaps with the PTG, we can plan in such a way that the people delivering the ob-boarding doesn't have to be in the room
21:08:43 <mlavalle> IMO
21:08:51 <slaweq> mlavalle: right :)
21:08:55 <mlavalle> it's a question of proper planning
21:09:15 <slaweq> ok, lets move on
21:09:26 <slaweq> next announcements are about Train release:
21:09:44 <slaweq> according to schedule: https://releases.openstack.org/train/schedule.html
21:09:52 <slaweq> last week we released RC1
21:10:02 <slaweq> for Neutron and for stadium projects
21:10:09 <slaweq> I think all releases are done
21:10:19 <slaweq> we have now stable/train branches created
21:10:56 <slaweq> next week is time for final RC if we will need it
21:11:08 <slaweq> and week of October 14th is Train release
21:11:48 <slaweq> that's all announcements from me
21:12:00 <slaweq> anyone else got any other announcement for the team?
21:13:14 <slaweq> ok, let's move on then
21:13:19 <slaweq> #topic Blueprints
21:13:44 <slaweq> BPs and bugs targeted for rc1 are here https://launchpad.net/neutron/+milestone/train-rc1
21:13:59 <slaweq> all patches for those are merged on time
21:14:06 <slaweq> congrats team!
21:14:36 <slaweq> do You have any potential bugs which should be target for rc2?
21:14:53 <slaweq> I don't know about any of such but maybe I missed something
21:16:52 <slaweq> ok, I take that as "no", which is good :)
21:17:26 <slaweq> if You would have any bug which potentially would require train rc2, please ping me on irc or email
21:18:06 <njohnston> will do
21:18:18 <slaweq> I think that about other blueprints we can talk on meetings in next weeks, when Train will be released finally
21:18:21 <mlavalle> will do
21:18:29 <slaweq> thx njohnston and mlavalle :)
21:19:23 <yamamoto> networking-midonet had a fix which might warrant an rc
21:19:57 <slaweq> yamamoto: do You have link to bug?
21:20:11 <yamamoto> https://review.opendev.org/#/c/685649/
21:21:35 <slaweq> thx yamamoto
21:21:50 <slaweq> it is already backported to stable/train
21:22:10 <mlavalle> yeah
21:22:43 <slaweq> I will talk with amotoki about when we can release rc2 for networking-midonet which will include this fix, fine for You?
21:22:56 <yamamoto> yes
21:23:21 <slaweq> yamamoto: ok, thx for letting us know about it
21:24:51 <slaweq> ok, let's move on
21:25:00 <slaweq> #topic Community goals
21:25:34 <slaweq> according to ipv6-only deployments testing, there is no any update
21:26:05 <slaweq> we still have some stadium projects which require some work, patches are available at https://review.opendev.org/#/q/topic:ipv6-only-deployment-and-testing+(status:open+OR+status:merged)+(project:%255Eopenstack/neutron.*+OR+project:%255Eopenstack/networking-.*)
21:26:36 <slaweq> according to pdf docs, I think we are almost done
21:26:48 <slaweq> on the list at https://review.opendev.org/#/q/topic:build-pdf-docs+(status:open+OR+status:merged)+(project:%255Eopenstack/neutron.*+OR+project:%255Eopenstack/networking-.*) we have only few patches not merged yet
21:26:56 <tidwellr> slaweq: I have some questions about the IPv6 patches
21:27:06 <slaweq> tidwellr: sure
21:27:14 <tidwellr> in particular neutron-dynamic-routing
21:28:35 <tidwellr> we already have what in my view amounts to pretty good coverage on all the IPv6 things, maybe other projects are in the same boat. Are we viewing this series of patches as required to claim we're in line with the community IPv6 goal?
21:29:49 <njohnston> tidwellr: Yes, because this is really testing the singlestack IPv6-only deployment model
21:30:01 <slaweq> tidwellr: the goal of this community goal is to provide jobs which are "ipv6-only", without any ipv4 communication
21:30:09 <slaweq> at least that's how I understand this
21:30:16 <njohnston> Whereas most of our IPv6 testing is done assuming a dual-stack IPv4 environment
21:30:37 <slaweq> but maybe we can modify this existing IPv6 job instead of adding new one, I'm not sure
21:30:48 <slaweq> I can talk with gmann about that tomorrow if You want
21:31:25 <njohnston> tidwellr: Is this the one you are most concerned with? https://review.opendev.org/#/c/682700/
21:31:54 <tidwellr> I'm sure this really isn't too much work, I was just wondering what we were trying to get out of these.
21:32:32 <slaweq> tidwellr: You have very good point, maybe there is no need to add one additional job to ci queues
21:32:34 <tidwellr> njohnston: well, that's the one I'm most familiar with. I was drawing on it as an example
21:33:37 <tidwellr> it may be appropriate for other projects, but the IPv6-isms in neutron-dynamic-routing are either already covered in the neutron tests or by the scenario tests
21:33:53 <slaweq> tidwellr: I will sync with gmann about it tomorrow morning and will later let You know about this
21:33:55 <slaweq> ok for You?
21:34:03 <tidwellr> sure
21:34:09 <slaweq> thx
21:34:12 <njohnston> tidwellr: I would say that we should end up with one job at the end - you're definitely farther ahead than most anyone else by having neutron-dynamic-routing-dsvm-tempest-scenario-ipv6 already
21:34:29 <slaweq> and thx for raising this here :)
21:35:01 <tidwellr> sorry to de-rail
21:35:20 <njohnston> For full python 3 compatibility - https://etherpad.openstack.org/p/neutron_stadium_python3_status - we have only remaining issues with networking-midonet, networking-odl, and networking-bagpipe.  yamamoto do you have any comments on getting all midonet CI jobs to python 3?
21:35:30 <mlavalle> tidwellr the de-reiler....LOL
21:36:29 <tidwellr> mlavalle: I have a feeling that's gonna stick now..... ;)
21:36:52 <mlavalle> with the bad spelling included
21:36:54 <yamamoto> njohnston: ones on the "Jobs still on python 2.7" list?
21:37:26 <njohnston> yamamoto: correct
21:38:22 <yamamoto> i think they are removed for other reasons
21:38:40 <njohnston> yamamoto: has there been any progress on midonet on bionic?
21:38:51 <yamamoto> no
21:39:14 <njohnston> yamamoto: OK, well hopefully things will get rolling soon :-)
21:39:57 <yamamoto> why should centos jobs stay python2.7?
21:41:12 <slaweq> yamamoto: I'm not sure but AFAIK You don't have python 3.6 on centos 7
21:41:19 <njohnston> yamamoto: While some versions of centos come with python3, not all of them do, so I thought those jobs would be fine to stay on python 2.7 and then when centos8 jobs are defined they would be python 3 from the start
21:42:00 <njohnston> yamamoto: If you think those are ripe for conversion though, I defer to you as a midonet expert. :-)
21:42:41 <yamamoto> ok thank you
21:43:14 <njohnston> Regarding midonet, I did some looking in to the job failures on https://review.opendev.org/#/c/685702/ - it's just a couple of tests on the affected jobs, but I have not come to a conclusion as to why they are unhappy yet
21:43:18 <slaweq> yamamoto: and if some of those jobs are not existing anymore, please update etherpad accordingly
21:43:24 <njohnston> oops I meant to say regarding bagpipe
21:43:52 <yamamoto> slaweq: i will
21:43:59 <slaweq> yamamoto: thx a lot
21:44:12 <slaweq> njohnston: yeah, I will try to take a look at those errors this week
21:44:24 <njohnston> thank you slaweq
21:44:29 <slaweq> it shouldn't be (I hope so) hard issue to fix
21:45:27 <slaweq> ok, I think we already covered all community goals for today
21:45:31 <slaweq> so let's move on
21:45:34 <slaweq> #topic Bugs
21:45:53 <slaweq> our bug deputy last week was rubasov
21:45:59 <slaweq> he sent report at http://lists.openstack.org/pipermail/openstack-discuss/2019-September/009803.html
21:46:25 <slaweq> I would like to ask L3 subteam to take a look at https://bugs.launchpad.net/neutron/+bug/1845360
21:46:25 <openstack> Launchpad bug 1845360 in neutron "ARP advertisement issue with DVR" [Undecided,New]
21:46:32 <slaweq> as it is not triaged yet
21:47:07 <slaweq> there is also one issue with fwaas which affects our gate: https://bugs.launchpad.net/neutron/+bug/1845300
21:47:08 <openstack> Launchpad bug 1845300 in neutron "FWaaS tempest tests are failing" [High,Confirmed]
21:47:43 <slaweq> and one other not assigned "gate issue" https://bugs.launchpad.net/neutron/+bug/1845176
21:47:43 <openstack> Launchpad bug 1845176 in neutron "Removing of QoS queue in neutron-ovs-agent fails due to existing references" [Medium,Confirmed]
21:47:56 <slaweq> so if someone would have cycles to take a look, that would be great :)
21:48:21 <slaweq> that's all what I wanted to highlight from rubasov's report
21:48:40 <slaweq> I updated our bug deputy schedule also
21:48:46 <slaweq> so we all have new round now
21:48:57 <slaweq> this week bug deputy is bcafarel
21:49:05 <slaweq> I will remind it to him tomorrow morning
21:49:25 <slaweq> please also check this new schedule, available at https://wiki.openstack.org/wiki/Network/Meetings
21:49:59 <slaweq> and please let me know if You can't do bug deputy in term assigned to You, I will try to adjust it somehow
21:51:08 <slaweq> any other bugs You want to talk about today?
21:52:31 <slaweq> ok, if not than let's move on
21:52:38 <slaweq> #topic docs
21:52:48 <slaweq> I have one small thing to mention about docs
21:52:58 <slaweq> As boden is mostly stepping down now, we will need someone new as docs CrossProjectLiaison: https://wiki.openstack.org/wiki/CrossProjectLiaisons#Documentation
21:53:10 <slaweq> maybe someone wants to volunteer for this position?
21:53:37 <slaweq> as boden told me, he didn't have any additional work related to this but it would be good to have someone listed there, just in case
21:55:07 <slaweq> ok, if someone would like to volunteer for this, please let me know by mail or on irc :)
21:55:08 <njohnston> that person would probably want to plan on attending the docs SIG meetings
21:55:28 <slaweq> njohnston: are there such meetings weekly?
21:55:35 <slaweq> I didn't know about it
21:56:13 <njohnston> http://eavesdrop.openstack.org/#Documentation_Team_Meeting
21:56:19 <mlavalle> amotoki has been doing docs stuff. I would ask him first
21:56:46 <slaweq> mlavalle: yes, I was also thinking about him
21:56:51 <mlavalle> he did the docs in pdf community goal
21:57:03 <slaweq> thx for suggestion, I will ask him tomorrow
21:58:08 <slaweq> ok, let's move on
21:58:17 <slaweq> #topic On Demand agenda
21:58:29 <slaweq> anyone have anything else to talk about today?
21:58:41 <slaweq> if not, we can finish meeting
21:59:31 <slaweq> ok, so thx for attending
21:59:33 <njohnston> o/
21:59:35 <slaweq> and have a great week
21:59:37 <mlavalle> o/
21:59:37 <slaweq> o/
21:59:42 <slaweq> #endmeeting