15:00:09 #startmeeting ironic 15:00:09 Meeting started Mon May 8 15:00:09 2023 UTC and is due to finish in 60 minutes. The chair is JayF. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:09 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:10 The meeting name has been set to 'ironic' 15:00:15 o/ 15:00:16 Who all is here this morning? 15:00:19 o/ 15:00:20 o/ 15:00:34 We have a very simple agenda so unless folks have something for open discussion I'm going to try and make it quick. 15:00:40 o/ 15:00:41 #topic announcements/reminder 15:00:51 #note 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:02 #note Please avoid running a `recheck` command bare, without any other comments. Obviously, best case is to troubleshoot and fix an issue in CI, but in case of some ephemeral failure, please just note that -- e.g. `recheck jobname failed`. This is tracked at an OpenStack level (https://etherpad.opendev.org/p/recheck-weekly-summary) and I've noticed more contributors doing 15:01:04 bare rechecks. 15:01:30 Although I recently confirmed those messages are not aggreggated, it can be useful for others coming to a patch later. 15:01:49 Those are the two announcements/reminders. 15:02:17 We had no action items last meeting; skipping agenda item. 15:02:28 #topic Review Ironic CI status 15:02:46 TheJulia: did you ever get that grenade-with-debug job to fail? 15:02:56 That's the only outstanding gate thing right now, yeah? Grenade? 15:03:13 yeah, trying to figure out if nova-api is just dying 15:03:18 the rbac job has been turned non-voting 15:03:31 I think we likely need to consider doing the same thing to grenade 15:03:40 le sigh, but yeah 15:03:54 Only for a short time :/ we have another grenade job (skip-level) to get running, too. 15:04:03 for SLURP 15:04:20 We likely need to reconsider nova being central to our upgrade testing 15:04:41 ... As well. 15:04:51 That sounds like a pretty brutal decision given we have a big nova-compute migration incoming 15:04:58 when sharding is complete 15:05:00 We have a bifrost upgrade job, but I wonder if the Nova-Ironic link is actually the weak point that we want to test 15:05:06 yep 15:05:30 well, the requirement has always been "however it is done", not mandating the tool precisely 15:05:47 unless slurp codified grenade 15:05:57 but without actual grenade maintenance, I can't see that as being reasonable 15:06:24 I'll put it this way 15:06:28 What is the maintenance work we need from grenade? 15:06:36 us running grenade is a convience upgrade test 15:06:44 you definitely cannot expect me to miss grenade :D 15:07:10 we trapped ourselves with devstack 15:07:50 The story I see developing, as told by our CI reliability, is that we have a good handle on testing standalone ironic, and a less-good one on testing ironic+nova, generally, with grenade being a pain point 15:08:17 It's hard for me to think it's grenade/devstack as a tooling problem versus actually implying functional issues without more data 15:08:22 Merged openstack/ironic master: Handle MissingAttributeError when using OOB inspections to fetch MACs https://review.opendev.org/c/openstack/ironic/+/880575 15:08:34 afaik grenade is basically as needed only, and locks us in to a nova-centric model. Maybe that is fine. dunno. 15:09:03 I don't see us as locked-in to a nova-centric model so much as, two basic columns of integration testing: Ironic "standalone" and openstack integrated 15:09:26 but either way, we need to make patches mergable and keep upgrades testable 15:09:36 we should keep down the path of identifying if the nova-api is dying 15:09:47 because if it is, hopefully we can get some help from those associated teams 15:09:49 that is what I'm doing 15:09:57 ++ that's what I thought just getting it into the meeting log 15:10:01 Going to move on 15:10:04 Well, among many things that we did right with bifrost, is this one: the production tool is easy to use for testing 15:10:05 the underlying issue is basically people are ignoring the issue or going "it is not my problem" 15:10:33 so... at some point, we're going to be completely blocked unless we can pin it down 15:10:33 TheJulia: I'd request if you're not getting good results in IRC, lets make an explicit request on the list so if there is indifference, it's more visible at a project level 15:10:51 ack 15:11:05 #topic Review ongoing 2023.2 workstreams 15:11:13 #link https://etherpad.opendev.org/p/IronicWorkstreams2023.2 15:11:20 if nova-api is dying will be a major data point, so time will tell 15:11:32 Please view and update workstream status. Thank you for putting the DPU information in there, I'll review those patches today 15:12:10 #topic Open Discussion 15:12:14 Anything for open discussion? 15:12:28 I'll note, Ironic cores please check your email and respond to the one I sent last week at some point :) 15:14:07 Sounds like nothing for open discussion; closing the meeting. Have a good week all o/ 15:14:09 #endmeeting