Friday, 2024-01-19

opendevreviewliuyulong proposed openstack/neutron master: Check subnet service_type for subnet_create  https://review.opendev.org/c/openstack/neutron/+/90122500:53
opendevreviewliuxie proposed openstack/neutron-tempest-plugin master: Add test job for address_group api backend Ml2/OVN  https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/90602003:08
opendevreviewMerged openstack/ovn-bgp-agent stable/2023.2: Use netaddr IPNetwork instead of parsing IP strings  https://review.opendev.org/c/openstack/ovn-bgp-agent/+/90553309:57
opendevreviewMerged openstack/ovn-bgp-agent stable/2023.2: Remove copy&paste code from ensure_arp_ndp_enabled_for_bridge  https://review.opendev.org/c/openstack/ovn-bgp-agent/+/90573309:57
opendevreviewMichel Nederlof proposed openstack/ovn-bgp-agent master: Fix startup if the hostname is not configured in OVS and use the system-id.  https://review.opendev.org/c/openstack/ovn-bgp-agent/+/90604309:58
opendevreviewFernando Royo proposed openstack/ovn-bgp-agent master: Add support to PF OVN LBs for NB Driver  https://review.opendev.org/c/openstack/ovn-bgp-agent/+/90550410:22
opendevreviewMichel Nederlof proposed openstack/ovn-bgp-agent master: Fix misplacement if options.requested-chassis does not match external_ids.neutron:host_id  https://review.opendev.org/c/openstack/ovn-bgp-agent/+/90611113:51
opendevreviewMichel Nederlof proposed openstack/ovn-bgp-agent master: Fix misplacement if options.requested-chassis does not match external_ids.neutron:host_id  https://review.opendev.org/c/openstack/ovn-bgp-agent/+/90611113:52
haleyb#startmeeting neutron_drivers14:00
opendevmeetMeeting started Fri Jan 19 14:00:47 2024 UTC and is due to finish in 60 minutes.  The chair is haleyb. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
opendevmeetThe meeting name has been set to 'neutron_drivers'14:00
mlavalle\o14:00
haleybPing list: ykarel, mlavalle, mtomaska, slawek, obondarev, tobias-urdin, lajoskatona, amotoki14:00
mlavalle\o14:01
obondarevo/14:01
haleybi know rodolfo and slawek cannot make it, so don't know if we will have quorom14:01
mlavalleack14:01
mtomaskao/ 14:01
lajoskatonao/14:02
haleybi think we still need one more for quorom, but we can talk about eventlet lajoskatona 14:04
lajoskatonahaleyb: ack14:04
haleybseems they all got reverted, so we have nothing do to :)14:04
lajoskatonaI think at the moment it iis just to have a common view of what we can expect and give time everybody to think about it, perhaps with company managers14:05
lajoskatonaahh, cool, so all reverted, than I am more confused than yesterday :-)14:05
lajoskatonaSo the basic situation if you haven't followed the mail thread(s) and the governance doc14:06
haleybreverted or abandoned, yes14:06
lajoskatonahttps://review.opendev.org/c/openstack/governance/+/902585 is the governanace doc proposal14:06
lajoskatonaI think it worth reading as a good summary of where we are14:07
lajoskatonaSo eventlet is not maintained most of the seasoned maintainers are left, and it is not py312 compatibel (before 0.34, I hope I remember well the numbers)14:08
lajoskatonaand Harve and other guys contacted the last eventlet cores, and started to help around eventlet to fix the most urgent issues, so now it basically works with py312 (that is 0.34 release of eventlet for which the patches were up yesterday and were abandoned)14:09
haleybright, 0.34 and after should be py3.12 compatible14:09
lajoskatonabut even with this there's a lot of reason to change from eventlet to something else14:10
mlavalleso we are good for now?14:10
lajoskatonathe something else is a question, in the doc asyncio is the goal, but there's a debate in the comments, and another big question who will do it14:10
mlavallethat14:11
mlavalleis a big question14:11
lajoskatonamlavalle: yes, at the moment as for 2024.1 py312 is not a goal we are safe but for Dalmatian py312 must be supported so for that we need 0.3414:11
lajoskatonaand after that the same issues are still there (no eventlet maintainers and eventlet was designed for issues with py2.x not for py3...14:12
lajoskatonaso this is basically, but the doc the guys prepared is much better than me as they know much more and collected a lot of fact, and the discussions also added extra points to it14:13
mlavallein other words, we need something else after py3.1214:13
lajoskatonaso here we are with it, and I think it is good to know about it and think about it 14:13
mlavalletotally14:14
haleybeach project can move to asyncio separately, right?14:15
lajoskatonayes, D release is saved it seems and py312 can be added as supported runtime, but after that a decision must be made14:15
lajoskatonaas I understand they want to first move the oslo libs (oslo.services, oslo.privsep....) and create a lib that is some kind of glue loginc that hide the diff between eventlet and asyncio14:16
obondarevwell, only need to write an eventlet->asyncio migration tool, that's it (just kidding)14:16
lajoskatona:-)14:16
haleybaiohub, and seems that's where a lot of the comments are14:17
lajoskatonaahh, es that is the planned project, true14:17
lajoskatonaand that's the story basically :-)14:19
haleyblajoskatona: thanks for the discussion14:20
mlavalleyes. thanks for the overview14:21
lajoskatonaI beleive we will hear a lot about this in the coming months :-)14:22
haleybobviously neutron uses eventlet in a number of places like threading in the agents and wsgi layer14:23
mlavallehaleyb: don't forget to close the meeting14:23
haleybsome could probably me migrated quickly, others not so much14:23
haleybmtomaska: we did not have quorum to vote on your item, we can keep it on agenda for next week14:24
haleybi did see rodolfo already sent a WIP patch14:25
haleyb#endmeeting14:25
opendevmeetMeeting ended Fri Jan 19 14:25:20 2024 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:25
opendevmeetMinutes:        https://meetings.opendev.org/meetings/neutron_drivers/2024/neutron_drivers.2024-01-19-14.00.html14:25
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/neutron_drivers/2024/neutron_drivers.2024-01-19-14.00.txt14:25
opendevmeetLog:            https://meetings.opendev.org/meetings/neutron_drivers/2024/neutron_drivers.2024-01-19-14.00.log.html14:25
lajoskatonao/14:25
haleybin the meantime let's merge some patchez!14:26
mlavallehave a nice weekend y14:26
obondarevo/14:26
opendevreviewAndrew Bonney proposed openstack/neutron master: l3agent: add iptables rule to block mldv2 responses  https://review.opendev.org/c/openstack/neutron/+/90611414:44
rubasovhi everyone: I found a proper repro for https://bugs.launchpad.net/neutron/+bug/2048785 and doing that I realized this may have security implications so changed the bug report to "Public Security", since both the report and the proposed fix were public already. Please correct me if it's better set to private...15:22
haleybrubasov: i'm not sure it can be private since it was already public15:27
rubasovyes, I see that way too, it does not make much sense to make it private after it was public already15:30
opendevreviewBrian Haley proposed openstack/neutron master: Consume code from neutron-lib  https://review.opendev.org/c/openstack/neutron/+/90535422:21

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!