15:00:02 #startmeeting ironic 15:00:02 Meeting started Mon Mar 13 15:00:02 2023 UTC and is due to finish in 60 minutes. The chair is iurygregory. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:02 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:02 The meeting name has been set to 'ironic' 15:00:07 o/ 15:00:10 o/ 15:00:24 Hello ironicers, welcome to our weekly meeting! 15:00:26 o/ 15:00:56 you can find the agenda for our meeting in the wiki 15:00:59 #link https://wiki.openstack.org/wiki/Meetings/Ironic#Agenda_for_next_meeting 15:01:51 #topic Announcements / Reminder 15:02:11 #info All ironic projects already have stable/2023.1(antelope), master is tracking 2023.2 (bobcat) 15:02:36 #info The Antelope coordinated release will happen on Wednesday, 22 March, 2023. 15:03:07 o/ 15:03:23 Thank you all contributors! 15:03:40 #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:04:05 #topic Review action items from previous meeting 15:04:43 #info We had one action item "JayF To look into VMT for Ironic", considering done since he did 15:05:08 #topic Review Ironic CI status & update whiteboard if needed 15:05:41 Does anyone have something to say about our current CI status? something we need to keep an eye, etc 15:07:30 ok, moving on 15:07:34 #info The experimental metal3 job has merged 15:07:48 oh right, good catch dtantsur =) 15:08:09 thanks dtantsur and rpittau for the work on it 15:08:37 #topic VirtualPDU 15:08:49 #info VirtualPDU repo rename from x/virtualpdu -> openstack/virtualpdu is tentatively scheduled for April 7 15:09:10 #topic Ironic Bobcat vPTG 15:09:21 Is there a schedule yet? 15:09:22 o/ 15:09:26 o/ 15:09:29 #info Scheduling - please review and respond to the scheduling message on the list. 15:09:33 #link https://lists.openstack.org/pipermail/openstack-discuss/2023-March/032641.html 15:09:37 TheJulia, ^ 15:09:39 Thanks 15:09:43 * TheJulia had not seen that yet 15:10:23 everyone, please try to read JayF email above in openstack-discuss about the schedule for the bobcat PTG 15:10:59 #info Participate in the planning etherpad 15:11:06 #link https://etherpad.opendev.org/p/ironic-bobcat-ptg 15:12:52 #topic Ironic Vulnerability management 15:13:19 JayF started a ML thread few weeks ago 15:13:35 #link https://lists.openstack.org/pipermail/openstack-discuss/2023-March/032658.html 15:14:43 if no objections are raised in the ML or during our meeting, we will apply ironic to be VMT-managed 15:14:52 o/ (late) 15:15:06 feel free to let us know here on irc or in the ML =) 15:17:02 ok, next topic in our agenda is from dtantsur 15:17:06 #topic Hosting full IPA images on tarballs.opendev.org 15:17:12 * dtantsur wonders if we have quorum 15:17:15 anyway 15:17:38 As you might have heard, the TripleO team is wrapping up its development 15:18:02 metal3 is currently relying on images built by RDO, tested in the TripleO CI and published, again, on the RDO resources 15:18:36 the 2nd part of this chain is gone, there probably will be some sort of a replacement, but I wonder if metal3 (being an upstream FOSS project) should consume the IPA images we publish 15:18:45 (yeah, I missed IPA in the explanation) 15:19:07 the problem: metal3 relies on the extra-hardware element (and having multipath-io probably won't hurt either) 15:19:10 I suspect there may not be pure midstream like there is today, and recommend that as an upstream community, metal3 consume images from another upstream project. 15:19:22 right 15:19:38 The current CS9 image is 390M, adding extra-hardware will bring it to 410M 15:19:50 not horrible in the slightest 15:20:20 The default is RDO images right now, which I believe would be larger? 15:20:27 roughly the same, it seems 15:20:30 it's smaller than older images we have there 15:20:32 oh, okay 15:21:16 in theory, since RDO supports Ironic, it should publish some IPA images 15:21:27 but that's my understanding, I don't know what RDO people think 15:21:35 that's probably not the biggest of their current headaches 15:21:54 we can talk with rdo folks to see what they think 15:22:05 I did, they don't know 100% yet 15:22:24 oh ok 15:22:51 Another approach would be to see if we can rid metal3 of dependency on extra-hardware 15:23:01 Yeah, RDO as a project has been modeleda round TripleO, there will still be a packaging need, but not quite like what exists today, so the form and shape given pre-existing usage will still shape and influence things moving forward 15:23:04 then it can use the images we publish today 15:23:32 what does it use extra-hardware for anyway? 15:23:35 could it be optional? 15:24:52 Firmware information (versions) and NIC speeds 15:25:11 If these are easy to get, maybe we should add them to the IPA inventory.. 15:25:42 TheJulia: check what uses "Extra" in https://github.com/metal3-io/baremetal-operator/blob/main/pkg/provisioner/ironic/hardwaredetails/hardwaredetails.go 15:28:28 I could see some of that being rather useful 15:29:01 Okay, so I have some more homework to do :) Thanks all! 15:29:32 I may end up extending IPA indeed. Or come back with the same proposal :) 15:29:43 thanks dtantsur 15:29:55 #topic Open discussion 15:30:32 anything else we should discuss today? 15:30:57 coffee. Lots of coffeeeeeee 15:31:13 coffee++ 15:31:25 Thanks everyone! See you next week! 15:31:28 #endmeeting