14:00:19 <slaweq> #startmeeting networking
14:00:20 <openstack> Meeting started Tue Jul 28 14:00:19 2020 UTC and is due to finish in 60 minutes.  The chair is slaweq. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:00:21 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:00:23 <openstack> The meeting name has been set to 'networking'
14:01:07 <ralonsoh> hi
14:01:16 <ralonsoh> (I need to update the channel in my calendar)
14:01:19 <slaweq> hi
14:01:19 <bcafarel> oh, right, new bat-channel
14:01:21 <lajoskatona> Hi
14:01:31 <amotoki> hi
14:01:49 <slaweq> :)
14:02:10 <njohnston> o/
14:02:46 <slaweq> agenda for the meeting is at
14:02:47 <slaweq> #link https://wiki.openstack.org/wiki/Network/Meetings
14:02:50 <slaweq> lets start
14:03:06 <slaweq> first of all welcome back after 2 weeks :)
14:03:10 <slaweq> #topic Announcements
14:03:45 <slaweq> this week is Victoria-2 milestone
14:04:20 <slaweq> I don't think we need to do any specific releases at that point
14:04:46 <slaweq> but I would like confirmation from amotoki on that :)
14:05:35 <amotoki> I don't think we have any specific issue, but if we have some requirements changes which affect stadium projects it might be worth cuting a beta release.
14:05:52 <amotoki> there is no need to sync with milestone-2 though
14:06:49 <slaweq> ok, so we should be good now IMO
14:06:51 <slaweq> thx amotoki
14:07:07 <slaweq> next announcement
14:07:23 <slaweq> Networking-midonet - today I sent another email with call for maintainers for this project
14:07:44 <slaweq> but I don't expect really that someone will raise hand to do that
14:08:16 <slaweq> so probably next week I will propose some patches to add info that project is going to be deprecated in next cycle
14:08:29 <slaweq> in same way as we did with neutron-fwaas in Ussuri
14:09:03 <slaweq> next one
14:09:12 <slaweq> team meeting - day changed
14:09:24 <slaweq> please note that we will not have Monday meeting anymore
14:09:48 <slaweq> team meetings will be always on Tuesday (like today) on this channel
14:09:57 <slaweq> please update Your calendars :)
14:10:03 <bcafarel> yay from my selfish European point of view :)
14:10:10 <slaweq> bcafarel: exactly :)
14:10:36 <amotoki> me too. 11pm is much better than 6am to me :)
14:10:51 <slaweq> amotoki: I can imagine
14:11:02 <slaweq> ok, any other announcements from the team?
14:11:42 <mlavalle> o/
14:11:46 <slaweq> hi mlavalle
14:11:55 <mlavalle> hi there
14:12:00 <slaweq> I was just saying here that meeting time and place was changed
14:12:21 <slaweq> so please update Your calendar as meeting will be always on Tuesday in this channel
14:12:30 <mlavalle> so, always Tuesay 1400utc #openstack-meeting-3, right?
14:12:38 <slaweq> correct
14:12:45 <mlavalle> +1
14:13:15 <slaweq> ok, lets move on
14:13:16 <slaweq> #topic Blueprints
14:13:27 <slaweq> Blueprints for Victoria-2: https://launchpad.net/neutron/+milestone/victoria-2
14:13:56 <slaweq> do You have any updates about some of them?
14:14:41 <mlavalle> regarding address groups for security group rules...
14:14:53 <mlavalle> hangyang is working on server side coe
14:14:57 <mlavalle> *code
14:15:22 <mlavalle> and for https://review.opendev.org/#/c/741784/2, which is the api definition in neutron lib
14:15:43 <mlavalle> there will be a follow up patch with api-ref
14:15:59 <slaweq> thx
14:16:07 <mlavalle> in the meantime, can I get another review for the patch I just mentioned ^^^^
14:16:13 <slaweq> IMO this neutron-lib patch is now good to go
14:16:30 <mlavalle> I also think so
14:17:14 <ralonsoh> I'll review it today
14:18:04 <slaweq> mlavalle: I have a question about https://blueprints.launchpad.net/neutron/+spec/dns-records-in-neutron
14:18:12 <slaweq> is there anything more needed there?
14:18:20 <slaweq> neutron patch is merged already
14:18:45 <mlavalle> I don't think so
14:18:58 <mlavalle> but I'll ask Hamza later today to be sure
14:19:04 <slaweq> thx
14:19:06 <mlavalle> I'll let you know in the channel
14:19:11 <slaweq> thx a lot
14:20:02 <slaweq> mlavalle: and one more question to You, about https://blueprints.launchpad.net/neutron/+spec/tagging-on-post
14:20:18 <slaweq> IIUC the last missing part is OSC patch https://review.opendev.org/#/c/723280/
14:20:37 <slaweq> will You have time to take a look at it as ci failures seems like related to this change probably
14:20:37 <mlavalle> correct
14:20:41 <mlavalle> I'll finish it
14:20:46 <slaweq> thx a lot
14:20:52 <slaweq> if You need help, please ping me
14:21:05 <mlavalle> ok
14:21:06 <mlavalle> thanks
14:21:30 <slaweq> regarding https://blueprints.launchpad.net/neutron/+spec/default-dns-zone-per-tenant
14:21:33 <slaweq> neutron patch is
14:21:49 <slaweq> IMO ready to review https://review.opendev.org/#/c/686343/
14:21:59 <slaweq> so please add it to Your review queue :)
14:22:26 <slaweq> I need to check some failures in neutron-tempest-plugin patch https://review.opendev.org/#/c/733994/ to finish that BP
14:22:33 <slaweq> I hope to do it this week
14:23:01 <slaweq> and last but not least from my side
14:23:03 <slaweq> https://blueprints.launchpad.net/neutron/+spec/metadata-over-ipv6
14:23:15 <slaweq> before PTO I reviewed some of the patches related to this BP
14:23:32 <slaweq> and now we have still 3 patches in gerrit: https://review.opendev.org/#/q/topic:metadata-ipv6+(status:open+OR+status:merged)
14:23:54 <slaweq> I will try to review them again this week
14:24:04 <slaweq> but please do that also if You will have some time
14:24:28 <njohnston> I removed myself as the assignee for "API Support for Managing Custom Ethertypes" as I will be unable to devote time to it.
14:25:15 <slaweq> thx for info njohnston
14:25:36 <slaweq> I can assign it to myself but I will not have time to do it in this cycle probably
14:26:10 <slaweq> so unless there is someone else who wants to work on it now, I will move it to "neutron-next" for now as we will not finish it in Victoria probably
14:27:54 <slaweq> ok, I think that this is all about BPs for today
14:28:51 <slaweq> #topic Community Goals
14:28:58 * tosky is lurking :)
14:29:06 <slaweq> hi tosky
14:29:18 <slaweq> speaking about tosky and migration to zuul v3
14:29:51 <slaweq> I added it to this section as according to etherpad: https://etherpad.opendev.org/p/goal-victoria-native-zuulv3-migration we still have some work to do
14:30:24 <slaweq> especially for old jobs defined in openstack/openstack-zuul-jobs
14:31:38 <slaweq> I will check those old legacy jobs in next days/weeks
14:32:05 <slaweq> but the question is about networking-midonet - there is a lot of legacy jobs defined in this repo
14:32:36 <slaweq> but most (all) of them are already broken and giving current status of networking-midonet I don't think there will be anyone who will want to work on them
14:32:55 <slaweq> can we maybe simply skip conversion of those jobs?
14:33:42 <bcafarel> +1 especially with pending maintainers call here
14:33:59 <njohnston> since zuul jobs have a single namespace, is there any reason to not just migrate the definition of those jobs into the midonet repo where they can be deprecated with the rest?
14:34:07 <tosky> that's up to you - from the point of view of the goal, there shouldn't be legacy jobs, so if you find out they are not needed, just remove them
14:34:21 <tosky> deprecating/removing a repository is another way to get rid of them, yes
14:34:38 <slaweq> tosky: we will probably deprecate repository in W cycle
14:34:54 <slaweq> but those jobs are not run anywhere already as they are broken
14:35:11 <slaweq> IIRC the problem was that midonet wasn't working properly on Ubuntu Bionic
14:35:14 <tosky> uhm, they should be removed then before branching victoria
14:35:22 <amotoki> slaweq: aren't we going to deprecate networking-midonet in this cycle and remove it in W?
14:35:41 <slaweq> amotoki: it's not like we did with fwaas for example
14:36:01 <slaweq> I want to do it in same way like with fwaas so
14:36:26 <amotoki> slaweq: we deprecated neutron-fwaas in Ussuri and remove it from the neutron stadium in Victoria, so I think we are doing the same.
14:36:28 <slaweq> 1. in Victoria we will add just info to the readme file and documentation that this project is going to be deprecated in next cycle
14:37:01 <slaweq> 2. in W cycle we will deprecate it officially which means that we will remove all code from master branch and keep stable branches only, like we did for neutron-fwaas in this cycle
14:37:33 <slaweq> amotoki: it is correct what You are saying
14:38:02 <slaweq> but official terms are a bit different and deprecation means removal of code from master branch and keep stable branches only
14:39:42 <slaweq> amotoki: is that clear for You now?
14:39:51 <amotoki> slaweq: ah, I see. if we say deprecate/remove the master branch of XXXX, it is correct. From the perspecitve of a repo with all branches, the wording might be different.
14:40:04 <slaweq> amotoki: yes
14:40:51 <amotoki> slaweq: agree with you. anyway we agree we are going to mark networking-midonet master as deprecated.
14:40:58 <slaweq> yes
14:41:00 <slaweq> :)
14:41:40 <slaweq> ok, any updates about Ubuntu Focal?
14:43:04 <bcafarel> not on my side :(
14:43:25 <ralonsoh> no, sorry
14:43:32 <slaweq> np
14:43:45 <slaweq> lets get back to this next week :)
14:43:52 <lajoskatona> +1
14:44:08 <slaweq> and with that I think we are done with community goals
14:44:13 <slaweq> #topic Bugs
14:44:21 <slaweq> njohnston was bug deputy last week: http://lists.openstack.org/pipermail/openstack-discuss/2020-July/016112.html
14:44:37 <slaweq> njohnston: anything You want to bring up here?
14:45:11 <njohnston> just the two I could not triage
14:45:25 <njohnston> https://bugs.launchpad.net/bugs/1888256 on rocky
14:45:26 <openstack> Launchpad bug 1888256 in neutron "Neutron start radvd and mess up the routing table when: ipv6_ra_mode=not set ipv6-address-mode=slaac" [Undecided,New]
14:45:55 <njohnston> which I know haleyb looked into but did not get anywhere
14:46:05 <njohnston> and https://bugs.launchpad.net/bugs/1888464 on stable/stein
14:46:06 <openstack> Launchpad bug 1888464 in neutron "IPv6 PD with DVR does not assign correct snat sg address" [Undecided,New]
14:48:22 <slaweq> if anyone with IPv6 background can take a look into those bugs that would be great
14:49:01 * maciejjozefczyk sorry for beign late
14:50:35 <slaweq> thx njohnston for taking care of bug deputy last week
14:50:45 <slaweq> this week amotoki is our bug deputy
14:50:55 <slaweq> next week will be mlavalle
14:51:06 <mlavalle> ack
14:51:13 <slaweq> please also check table at https://wiki.openstack.org/wiki/Network/Meetings
14:51:14 <amotoki> sure. thanks for the reminder
14:51:52 <slaweq> because I had to remove maciejjozefczyk from this table so weeks for some of You can be 1 week earlier than was planned at the beginning
14:53:01 <slaweq> any other bugs You want to discuss today?
14:54:53 <slaweq> I guess that this means "no" and we can move on
14:55:08 <slaweq> #topic On Demand Agenda
14:55:19 <slaweq> I have one quick item here
14:55:39 <slaweq> some time ago haleyb proposed patch https://review.opendev.org/#/c/735251/ to change some terminology in our code
14:55:53 <slaweq> first of all I would like to ask You to review it
14:56:27 <slaweq> and the other question, mostly to njohnston as tc member - is there maybe any "high level" effort to change that in all OpenStack repos in same way?
14:56:38 <slaweq> or each project should/can do it on their own?
14:59:17 <slaweq> ok, we are running out of time
14:59:24 <slaweq> thx for attending the meeting today
14:59:30 <slaweq> and have a great week
14:59:32 <slaweq> o/
14:59:32 <lajoskatona> o/
14:59:35 <slaweq> #endmeeting