14:00:47 #startmeeting neutron_drivers 14:00:47 Meeting 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:47 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:47 The meeting name has been set to 'neutron_drivers' 14:00:51 \o 14:00:55 Ping list: ykarel, mlavalle, mtomaska, slawek, obondarev, tobias-urdin, lajoskatona, amotoki 14:01:01 \o 14:01:02 o/ 14:01:12 i know rodolfo and slawek cannot make it, so don't know if we will have quorom 14:01:32 ack 14:01:38 o/ 14:02:29 o/ 14:04:18 i think we still need one more for quorom, but we can talk about eventlet lajoskatona 14:04:36 haleyb: ack 14:04:44 seems they all got reverted, so we have nothing do to :) 14:05:25 I 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 managers 14:05:58 ahh, cool, so all reverted, than I am more confused than yesterday :-) 14:06:22 So the basic situation if you haven't followed the mail thread(s) and the governance doc 14:06:23 reverted or abandoned, yes 14:06:56 https://review.opendev.org/c/openstack/governance/+/902585 is the governanace doc proposal 14:07:17 I think it worth reading as a good summary of where we are 14:08:13 So 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:09:29 and 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:49 right, 0.34 and after should be py3.12 compatible 14:10:01 but even with this there's a lot of reason to change from eventlet to something else 14:10:31 so we are good for now? 14:10:41 the 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 it 14:11:05 that 14:11:15 is a big question 14:11:27 mlavalle: 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.34 14:12:07 and after that the same issues are still there (no eventlet maintainers and eventlet was designed for issues with py2.x not for py3... 14:13:12 so 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 it 14:13:55 in other words, we need something else after py3.12 14:13:57 so here we are with it, and I think it is good to know about it and think about it 14:14:10 totally 14:15:16 each project can move to asyncio separately, right? 14:15:21 yes, D release is saved it seems and py312 can be added as supported runtime, but after that a decision must be made 14:16:27 as 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 asyncio 14:16:46 well, only need to write an eventlet->asyncio migration tool, that's it (just kidding) 14:16:55 :-) 14:17:25 aiohub, and seems that's where a lot of the comments are 14:17:47 ahh, es that is the planned project, true 14:19:16 and that's the story basically :-) 14:20:54 lajoskatona: thanks for the discussion 14:21:27 yes. thanks for the overview 14:22:10 I beleive we will hear a lot about this in the coming months :-) 14:23:10 obviously neutron uses eventlet in a number of places like threading in the agents and wsgi layer 14:23:43 haleyb: don't forget to close the meeting 14:23:46 some could probably me migrated quickly, others not so much 14:24:42 mtomaska: we did not have quorum to vote on your item, we can keep it on agenda for next week 14:25:01 i did see rodolfo already sent a WIP patch 14:25:20 #endmeeting