15:03:00 <TheJulia> #startmeeting ironic
15:03:00 <opendevmeet> Meeting started Mon Jan 19 15:03:00 2026 UTC and is due to finish in 60 minutes.  The chair is TheJulia. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:03:00 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:03:00 <opendevmeet> The meeting name has been set to 'ironic'
15:03:04 <rpittau> o/
15:03:08 * TheJulia hands everyone coffeeeeee
15:03:09 <dtantsur> I think we need to get back to asking the question "who is chairing the meeting next time?" :)
15:03:10 <dtantsur> o/
15:03:11 <kubajj> o/
15:03:19 <TheJulia> dtantsur: ++ c oncur
15:03:49 <TheJulia> Greetings everyone, welcome to our weekly Ironic meeting. Our agenda can bef ound at https://wiki.openstack.org/wiki/Meetings/Ironic#Agenda_for_January_19.2C_2025
15:03:55 <cid> o/
15:05:48 <TheJulia> err, be found
15:05:51 <TheJulia> Clearly, I need more coffee
15:05:56 * TheJulia sips coffee and proceeed
15:05:58 <TheJulia> s
15:06:11 <TheJulia> #topic Announcements / Reminders
15:06:22 <TheJulia> As a standing reminder to review #ironic-week-prio items.
15:06:28 <TheJulia> #link https://tinyurl.com/ironic-weekly-prio-dash
15:06:41 <TheJulia> We have 30 items, lets get it below 25 this week.
15:06:47 <TheJulia> (preferably 20)
15:07:00 <cid> ++
15:07:17 <rpittau> if CI collaborates I think it's doable :)
15:07:24 <TheJulia> This is week R-10 on the release cycle.
15:07:26 <TheJulia> #link https://releases.openstack.org/gazpacho/schedule.html
15:07:51 <TheJulia> As a reminder, we should check the cycle priorities as well. If you get a chance this week, please take a quick glance at that list.
15:08:04 <TheJulia> Does anyone have anything else to remind us of or announce this week
15:08:08 <rpittau> yup, I'm planning a round of releases btw
15:08:37 <TheJulia> Does anyone have anything else?
15:09:52 <TheJulia> Onward
15:09:55 <TheJulia> #topic Working Group Updates
15:10:04 <cardoe> TheJulia: via msg? I’m driving home today
15:10:13 <TheJulia> First up standalone networking. alegacy you around today?
15:10:21 <TheJulia> cardoe: could work
15:11:23 <TheJulia> My impression is we're largely just in review phase for the standalone networking work.
15:11:44 <TheJulia> dtantsur: An update for Async IO ?
15:12:04 <dtantsur> Not much new on the async front. Still finishing the spec.
15:12:25 <dtantsur> (re standalone networking, I've left some comments on the first patch)
15:13:12 <TheJulia> okay then
15:14:19 <TheJulia> As for VXLAN networking, I think we're starting to make progress. I've gotten bit of a development test lab up and we have patches posted for networking-generic-switch to handle quite a bit of switch side configuration as it relates to the topic.
15:14:33 <TheJulia> The spec still needs reviews, but I think we're in a state of consensus at this point
15:14:42 <TheJulia> Does anyone else have anything working group related?
15:14:54 <cid> Not at the moment
15:15:56 <TheJulia> Since we have no defined discussion topics, lets go onward to the Bug Deputy Updates
15:16:02 <TheJulia> cid, the microphone is yours
15:16:15 <cid> Sure
15:16:20 <cid> There were a total of 6 new bugs, and 2 RFEs.
15:16:25 <cid> - Allow abort verb on DEPLOYWAIT
15:16:25 <cid> - Deferred Tasks - Have a way to centralize periodics and minimize sleep usage
15:16:32 <cid> I don't think these need reviews (?)
15:16:37 <TheJulia> The deploywait one, I think we already agreed to
15:16:51 <TheJulia> Deferred tasks is for the proposed spec document which I think I updated last week
15:17:15 <cid> Is it ready for reviews yet?
15:17:27 <TheJulia> Yes, it is up for review in ironic-specs
15:17:45 <cid> +++, cool cool
15:17:55 <TheJulia> is that 6 new bugs across all ironic projects?
15:18:22 <cid> Indeed, Bifrost, Ironic, Sushy, ...
15:18:27 <TheJulia> okay
15:18:37 <cid> 12th - 19th January, 2026
15:18:37 <cid> - https://bugs.launchpad.net/ironic/+bug/2138310 (in Progress, no review necesssary)
15:18:37 <cid> - https://bugs.launchpad.net/bifrost/+bug/2137376
15:18:37 <cid> - https://bugs.launchpad.net/sushy-tools/+bug/2137387
15:18:37 <cid> - https://bugs.launchpad.net/ironic/+bug/2137571
15:18:38 <cid> - https://bugs.launchpad.net/ironic/+bug/2138129
15:18:38 <cid> - https://bugs.launchpad.net/python-ironicclient/+bug/2138466
15:18:52 <cid> - https://bugs.launchpad.net/ironic-python-agent/+bug/2138540
15:18:52 <cid> - https://bugs.launchpad.net/ironic/+bug/2137571 (RFE but already approved, no review necessary)
15:18:52 <TheJulia> Impressive given launchpad was down for ?2? days last week
15:19:04 <cid> Oh, I didn't notice.
15:19:34 <TheJulia> There would be 7 or 8 if it had been up all week because cardoe hit the inspection issue and I think there was another thing patches got propsoed to just fix because we couldn't file a bug
15:19:37 <TheJulia> no worries :)
15:19:51 <TheJulia> Okay, So who whall be the deputy next week?
15:20:36 <cid> I'm always open to it, in the absence of any other interests. I wouldn't want to have all the fun :D
15:21:28 <TheJulia> We should really try to alternate it out
15:21:36 <TheJulia> but you do a really good job at it :)
15:22:08 <TheJulia> I'll give it a shot this week
15:22:20 <cid> tks!
15:22:38 <TheJulia> Since we have no RFE's requiring review this week, onward to Open Discussion
15:22:41 <TheJulia> #topic Open Discussion
15:22:53 <TheJulia> Does anyone have anything they would like to discuss
15:22:54 <TheJulia> ?
15:22:55 <janders> I have a couple topics
15:23:00 <TheJulia> janders: go ahead
15:23:17 <janders> first - I hit this in CI an hour ago, running recheck, hopefully will clear but giving everyone a heads-up:
15:23:20 <janders> | controller | fatal: unable to look up thekelleys.org.uk (port 9418) (Temporary failure in name resolution)
15:23:28 <janders> looks like DNS failure downloading DNS package :)
15:23:37 <janders> (same one dtantsur mentioned before the meeting)
15:23:43 <janders> no action required, unless we start seeing it more
15:23:55 <janders> it failed one of my patches in gate
15:23:59 <TheJulia> janders: btw, I did comment on the Redfish forum item we discussed briefly last week
15:24:20 <janders> TheJulia yeah, I saw it, ++
15:24:39 <janders> do you expect you'll be attending tomo? we can try raise this issue for another discussion
15:24:45 <abongale> cid: o/ I could take this one https://bugs.launchpad.net/python-ironicclient/+bug/2138466  and https://bugs.launchpad.net/ironic/+bug/2138129, it will be fun
15:25:23 <janders> prob best if we're both around for the discussiobn
15:25:23 <TheJulia> janders: I will try to join tomorrow. If you want to try and raise it on the agenda then I think it might make sense. The gap really needs to be bridged somehow
15:25:30 <janders> ++
15:25:36 <janders> thanks TheJulia
15:25:37 <TheJulia> And we're sort of in a unique position there
15:25:42 <janders> yeah
15:25:53 <janders> it feels we do have a valued voice; lets use it
15:25:59 <TheJulia> ++
15:26:00 <cid> abongale. That would be nice. o/
15:26:24 <janders> my second topic: I would appreciate reviews on https://review.opendev.org/c/openstack/ironic/+/971152/6 and https://review.opendev.org/c/openstack/ironic/+/971150/6 - last two patches in the big firmware upgrade chain
15:26:53 <janders> right now I am re-running CI on the initial, big patch but once that's good it would be great to tick this off
15:26:57 <janders> I marked them as weekly prio
15:27:07 <TheJulia> abongale: it might be breaking, but could make sense to change the pattern of behavior, if a field value is requested with json, to return the real field name
15:27:12 <janders> both have 1x +2
15:27:33 <kubajj> I also have two things
15:27:39 <kubajj> A question about the possibility of implementing a node evacuation feature - i.e. have a stand-by node, if a node goes down, a user could bring over the disks and start the node with the same parameters on the other node (would probably be mostly changes on nova)
15:27:46 <kubajj> My question regarding this  topic is - do yo u think this is even possible? Would anybody else want this?
15:28:38 <TheJulia> janders: I'll trade you if you review https://review.opendev.org/c/openstack/ironic/+/973560  and https://review.opendev.org/c/openstack/ironic/+/973413 :)
15:28:53 <TheJulia> (actually, I'll try to look at those this week)
15:29:10 <dtantsur> abongale, TheJulia, anything around https://bugs.launchpad.net/ironic/+bug/2138129 should really consider https://bugs.launchpad.net/ironic/+bug/2049913
15:29:30 <TheJulia> kubajj: oh wow. That could be a big discussion. Like user physically moves the platters?
15:29:36 <dtantsur> because it's essentially a different angle of the same discussion
15:30:02 <janders> kubajj would it be expected for the image to "just work" or is there assumption there'll be manual NIC/storage/... massaging?
15:30:03 <TheJulia> dtantsur: hmm, likely yes
15:30:06 <kubajj> TheJulia: yep, they operate mission critical nodes, like cryogenics, and stuff
15:30:25 <dtantsur> So very like an RFE that needs a spec
15:30:40 <TheJulia> Yeah, a spec most likely
15:30:41 <janders> kubajj first thing that came to mind is it's borderline touching baremetal snapshots
15:31:04 <TheJulia> The... big thing which comes to mind is NVRAM records and as previously mentioned network configuration
15:31:14 <janders> although I do get the difference
15:31:23 <kubajj> janders: we don't have those, right?
15:31:30 <TheJulia> we don't really have a good way to handle that
15:31:34 <janders> kubajj I don't believe so
15:32:01 <TheJulia> kubajj: we've talked about it, a lot over the years. (That being snapshots...) but the real issue is the complexity versues the variety of lower level interfaces
15:32:43 <TheJulia> I *do* think it would be relatively easy for us to have a means to move VIFs and ironic side configuration over
15:32:50 <kubajj> janders: yes, ideally, it would "just work" but a good starting point would be just something which would "kinda work"
15:33:05 <TheJulia> I think a spec would be a really good starting point to enumerate the requirements
15:33:08 <janders> kubajj 100% agreed
15:33:13 <kubajj> TheJulia: undestandable, it does sound complex
15:33:34 <kubajj> TheJulia: ok, we can try to come up with one
15:33:37 <TheJulia> its almost a "move x node's config to y node"
15:33:42 <janders> just throwing it out there: with devices in general, where I have mission critical stuff I just deploy more than I need to
15:33:43 <TheJulia> and then go move the disks in order
15:33:46 <kubajj> TheJulia: yep, exactly
15:34:00 <janders> so if some die, L1 can come and do something simple-enough to keep the lights on
15:34:06 <janders> since hard work has been done preemptively
15:34:13 <TheJulia> yeah
15:34:16 <janders> now I wonder how this maps into this concept
15:34:31 <janders> curious about any quick thoughts, otherwise happy to take this to the spec discussion
15:34:50 <janders> TLDR is - what if for some reason moving the disk isn't enough
15:34:58 <kubajj> janders: yeah, for some stuff, we do have LBs, but I do not know what exactly is the plan here, was just asked, if something like this is possible
15:35:15 <janders> kubajj makes sense
15:35:22 <janders> it's a clever idea TBH
15:35:35 <janders> lightweight cold spare
15:35:58 <janders> kinda
15:36:16 <kubajj> janders: afaik, this is just what they do now, we are just overtaking their mini-datacentre (~600 nodes) with Ironic and they want all procedures to work
15:36:48 <kubajj> we can explore other ways of handling this later
15:37:08 <TheJulia> So
15:37:09 <kubajj> I will discuss it with them and we can come up with a spec
15:37:14 <janders> it's hard to dispute some of those battle-learned-and-tested tricks from veteran ops folks
15:37:23 <TheJulia> One of the vendors did propose something like this as a value add years ago, but it was always using the backend SAN
15:37:47 <TheJulia> But yeah, move the disks and if it is setup for dhcp \o/
15:37:57 <TheJulia> Although, if you want to force network reconfiguration... that is a bit more work
15:38:17 <TheJulia> and could require the agent to going and nuking cloud-init and then metadata would need to be updated. Regardless, there is a very interesting idea here
15:38:31 <janders> ++
15:38:39 <janders> I wonder about BMC config implications
15:38:43 <janders> (network and other)
15:38:59 <kubajj> TheJulia: I think we do not need network reconfiguration yet (still didn't manage to convince our networking team to let us touch their switches)
15:39:05 <TheJulia> Well, you evacuate to another node, so the BMC would absolutely change
15:39:11 <TheJulia> just not the config for the BMC itself
15:39:23 <TheJulia> The way evacuate works is I think you functionally say "take this, put on this"
15:39:46 <kubajj> what would be interesting is if they had different bios settings, would complicate it even more 👀
15:39:48 <TheJulia> kubajj: well, I was more meaning workload side
15:40:03 <TheJulia> Yeah, the real question is what is the resolution of the configuration changes
15:40:23 <janders> btw none of my comments are to hint it's a bad, idea, im just thinking out loud about painpoints
15:40:45 <TheJulia> ditto
15:40:57 <TheJulia> Does anyone else have anything else to raise/discuss/plot?
15:41:07 <kubajj> janders: that's what I wanted to hear, if it was straightaway unimplementable, I would not want to start doing stuff :D
15:41:32 <kubajj> The second thing was that I wanted to thank mostepha[m] for his work upstream, he is heading back to university next week. It was great to have him around, especially for his work on the IPA
15:41:59 <TheJulia> Thank you mostepha[m]!
15:42:05 <cid> Thank you mostepha[m]
15:42:17 <janders> Thank you mostepha[m]!
15:43:22 <TheJulia> Anything else, anyone?
15:45:07 <TheJulia> #topic Who is going to run our next meeting?
15:45:13 <TheJulia> Would anyone like to volunteer?
15:46:59 <TheJulia> I guess I'll run the next meeting
15:47:10 <TheJulia> Okay folks, thanks everyone! Have a great week!
15:47:11 <TheJulia> #endmeeting