15:00:10 #startmeeting ironic 15:00:10 Meeting started Mon Mar 17 15:00:10 2025 UTC and is due to finish in 60 minutes. The chair is rpittau. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:10 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:10 The meeting name has been set to 'ironic' 15:00:13 o/ 15:00:16 o/ 15:00:17 Hello everyone! 15:00:23 o/ 15:00:24 Welcome to our weekly meeting! 15:00:24 The meeting agenda can be found here: 15:00:24 https://wiki.openstack.org/wiki/Meetings/Ironic#Agenda_for_March_17.2C_2025 15:00:25 \o 15:00:55 let's give a minute for people to join 15:01:15 hmm, wiki is not responding for me :( 15:01:17 o/ 15:01:28 :/ 15:02:03 not a lot in the agenda today anyway 15:02:05 #topic Announcements/Reminders 15:02:17 o/ 15:02:27 #info Standing reminder to review patches tagged ironic-week-prio and to hashtag any patches ready for review with ironic-week-prio: 15:02:27 #link https://tinyurl.com/ironic-weekly-prio-dash 15:03:06 I see there are still some patches to review there, epoxy release is upon us 15:03:29 just skipping to the most important point 15:03:48 #info 2025.1 Epoxy Release Schedule 15:03:48 we're at R-2 15:03:56 o/ 15:04:10 meaning we need to check for any leftover patches 15:04:14 I think we just need to release at this point, change 699953 is the only one which I honestly think could be classified as a fix backport if it comes down to it 15:04:19 the stable branches cut patches are out already 15:04:25 TheJulia: sounds good 15:04:26 cool cool 15:04:31 jsut wanted confirmation 15:04:44 gimme 1 evening to see if https://review.opendev.org/c/openstack/ironic/+/939217 is ready 15:04:50 sure 15:04:56 We're just 2 patches away from inspection rules, I understand? 15:05:05 1 patch? 15:05:14 is it just docs? 15:05:15 https://review.opendev.org/c/openstack/python-ironicclient/+/937628 too 15:05:21 too late then 15:05:22 well, the client missed epoxy already 15:05:30 I see 15:05:30 yep 15:05:37 client's gone 15:05:44 Alright 15:05:50 in theory we can merge only ironic and ipa now, but I left some space for ngs 15:06:21 oh and ironic-tempest-plugin ? 15:06:23 I think ngs had a change merge this morning which would make sense, but yeah, I think its time to just get it all in order and move forward from there 15:06:35 yeah, end of cycle release of i-t-p makes sense 15:06:40 alright 15:07:22 Honestly not a big deal if ironicclient support for rules misses epoxy; no upper-constraint respecting project will be using that support 15:07:27 so we just need to get it in and released for users 15:07:49 ok 15:08:02 so I'll wait until tomorrow morning before closing the releases 15:08:11 ++ 15:08:27 JayF: you raise an interesting point, upper-constraints respecting projects in general shouldn't be client at this point 15:08:34 they should be using the sdk 15:09:25 (in other words, openstack might want to revisit the client library holds in general since they are no longer libraries, they are tools) 15:09:44 a good point 15:09:46 ((but this is not a discussion for this moment)) 15:10:01 mm interesting point 15:10:46 anything more to discuss on the incoming releases/branch cuts ? 15:11:41 alright! 2 weeks to go! :) 15:12:11 #info Flamingo PTG will take place place April 7-11, 2025! 15:12:11 dont' forget to add topics to the etherpad: 15:12:11 #link https://etherpad.opendev.org/p/ironic-ptg-april-2025 15:12:15 and don't forget to register! 15:13:24 anything else to announce/remind ? 15:13:49 Do we still need to register Ironic times? 15:13:51 For the PTG? 15:14:08 I believe we still need to 15:14:11 JayF: nope, that's done already 15:14:14 cool 15:14:41 https://ptg.opendev.org/ptg.html no, it's not 15:14:42 just need to prepare the schedule 15:14:42 probably start reserving some dates/times this week based on what we have in the schedule 15:14:54 yeah, that's what I'm talking about, getting the ironic times registered into the system 15:14:55 JayF: oh you mean that 15:15:10 not done yet as I was waitingto have some topics to understand how much time we need 15:15:39 I would assume we're going to need a bit of time because we're getting into complex networking items where we're going to need to have some deep discussions 15:15:46 so, in other words 15:15:51 I wouldn't think of it as "30 minutes per topic" 15:16:08 yep 15:16:08 I will add at least 3 hours per day monday till thursday 15:16:09 and I'd think... ~2 hours per complex topic 15:16:11 then we adjust 15:17:40 there's no discussion topic planned for today, any open discussion? 15:18:08 oh actually I forgot one very important thing! 15:18:35 the ironic outreachy project has been accepted and it's open for applications 15:19:41 masghar and myself are the designated mentors for this round :) 15:19:58 :D 15:20:35 we'll try to provide updates every week, but for now we're just waiting for applications 15:21:09 Here is the project link: https://www.outreachy.org/outreachy-june-2025-internship-cohort/communities/openstack/set-bare-metal-hosts-clock-remotely-using-redfish/cfp/ 15:22:37 anything else to add or any other topic to discuss? 15:23:40 ok, thanks everyone! 15:23:40 #endmeeting