15:00:24 #startmeeting ironic 15:00:24 Meeting started Mon Feb 26 15:00:24 2024 UTC and is due to finish in 60 minutes. The chair is JayF. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:24 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:24 The meeting name has been set to 'ironic' 15:00:30 o/ 15:00:34 o/ 15:00:35 o/ 15:00:37 #topic Announcements/Reminders 15:00:42 #info Standing reminder to review patches tagged ironic-week-prio and to hashtag any patches ready for review with ironic-week-prio: https://tinyurl.com/ironic-weekly-prio-dash 15:00:47 #info Project Teams Gathering (PTG) will be held from Monday, April 8 to Friday, April 12 2024 - https://etherpad.opendev.org/p/ironic-ptg-april-2024 15:01:00 #info Ironic Meetup/BareMetal SIG June 5, OpenInfra Days June 6 @ CERN. Signup at https://indico.cern.ch/event/1378171/ and https://indico.cern.ch/event/1376907/ 15:01:07 #topic Caracal Release Schedule 15:01:23 #info Client library freeze is 2/29. Please ensure our clients are happy and releable 15:01:33 #link https://review.opendev.org/q/project:openstack/python-ironicclient+branch:master+is:open 15:01:53 $topic Review Ironic CI Status 15:01:55 How is CI? 15:02:16 seems pretty stable ime 15:02:23 but I mostly observed over the weekend :) 15:02:34 nothing to report, but we should probably reenable functional job in ironicclient ASAP 15:02:46 depends on this https://review.opendev.org/c/openstack/tempest/+/908727 15:03:21 alright, I have that open will put a review on it 15:03:31 Moving on if there's nothing else... 15:03:47 #topic vPTG planning 15:03:58 rpittau I think you were going to say some things about ptg? 15:04:07 yes 15:04:22 we need to define the schedule for the PTG as we did last time 15:04:35 and consider if we want an operator hour this time too 15:04:50 I wa sthinking to book 3-4 hours tuesday wednesday and thursday 15:04:51 IIRC the last operator hour was mostly us talking... 15:04:58 I like the idea, in theory of an operator hour, but ^ 15:05:04 yeah 15:05:21 I am +1 to not planning one if we do not anticipate or have reason to believe attendance will change 15:05:28 I'm going to book the normal time for now 15:05:31 Maybe like of promotion on our side, but I also don't know how to fix that 15:06:14 I've indicated to avoid scheduling at the same time as nova if possible in case we need some cross-project time with them 15:06:24 dtantsur: I'm not convinced there's a market for it in general tbh 15:06:29 rpittau: and TC, please 15:06:34 JayF: sure 15:06:36 rpittau: TC usually is late/early week, I haven't scheduled it yet 15:06:39 I thnk I added that too :) 15:06:54 It's weird. I feel like a lot of folks want to talk about Ironic, they just don't come... 15:07:12 I think operator hours are just ... not appealing as a venue 15:07:15 people feel more comfortable in person 15:07:32 and we'd have to have 4 of them to make them convienient tomany possible timezones 15:07:52 It is an advertising, awareness, and willingness to open up in a “public” space issue 15:08:11 * TheJulia goes to make taking day off coffee 15:08:56 * JayF is happy to delegate the operator hour will we/won't we to rpittau 15:09:03 in case someone is interested we can always book some time later 15:09:33 for now I think we can concentrate on the normal schedule 15:10:03 ++ 15:10:25 Folks should propose and comment on topics here: 15:10:32 #link https://etherpad.opendev.org/p/ironic-ptg-april-2024 15:10:37 Moving on 15:10:49 #topic Lextudio not maintaining pyasn1 15:10:53 Whose topic is this? 15:10:56 that's me again 15:11:14 lextudio yanked the latest releases of pyqsn1 and pyasn1-modules 15:11:24 stating that people should just use the normal pyasn1 15:11:37 they don't seem to want to keep maintaing that 15:11:45 is there a reason we don't use normal pyasn1? 15:11:48 so we should probably move back to pyasn1 15:12:08 we moved to lextudio to keep consistency in the snmp ecosystem 15:12:30 which is really ironic now :) 15:12:36 consistency \o/ 15:13:01 rpittau: we should make noise about that, if we're basically maintaining the snmp libraries for python lol 15:13:55 So if this an urgent item? 15:14:01 Do we need to migrate for C or D? 15:14:09 as far as I can see the lextudio snmp works well with normal pyasn1, so my proposal would be to migrate back to that in D 15:14:17 should be ok for C 15:14:27 ack; then I suggest we punt to PTG 15:14:33 sounds good 15:14:33 unless someone has a lot of time and wants to JFDI :) 15:14:45 #topic Bug Deputy 15:14:52 sounds like TheJulia took the day off, she was bug deputy 15:15:06 I only added new bugs last week, sorry! 15:15:08 I said I'd take it this week, but I may kick that to next 15:15:14 I need to get something done before C-3 15:15:45 I can take a look this week 15:15:50 #info dtantsur bug deputy 15:15:54 thanks 15:16:01 No RFEs for review, skipping 15:16:05 #topic Open Discussion 15:16:10 anything not on the agenda for open discussion? 15:16:56 Last call 15:17:39 #endmeeting