14:00:02 <lajoskatona> #startmeeting networking
14:00:02 <opendevmeet> Meeting started Tue Aug 16 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> Hi
14:00:04 <mlavalle> o/
14:00:14 <frickler> \o
14:00:16 <averdaguer> o/
14:00:23 <rubasov> o/
14:01:00 <slaweq> o/
14:01:12 <ralonsoh> hi
14:02:37 <lajoskatona> let's start it :-)
14:02:43 <lajoskatona> #topic Announcements
14:02:50 <lajoskatona> the usual Zed schedule: https://releases.openstack.org/zed/schedule.html
14:02:58 <lajoskatona> we are at the end of it
14:03:04 <bcafarel> late o/
14:03:13 <lajoskatona> see the mail from elodilles: [release] Release countdown for week R-7, Aug 15 - 19 (#link https://lists.openstack.org/pipermail/openstack-discuss/2022-August/029965.html )
14:03:33 <lajoskatona> The important dates from it:
14:03:42 <lajoskatona> Non-client library freeze: August 26th, 2022 (R-6 week)
14:04:14 <lajoskatona> that is neutron-lib and next week, so if you have anything to merge, raise your hand and we can increase the review prioirty
14:04:19 <lajoskatona> Client library freeze: September 1st, 2022 (R-5 week)
14:04:24 <lajoskatona> Zed-3 milestone: September 1st, 2022 (R-5 week)
14:04:33 <slaweq> not only neutron-lib
14:04:36 <slaweq> also ovsdbapp and os-ken IIRC
14:04:47 <lajoskatona> yeah sorry, true
14:05:09 <lajoskatona> I checked yesterday and we have only one or 2 patches hanging
14:05:16 <lajoskatona> in these
14:06:25 <lajoskatona> Some info for the PTG:
14:06:29 <lajoskatona> Antelope PTG etherpad: https://etherpad.opendev.org/p/neutron-antelope-ptg
14:06:36 <lajoskatona> It will be a 100% virtual event, see: https://lists.openstack.org/pipermail/openstack-discuss/2022-August/029879.html
14:06:47 <lajoskatona> I updated the etherpad based on this info
14:07:31 <lajoskatona> Please register to it, it is free: https://openinfra-ptg.eventbrite.com/
14:08:11 <lajoskatona> bad news that there will be no beer and pizza (or whatever session) dinner, but we can have higher participation
14:09:22 <mlavalle> we can drink our beers toegether during th last session
14:09:26 * slaweq is sad because of this
14:09:41 <lajoskatona> mlavalle: true :-)
14:09:51 <mlavalle> and a slice of pizza
14:10:26 <lajoskatona> another small info: perhaps you remember that an operator day was planned for Firday of that week
14:11:07 <lajoskatona> perhaps we can add session for operators, but it is under organization by Kendall and Amy
14:11:23 <mlavalle> that would be good
14:11:31 <mlavalle> operators feedback is always good
14:11:45 <lajoskatona> +1
14:13:24 <lajoskatona> That's it for announcement, do you have any questions or comments?
14:14:16 <frickler> is there any data yet on when sessions will be scheduled? just like last time?
14:15:00 <lajoskatona> I haven't seen it yet
14:15:16 <opendevreview> Alex Katz proposed openstack/neutron-tempest-plugin master: Use StatefulConnection class to verify connectivity in SG tests  https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/853203
14:15:41 <lajoskatona> just the days: October 17-21
14:16:04 <frickler> so no Friday? that would make scheduling even harder
14:16:24 <lajoskatona> No 21 is Friday
14:16:39 <frickler> ah, right, fine then
14:17:29 <lajoskatona> Ok next topic
14:17:32 <lajoskatona> #topic Bugs
14:17:45 <lajoskatona> Report from isabek: https://lists.openstack.org/pipermail/openstack-discuss/2022-August/029787.html
14:18:21 <lajoskatona> I see only tis one as hanging: Failed to process compatible router - network is unreachable (#link https://bugs.launchpad.net/neutron/+bug/1982882 )
14:18:41 <lajoskatona> As I see waiting for more info
14:18:42 <ralonsoh> yeah but we need more ingo
14:18:44 <ralonsoh> yes
14:18:51 <lajoskatona> thanks ralonsoh
14:19:13 <lajoskatona> Report from elvira for the next week: https://lists.openstack.org/pipermail/openstack-discuss/2022-August/029900.html
14:19:34 <lajoskatona> as I checked all bug from that week is covered
14:19:46 <lajoskatona> And the last one:
14:19:48 <lajoskatona> Report from bcafarel: https://lists.openstack.org/pipermail/openstack-discuss/2022-August/029987.html
14:20:08 <lajoskatona> I saw an old manila bug arriving to us:
14:20:10 <lajoskatona> [CI][Devstack] Failing to SSH to test VMs with IPv6 (#link https://bugs.launchpad.net/neutron/+bug/1940324)
14:20:51 <lajoskatona> I checked only some config lines and they use dynamic routing and quagga in these jobs
14:22:12 <lajoskatona> hmmm, and as I mentioned it perhaps the problem is that they run it with ovn, and that is not working with n-d-r (local.conf from the bug: https://paste.openstack.org/show/808159/ )
14:22:44 <bcafarel> oh true I did not think of n-d-r/ovn combo
14:22:55 <frickler> oh, so that's a duplicate of a long standing issue then, nice
14:23:17 <ralonsoh> which one? for documentation
14:23:25 <lajoskatona> yeah, but manilla can change this job to use ovs I suppose
14:24:10 <bcafarel> it sounds worth asking them to test and see if the job works with ovs
14:24:33 <lajoskatona> I dont know if there is a bug for it, I know this dnm patch: https://review.opendev.org/c/openstack/neutron-dynamic-routing/+/814055
14:24:53 <ralonsoh> thanks
14:24:54 <lajoskatona> bcafarel: agree, I add a comment on the bug
14:25:07 <frickler> I think the bug was closed because it was documented as missing feature on the OVN matrix
14:25:36 <lajoskatona> frickler: that is possible.
14:26:17 <lajoskatona> ok, I saw another bug which has no owner:
14:26:20 <lajoskatona> Exception in concurrent port binding activation (#link https://bugs.launchpad.net/neutron/+bug/1986003 )
14:26:29 <ralonsoh> I'm checking this one
14:26:38 <ralonsoh> it's complicated to reproduce it
14:26:46 <mlavalle> thanks ralonsoh
14:26:47 <lajoskatona> just opened it and Bodo Peterman started to work on it :-)
14:27:05 <frickler> this is the OVN vs. BGP bug https://bugs.launchpad.net/neutron/+bug/1959666
14:27:29 <lajoskatona> frickler: thanks
14:28:59 <lajoskatona> any comments or questions for the bugs from the last weeks, or any bug to discuss?
14:29:09 <ralonsoh> not from me
14:29:27 <slaweq> nothing from me neighter
14:29:39 <bcafarel> all good here (and thanks ralonsoh for checking that live migration bug)
14:29:51 <slaweq> but just one quick thing regarding next week's non-client libs freeze
14:30:27 <lajoskatona> let's hear it
14:30:33 <slaweq> here are not released changes in os-ken and ovsdbapp https://paste.opendev.org/show/bTyAOsAZYSISrWewjMJK/
14:30:53 <slaweq> so IMO we should propose one more release of each of them before freeze
14:31:05 <ralonsoh> agree
14:31:41 <slaweq> that's all from me :)
14:32:10 <lajoskatona> slaweq: thanks, and agree
14:32:28 <lajoskatona> one more thing for bugs:
14:32:31 <lajoskatona> This week lajoskatona is the deputy and next week slaweq will be.
14:32:38 <slaweq> ok
14:32:43 <slaweq> good for me
14:32:49 <lajoskatona> slaweq: thanks
14:32:58 <lajoskatona> #topic On Demand Agenda
14:33:11 <lajoskatona> Do you have anything we can discuss?
14:33:42 <frickler> I have a question regarding cirros
14:34:01 <frickler> We are pretty closing to making a new release, which will very likely become 0.6.0
14:34:23 <opendevreview> Merged openstack/neutron stable/wallaby: [ovn]Change LogicalSwitchPortUpdateUpEvent old conditions  https://review.opendev.org/c/openstack/neutron/+/852155
14:34:34 <frickler> and my idea is to support as many CI features as possible, maybe even make the use of ubuntu as advanced image obsolete
14:34:57 <frickler> is someone interested in testing this and possibly listing features that are still missing?
14:36:05 <lajoskatona> frickler: sounds great
14:36:11 <slaweq> frickler: I can definitely prepare list of features which we are missing in cirros and why we need to use ubuntu in some tests
14:36:23 <lajoskatona> can't we have some periodic job or similar for it?
14:36:53 <slaweq> lajoskatona: if that will be ready I think we can simply switch our regular jobs to use new cirros
14:37:11 <frickler> you can find the latest builds as artifacts here https://github.com/cirros-dev/cirros/actions/runs/2834915920
14:37:31 <frickler> I can also try to put them onto some webserver for easier digestion
14:37:41 <lajoskatona> I mean to test the advanced features with master cirros or similar
14:38:10 <frickler> or maybe we can actually look into publishing a set of cirros-latest images, that's a good idea
14:38:16 <slaweq> lajoskatona: I think we can have just DNM patch which will use such image from master
14:38:35 <lajoskatona> slaweq: yeah, that is good
14:38:36 <slaweq> and when it will work and will be fine, we can update it in regular jobs
14:38:49 <slaweq> I don't think we need to have such periodic job forever
14:39:27 <lajoskatona> I thought as temporary one, but after saying it is not good idea :-(
14:40:53 <frickler> maybe I'll look into doing it the other way around, run some neutron job in cirros CI, that sounds more reasonable
14:41:11 <slaweq> frickler: true
14:41:19 <lajoskatona> frickler: thanks
14:41:38 <frickler> thanks for you ideas, that was helpful
14:41:42 <frickler> *yur
14:41:46 <frickler> *your even
14:42:10 <lajoskatona> if no more topics we can close the meeting
14:42:20 <slaweq> ++
14:42:28 <slaweq> and please remember about CI meeting in 18 minutes
14:42:34 <bcafarel> :)
14:42:37 <slaweq> it will be video meeting this week
14:42:39 <lajoskatona> it will be video meeting this time?
14:42:43 <lajoskatona> ahh thanks
14:42:45 <slaweq> yes :)
14:43:00 <lajoskatona> #endmeeting