14:00:02 <lajoskatona> #startmeeting networking
14:00:02 <opendevmeet> Meeting started Tue Sep 20 14:00:02 2022 UTC and is due to finish in 60 minutes.  The chair is lajoskatona. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:00:02 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:00:02 <opendevmeet> The meeting name has been set to 'networking'
14:00:04 <lajoskatona> o/
14:00:07 <ralonsoh> hi
14:00:17 <haleyb> hi
14:00:23 <mlavalle> o/
14:00:43 <slaweq> o/
14:01:23 <bcafarel> \o
14:01:42 <frickler> o/
14:02:45 <lajoskatona> I think we can start
14:02:50 <lajoskatona> #topic Announcements
14:03:00 <lajoskatona> The usual Zed schedule: https://releases.openstack.org/zed/schedule.html
14:03:03 <ykarel> o/
14:03:13 <lajoskatona> [release] Release countdown for week R-2, Sep 19 - 23 (#link https://lists.openstack.org/pipermail/openstack-discuss/2022-September/030506.html )
14:03:23 <lajoskatona> Important dates:
14:03:25 <lajoskatona> Final RC deadline: September 29th, 2022 (R-1 week)
14:03:25 <lajoskatona> Final Zed release: October 5th, 2022
14:03:25 <lajoskatona> Virtual PTG: October 17-21, 2022
14:03:46 <lajoskatona> And we have RC1, and stable/zed branch :-)
14:04:34 <ralonsoh> +1
14:04:48 <lajoskatona> I pushed the job definitions patch for Zed: https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/858097
14:04:57 <lajoskatona> and: https://review.opendev.org/c/openstack/neutron/+/858138
14:05:16 <lajoskatona> Please check it to have test coverage for zed
14:05:32 <slaweq> lajoskatona thx, I will review it
14:05:37 <lajoskatona> slaweq: thanks
14:05:59 <lajoskatona> to tell the truth finally I lost a little in our jobs :P
14:06:24 <slaweq> :)
14:07:47 <lajoskatona> Do you have comments or notes for the release, perhaps we missed something out?
14:08:13 <slaweq> not about release, but about PTG is I may
14:08:25 <lajoskatona> please
14:08:54 <slaweq> it's mostly to lajoskatona and ralonsoh - we should book some operator hours for neutron, see https://lists.openstack.org/pipermail/openstack-discuss/2022-September/030301.html for details
14:09:15 <rubasov> late o/
14:09:27 <ralonsoh> right, but is this a generic reservation?
14:09:37 <ralonsoh> so anyone can attendm, right?
14:09:47 <slaweq> ralonsoh so, slots are "predefined" in https://ptg.opendev.org/ptg.html
14:10:05 <slaweq> and we need to pick one of them and book it as "operator-hour-neutron"
14:10:27 <lajoskatona> slaweq: thanks, I missed this booking
14:10:27 <slaweq> and yes, it's "generic" so every operator can attend that slot and share their feedback about neutron with us
14:10:29 <mlavalle> can I attend as well?
14:10:39 <slaweq> mlavalle of course :)
14:10:42 <ralonsoh> should we first decide the meeting hours?
14:10:53 <ralonsoh> and then assign the operator hour(s)
14:10:56 <ralonsoh> ?
14:10:59 <slaweq> by "mostly to lajoskatona and ralonsoh" I meant that they should book it probably
14:11:07 <ralonsoh> yes
14:11:08 <slaweq> but session should be available for everyone of course
14:11:55 <lajoskatona> hmmm, even the etherpad link is incorrect :-(
14:11:58 <slaweq> ralonsoh yes, I think that it would be the best if we can pick one of the slots which will be in the same time as neutron sessions during PTG :)
14:12:13 <ralonsoh> ok, should I send a poll to ask for the Neutron sessions?
14:12:22 <ralonsoh> I think we should fill the schedule asap
14:12:40 <slaweq> didn't lajoskatona already send it?
14:12:45 <slaweq> I'm not sure
14:12:47 <lajoskatona> ralonsoh: agree, I overslept this schedule
14:12:54 <slaweq> ahh, ok
14:13:00 <slaweq> so it's definitely time to do so :)
14:13:01 <ralonsoh> I'll do it today
14:13:04 <slaweq> I can help if You want
14:13:12 <ralonsoh> and then I'll update the schedule of the PTG
14:13:26 <lajoskatona> thanks
14:13:33 <ralonsoh> and also another one for the operator hour, not clashing with the schedule of the PTG
14:13:38 <opendevreview> Miguel Lavalle proposed openstack/neutron master: Fix openstack-tox-py39-with-oslo-master job  https://review.opendev.org/c/openstack/neutron/+/855703
14:15:54 <lajoskatona> ok, I think we can jump, thanks slaweq for bringing this topic
14:16:13 <slaweq> yw lajoskatona :)
14:16:52 <lajoskatona> The usual bare recheck warning: https://etherpad.opendev.org/p/neutron-ci-meetings#L59
14:17:13 <lajoskatona> as I see we are quite good, 14.29% as I see
14:17:20 <mlavalle> +1
14:17:39 <slaweq> yes, we are good, thx a lot :)
14:17:45 <lajoskatona> please always check the results before recheck
14:18:24 <slaweq> ++
14:18:59 <lajoskatona> #topic Bugs
14:19:08 <lajoskatona> Report from mlavalle: https://lists.openstack.org/pipermail/openstack-discuss/2022-September/030509.html
14:19:25 <lajoskatona> mlavalle: any bugs you would like to highlight?
14:19:36 <mlavalle> no comments. It was a quiet week in the bugs front
14:19:39 <lajoskatona> I didn't see any comlications in your report
14:19:45 <mlavalle> and we have all of them under control
14:19:49 <lajoskatona> mlavalle: cool, thanks
14:20:15 <lajoskatona> This week rubasov is the deputy and next week ralonsoh will be.
14:20:19 <ralonsoh> ack
14:20:21 <rubasov> on it
14:20:30 <lajoskatona> ralonsoh, rubasov: thanks
14:21:12 <lajoskatona> #topic On Demand Agenda
14:21:27 <lajoskatona> Do you have anything to discuss?
14:21:57 <slaweq> Please remember about CI meeting in about 40 minutes. It will be video meeting this week 😃
14:22:02 <frickler> I made progress with cirros
14:22:20 <frickler> except for some OVN issue, all tests are running without Ubuntu now
14:22:27 <ralonsoh> what issue?
14:22:53 <lajoskatona> slaweq: ack
14:23:02 <frickler> ralonsoh: not sure yet, see the latest results at https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/854910
14:23:05 <lajoskatona> frickler: sounds great
14:23:29 <frickler> one issue may be because I had to turn on dhcp, since cirros cannot currently use config-drive for network setup
14:24:26 <frickler> next I'll discuss with cirros maints whether and how we would actually release this. since including python3 roughly doubles the image size
14:24:55 <ralonsoh> and do we need larger VMs? more RAM
14:25:33 <frickler> nope, certainly not more than Ubuntu. I didn't try yet to reduce flavor size
14:25:38 <lajoskatona> i suppose it will be smaller than ubuntu
14:26:01 <ralonsoh> yeah, just asking if the old default cirros flavor is enough
14:26:05 <frickler> I also did not test yet replacing the "normal" cirros image. only the advanced image so far
14:26:16 <ralonsoh> ok
14:26:20 <frickler> that would be an interesting next step though
14:26:28 <ralonsoh> in any case, this is a good improvement, thanks!
14:26:49 <lajoskatona> if we increase the image for all tests perhaps we lose more, so perhaps we can have a legacy and a new cirros which can work networking tests?
14:27:03 <ralonsoh> we can use both
14:27:13 <frickler> maybe cirros needs to publish two flavors of image, yes
14:27:17 <ralonsoh> but this new cirros image is smaller than ubuntu
14:27:23 <ralonsoh> so we win there
14:27:24 <frickler> like cirros and cirros++
14:27:32 <lajoskatona> :-)
14:28:12 <frickler> but it will actually allow us to get rid on needing nested-virt for performance reasons
14:28:24 <frickler> I tested with qemu and it works as well
14:28:39 <lajoskatona> frickler: thanks for the news
14:28:57 <ykarel> ++
14:29:28 <lajoskatona> Is there anything more which we can discuss?
14:29:42 <slaweq> frickler that's really good news, thx a lot
14:30:06 <mlavalle> frickler: thank you ++
14:32:02 <lajoskatona> If nothing more to discuss, let's close the meeting for today
14:32:11 <slaweq> o/
14:32:13 <ralonsoh> bye
14:32:13 <lajoskatona> #endmeeting