15:02:19 <TheJulia> #startmeeting ironic
15:02:19 <opendevmeet> Meeting started Mon Nov  3 15:02:19 2025 UTC and is due to finish in 60 minutes.  The chair is TheJulia. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:02:19 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:02:19 <opendevmeet> The meeting name has been set to 'ironic'
15:02:25 <TheJulia> Someone volunteer to chair :)
15:02:28 <dtantsur> o/
15:02:30 <dtantsur> thanks TheJulia!
15:02:36 * dtantsur not feeling all too great still
15:02:54 <rpittau> o/
15:03:03 <janders> o/
15:03:06 <TheJulia> #topic Announcements / Reminders
15:03:10 <TheJulia> dtantsur: :(
15:03:46 <TheJulia> Consider this reminder to review items tagged with ironic-week-prio, and furthermore apply the tag to any item which appears ready for reviews.
15:03:49 <TheJulia> #link https://tinyurl.com/ironic-weekly-prio-dash
15:04:11 <TheJulia> Also, a reminder the 2026.1 Gazpacho Release Schedule has been posted.
15:04:13 <TheJulia> #link https://releases.openstack.org/gazpacho/schedule.html
15:04:28 <cid> o/
15:04:37 <TheJulia> This week is week R-21 on the schedule.
15:04:58 <TheJulia> As a reminder, we structurally have a little less than two months left to the end of the year.
15:05:18 <dtantsur> Time flies!
15:05:18 <TheJulia> *Many* contributors will be taking PTO/Vacations at various times. Please be mindful and plan/set expectations ahead.
15:05:28 <dtantsur> I assume we'll need an intermedia release before NY?
15:05:36 <TheJulia> Yes
15:05:41 <TheJulia> We'll get there
15:06:11 <rpittau> I've created this patch that should help keeping in track with releasing our projects https://review.opendev.org/c/openstack/ironic/+/965090
15:06:36 <TheJulia> https://review.opendev.org/c/openstack/ironic-specs/+/965865/1/priorities/2026-1-workitems.rst presents a rough schedule.
15:07:12 <dtantsur> Huh, these don't match?
15:07:22 <rpittau> yeah they're not in conflict, my change is much more genric and can be applied to all release cycles
15:07:31 <dtantsur> rpittau's link says releasing at the first milestone, which is apparently R-20?
15:07:39 <dtantsur> TheJulia's says first week of Dec
15:07:48 <TheJulia> Lets get into it later
15:07:57 <dtantsur> sorry, please go on :)
15:07:58 <rpittau> we usually release between week 6 and 8 with a bugfix branch
15:08:18 <TheJulia> bottom line is we have broad schedules and more specific suggestion, coupled with a need to be realistic
15:08:33 <TheJulia> 6-8 is *way* too late
15:08:34 <TheJulia> fwiw
15:08:47 <TheJulia> around week 6, we should be prepared to cut our final release for the cycle.
15:08:55 <TheJulia> Lets get into it when we get there
15:09:08 <rpittau> 6 weeks after the beginning of the cycle ? I' mtalkgin about R-20
15:09:16 <rpittau> alright
15:09:38 <TheJulia> We have a working group updates section, and I think the thing to do there is to skip that for now. Once we have the areas highlighted via the prioriteis consensus, we can backfeed into that.
15:09:53 <TheJulia> In consideration of alegacy's time, do you have anything to really mention?
15:09:53 <dtantsur> I've just added the Async IO group to the list
15:10:00 <TheJulia> #topic Working Group Updates
15:10:30 <alegacy> Not really.  Testing is going well.  Really just in need of reviews
15:10:46 <TheJulia> cool cool, folks please review alegacy's work.
15:10:56 <TheJulia> Is there anything else this week for working group items?
15:10:59 <kubajj> o/
15:11:07 <dtantsur> Do they all have ironic-week-prio, alegacy?
15:11:52 <dtantsur> re Async WG, I'd like to have a boostrap call this or next week, wdyt? cid and whoever else is interested?
15:12:02 <alegacy> dtantsur: yes, I believe so... i'll double check now
15:12:11 <dtantsur> (if you're interested in async WG, add yourself to https://etherpad.opendev.org/p/ironic-asyncio)
15:12:19 <dtantsur> alegacy++
15:12:32 <cid> dtantsur, works for me either of the weeks.
15:12:49 <dtantsur> cool
15:13:02 <TheJulia> Since we don't have any discussion topis, bug deputy updates, or RFEs to review right now, it feels like the next stop for this meeting is Open Discussion, however we need to identify a bug deputy for the next week
15:13:30 <cid> alegacy, will make sure to review this week. Question, adding to the review queue means in merge-able state, but you mention some of them being tested :)
15:14:24 <cid> I can take the bug deputy task for this week, already been taking a look during the PTG
15:15:43 <TheJulia> cool cool
15:15:44 <cardoe> Folks can give some feedback on https://cardoe.com/neutron/evpn-vxlan-network/admin/data-center-networks.html which is where I'm trying to add a doc to neutron describing the VXLAN bits.
15:15:47 <TheJulia> Okay then, thanks cid!
15:15:51 <TheJulia> #topic Open Discussion
15:15:55 <cardoe> https://review.opendev.org/c/openstack/neutron/+/965415
15:16:01 <TheJulia> Clearly, we have a LOT to sift through this week.
15:16:06 <alegacy> cid: sorry, they are merge-able... by 'testing' i meant the testing I'm doing with this in a more integrated fashion with higher level software.
15:17:02 <cid> ack'd
15:18:15 <TheJulia> I guess at a simple CI level, maybe some additional scripting to do the needful in terms of a basic validation?! That might be feasible
15:20:03 <TheJulia> So clearly, we need to reach consensus on cycle plans. JayF has a WIP review up already for that which I encourage people to set bounds on and keep in mind we do have a time window during the next two months where some portion of contributors will disappear for at least a couple weeks.
15:20:56 <rpittau> #link https://review.opendev.org/c/openstack/ironic-specs/+/965865
15:21:56 <TheJulia> Any other items for discussion this week?
15:22:18 <janders> From my side, the top priority follow-up from the PTG I have is iRMC support/deprecation/removal. I am intending to reach out to iRMC/FJ folks early this week. Aiming to report back what I found out in next week's meeting
15:22:40 <TheJulia> janders: perfect, thank you!
15:23:23 <janders> no problem. A brief follow up question on this:
15:23:33 <TheJulia> Another item wort nothing, JayF did send an email to the mailing list regarding reviewer structure.
15:23:35 <TheJulia> #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/LUCBUPWZIRCANEHREHUPO7DZCPVJW4ML/
15:23:39 <TheJulia> I'm sure he would appreciate responses
15:23:50 <TheJulia> Also, does anyone feel interested in sending a PTG summary to the mailing list?
15:23:53 <kubajj> This is a wee bugfix of mostepha[m] , but it is blocking the progress on is_root_volume implementation: https://review.opendev.org/c/openstack/ironic-python-agent/+/965797
15:24:27 <janders> in my past comms with iRMC/FJ folks they indicated they need it in 2025.1, they seemed less concerned about what happens later
15:24:48 <janders> if we fasttrack deprecation/removal in master how does it affect still maintained branches?
15:25:13 <janders> I understand feature/bugfix workflow way better than deprecation/removal hence the question
15:25:38 <TheJulia> kubajj: eek, thats kind of a bad bug
15:26:10 <dtantsur> kubajj, mostepha[m], a release note won't hurt
15:26:20 <kubajj> TheJulia: it was also weird to debug, because we only hit it on one of our qa nodes
15:26:48 <TheJulia> Yeah, I think a release note is kind of key since we'll want to backport that
15:27:13 <TheJulia> janders: That may always change, but yeah, worth syncing up with them and letting us know
15:27:34 <kubajj> TheJulia, dtantsur: ok, will quickly add
15:27:41 <TheJulia> kubajj: thanks!
15:28:07 <TheJulia> janders: doesn't impact released branches.
15:28:31 <TheJulia> janders: but the reality is the snmp portions of the driver, which we've pushed back against in the past, need to minimally go away entirely.
15:29:24 <janders> TheJulia ack and thank you
15:29:45 <janders> I totally understand, I will start the discussion and report back
15:29:55 <TheJulia> janders: Concievably, if the snmp bits and dependency can be excised, that could be a bugfix
15:30:00 <TheJulia> thanks!
15:30:26 <TheJulia> but, because we also can't test or assure it, we're sort of forced to keep the dividing line at the whole of the driver
15:30:35 <janders> yeah
15:31:33 <TheJulia> Okay, anything else this morning?
15:31:39 <TheJulia> Do we have a PTG summary volunteer?
15:32:59 <JayF> TheJulia: I'd prefer we get work items landed and just send that as the summary
15:33:14 <JayF> Once we get that patch to a reasonable spot, I also plan on doing a video for gross YouTube
15:33:37 <TheJulia> PTGs are always 1-2 cycles worth of details and context, I'd prefer we draw a line or awareness since there is more there than we can execute upon as well.
15:34:17 <TheJulia> I guess ^^^ is where my concern with the current doc is, but it can be revised, I think the key aspect is for ironic contributors to review/comment *today*
15:35:32 <JayF> Yeah the doc is 100% in need of editing. I'm not by any means saying it's there.
15:35:41 <TheJulia> cool cool
15:35:45 <JayF> I may or may not have leaned on fancy new fake brain tooling to help build it 😂
15:35:53 <TheJulia> okay, anything else before we wrap this week's meeting then?
15:35:59 <TheJulia> lol
15:36:15 <TheJulia> I suspected that based upon one of the noted reasons which didn't add up
15:36:28 <TheJulia> (which is sort of weight there anyhow!)
15:38:29 <TheJulia> I'm taking silence as reason to call it a meeting.
15:38:32 <TheJulia> Thanks Folks!
15:38:37 <dtantsur> \o/
15:38:43 <janders> thank you all o/
15:38:45 * cardoe silences.
15:38:45 <TheJulia> Go review all the things!
15:38:57 <TheJulia> #endmeeting