15:00:39 #startmeeting ironic 15:00:39 Meeting started Mon Mar 11 15:00:39 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:39 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:39 The meeting name has been set to 'ironic' 15:00:45 o/ 15:00:46 o/ 15:00:47 * TheJulia grumbles about daylight savings time 15:00:54 o/ 15:00:58 o/ 15:00:58 o/ 15:01:05 Welcome to the weekly Ironic meeting. We operate under the OIF Code of Conduct. 15:01:10 #topic Announcements/Reminders 15:01:15 #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:01:22 #info Project Teams Gathering (PTG) will be held from Monday, April 8 to Friday, April 12 2024 15:01:28 #link https://etherpad.opendev.org/p/ironic-ptg-april-2024 15:01:34 #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:51 #topic Caracal Release Schedule 15:02:05 It's R-3 week, RC1s are due RC-ing projects by March 14th. 15:02:14 We don't RC, but that also serves as a good point to us to get our release going 15:02:29 If anyone has a specific change they want in Caracal, please let me know 15:02:40 I'm going to be focusing on landing stragglers and cutting releases this week 15:03:10 We will probably want https://review.opendev.org/c/openstack/ironic/+/912336 15:03:20 this week? :O 15:03:23 oh wow 15:03:45 ++ to this change 15:03:47 3 weeks until the release is final-final, and we can't ask releases team to take our deliverables last minute 15:03:53 so yeah, we gotta get moving :D 15:03:57 and also https://review.opendev.org/c/openstack/ironic/+/907991?usp=dashboard if we want the new inspection to be (more usable) for non-standalone folks 15:04:21 I'll try to squeeze in one more this week, fingers crossed 15:04:44 Please let me know if you have a change up you want in so I don't ninja the release under you :D 15:04:47 rpittau: you mean, vmedia implementation? 15:04:50 yeah 15:04:58 oh yeah. API without a single implementation is not great 15:05:02 yep 15:06:17 lets make sure we get things up fast :) time is coming up quickly 15:06:21 #topic Review Ironic CI Status 15:06:26 I'm pretty sure IPA gate is broken 15:06:34 I have a task on my todo list to dig into that today 15:07:40 Julia Kreger proposed openstack/ironic master: Fix artifical rbac policy constraint that resulted in 500s https://review.opendev.org/c/openstack/ironic/+/910969 15:08:25 I guess nothing else about CI status 15:08:31 #topic vPTG planning 15:09:12 Please review https://etherpad.opendev.org/p/ironic-ptg-april-2024 15:09:14 JayF: I think that was (or is) metalsmith legacy job, I've retested a patch to verify 15:09:17 we already have some pre-discussion happening 15:09:20 rpittau: thanks 15:09:26 rpittau: I am concerned it's a unit test issue 15:09:34 rpittau: so I'm not convinced that's the only bit, we'll see 15:09:34 yeah, I've left some comments today 15:09:34 oh ok, didn't spot that 15:10:51 #topic Bug Deputy 15:10:58 I was the bug deputy, but realistically in name only 15:11:06 I'm happy to take it another week and do two weeks worth of triage :) 15:11:21 Probably a valuable activity to take before release, anyway 15:11:46 #topic Open Discussion 15:11:51 We had an agenda item left 15:12:04 #info Please review BMC CA Cerfificate - ironic spec (https://docs.google.com/document/d/1Vxn-MrcXEnzeHaWvni4IE0WuQpR1QNWNC8EF65wXUho/edit) for RFE https://bugs.launchpad.net/ironic/+bug/2040236. Any comments are welcome. 15:12:14 My first feedback will be to push it to gerrit for further feedback :) 15:12:25 but I also intend on looking over it, in gdoc form and providing coarse feedback 15:12:38 Anything about this or anything else for open discussion? 15:12:59 wait, a google doc spec? 15:13:16 yeah, they wanted to have a preliminary discussion on that :) 15:13:39 I think we should communicate that it's about time for real discussions 15:13:43 Yeah, it was added to our agenda. It needs to be moved into gerrit but I am not going to hold that against them the first time around :) 15:13:45 I agree 15:14:41 Anything else for open discussion? 15:14:55 I will send it to gerrit, thanks 15:15:01 haoZhou: thanks for submitting it! 15:15:39 Last call for open discussion items 15:15:56 Okay, so my $0.02 feeling on that is the addition of the option itself, as long as it is a singular option is likely okay without a spec 15:16:17 I'm less and less a fan of driver specific field names unless absolutely necessary 15:16:25 I think JayF asked for the spec back in the RFE discussion days 15:16:55 TheJulia: well.. while a reasonable deployment should have the same CA for all BMCs, regardless of vendor, I can imagine a situation where some hardware simply cannot be updated 15:16:57 dunno 15:17:11 Or at least, it'd need to be aligned on something that is meant to reflect physical distance 15:17:14 like conductor group 15:17:16 Could be a PTG topic because for now we have all these [redfish]kernel_append_params and so on 15:17:40 yeah 15:17:50 "a different conductor group needs a different CI" aligns with a design where you have one Ironic orchestrating multiple, separately owned/operated computer rooms 15:17:58 s/CI/CA/ 15:18:45 This is probably a different concern. You probably will have a different ironic.conf per conductor group. 15:18:54 ooh 15:19:50 dtantsur: ++ 15:19:57 Either way, gerrit is a good place to have that discussion :) 15:20:04 right 15:20:11 Is there anything else or should I close it up? 15:20:54 #endmeeting