15:01:24 <JayF> #startmeeting ironic
15:01:24 <opendevmeet> Meeting started Mon Aug  7 15:01:24 2023 UTC and is due to finish in 60 minutes.  The chair is JayF. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:01:24 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:01:24 <opendevmeet> The meeting name has been set to 'ironic'
15:01:27 <rpittau> o/
15:01:28 <TheJulia> o/
15:01:29 <JayF> TheJulia: I was actually starting a pot :)
15:01:29 <iurygregory> o/
15:01:34 <kubajj> o/
15:01:34 <masghar> o/
15:01:39 <rpittau> that was fun :)
15:01:45 <TheJulia> JayF: hopefully enough to share with the channel! :)
15:01:58 <JayF> I'm more thinking lets all be on top of it
15:02:04 <JayF> so when it's done I can have a cup without rushing away ;)
15:02:08 <JayF> #topic Announcements/Reminder
15:02:20 <JayF> Standing reminder: tag your patches #ironic-week-prio, review things using the priority dashboard
15:02:33 <JayF> bonus add for today: the reverse is true; if your patch is no longer ready for review, just drop the tag until it is again
15:02:48 <JayF> so that our dashboard is a clean way to know what things need attn
15:03:09 <JayF> Next event on our schedule in the agenda is the Bobcat Non-client library freeze coming up 8/24
15:03:23 <JayF> please ensure your sushy changes and other library code is landed well before then for Bobcat release
15:03:28 <JayF> Moving on
15:03:43 <JayF> There were no action items last meeting; skipping agenda item.
15:03:52 <JayF> #topic Review Ironic CI Status
15:04:11 <JayF> So I know rpittau had an item here; bifrost is broken by centos stream, it seems?
15:04:15 <rpittau> yep
15:04:26 <rpittau> the BZ to fix that is ON_QA hence the question
15:04:35 <JayF> I don't know what that means
15:04:38 <rpittau> the package is ready, just need to be approved
15:04:42 <rpittau> and it will be published
15:05:00 <rpittau> once it's published there's no need for the workaround
15:05:03 <JayF> This only impacts bifrost CI, yeah?
15:05:08 <rpittau> correct
15:05:28 <JayF> My $.02 is to keep the workaround in your pocket, but AFAICT we don't have much pressing bifrost stuff
15:05:37 <JayF> so I'd lean slightly towards waiting for the fix
15:05:41 <JayF> but that's a mild preference
15:06:00 <TheJulia> Is it blocking the ironic gate at all, or has this apparent workaround kept us moving forward?
15:06:02 <rpittau> the workaround is on hold
15:06:25 <JayF> TheJulia: I think we only test CentOS Stream in Bifrost gate; that's what I was trying to ask earlier
15:06:33 <rpittau> TheJulia: bifrost ci is broken up to zed at the moment
15:06:48 <rpittau> the other projects look good so far
15:07:00 <rpittau> it's because we only have cs9 nodes in bifrost
15:07:10 <JayF> I'
15:07:22 <JayF> **I'll note that I think the virt side of the stack had to land a similar workaround
15:07:24 <JayF> at a devstack level
15:07:27 <TheJulia> looks like all the bifrost jobs on the ironic gate are non-voting, 2 of 3 work
15:07:35 <rpittau> well yeah, technically the issue is on devstack
15:08:15 <TheJulia> regardless, seems like we're good to move on then?
15:08:23 <rpittau> I haven't seen any impact in other projects besides bifrost
15:08:50 <JayF> yeah I'd say fix it if we get something pressing on bifrost
15:08:54 <JayF> otherwise let it sit
15:09:04 <rpittau> yep, agred
15:09:15 <JayF> Is there any other notable things going on with CI? Aside from bifrost; I think we're as happy as we've been in a while
15:09:24 <rpittau> nothing else AFAICS
15:10:13 <JayF> Moving on
15:10:22 <JayF> #topic Review Ongoing 2023.2 Workstreams
15:10:42 <JayF> I'll note, generally, we're reaching the homestretch of the release; things we want to land need to get up for review quickly so we can make sure they hit
15:10:47 <JayF> we've already had a super productive cycle though
15:11:33 <JayF> #link https://etherpad.opendev.org/p/IronicWorkstreams2023.2
15:12:02 <JayF> Giving another minute for comments on in-progress items
15:12:55 <kubajj> should I include the improving of config if I don't know if I'll complete it before the freeze?
15:13:17 <JayF> kubajj: first of all, lets try to get it in this cycle :) the freeze you have to worry about for that is 8/31-ish
15:13:21 <JayF> so you have weeks to complete that
15:13:29 <kubajj> oh, okay
15:13:34 <JayF> somewhere between 8/31 and 10/4 we have to have our final release cut
15:13:44 <JayF> 8/31 is when the other projects will stop taking major changes
15:14:10 <JayF> #topic OpenStack User Survey Updates
15:14:47 <JayF> I added this item to the agenda because here
15:14:49 <JayF> #link https://lists.openstack.org/pipermail/openstack-discuss/2023-July/034589.html
15:15:01 <JayF> Projects were asked to come up with any project-specific questions for the survey
15:15:06 <JayF> Ironic has none, currentyl
15:15:34 <JayF> We probably should? But I'm not sure what exactly, so I made this item to 1) increase awareness and see if anyone was interested in drafting questions and 2) give folks a chance to have input before I just go add something if nobody else has interest
15:16:16 <TheJulia> does anyone remember our ideas from last year
15:16:24 <iurygregory> I thought we had questions in the survey lol
15:16:25 <TheJulia> the ones that came up after we would have had to send them in?
15:16:54 <JayF> I don't even recall this at all last cycle tbh
15:17:09 <JayF> and if we have questions in the survey, they are missing from the google doc linked there
15:17:16 <JayF> or, always possible; I just missed it :D
15:17:16 <TheJulia> well, it would have been last june/july
15:19:13 <JayF> I created
15:19:15 <JayF> #link https://etherpad.opendev.org/p/ironic-user-survey-questions-2023
15:19:25 <JayF> We can use that to coordinate; I'll make sure to get something to them by EOW either way
15:19:45 <iurygregory> ++
15:19:55 <JayF> #topic Open Discussion
15:19:59 <JayF> floor is open for any other items
15:20:14 <opendevreview> Julia Kreger proposed openstack/ironic master: Support sha256/sha512 with the ilo firmware upgrade logic  https://review.opendev.org/c/openstack/ironic/+/882164
15:21:41 <JayF> Last call?
15:22:35 <TheJulia> regarding service steps
15:23:03 <TheJulia> I've not had time recently to work on it too much, but I'm wondering if it would be one of those "lets just merge it with imperfect testing" and sort it out next cycle sort of things
15:23:30 <JayF> I think we should make sure it lands this cycle; but can we be explicit about what further testing we want to make on it?
15:24:08 <TheJulia> some unit testing + tempest, but the through unit tests work just fine
15:24:27 <JayF> I'm not terribly worried about it not getting a temptest test, frankly
15:24:36 <TheJulia> so decent confidence, just there may be a obvious missing piece somewhere hwich we could just treat as a bug later
15:24:47 <JayF> with that context, I wouldn't hold it up
15:24:53 <TheJulia> okay, cool
15:24:53 <JayF> as long as it works when manually tested
15:25:04 <TheJulia> I'll try to polish it and get a client patch up this week
15:26:41 <JayF> awesome
15:26:47 <JayF> That's exciting, if you need specific help please ask
15:26:52 <JayF> I'm invested in being sure that lands in bobcat
15:27:10 <JayF> Anything else for open discussion?
15:27:21 <TheJulia> JayF: a client patch would always be appreciated :)
15:27:59 <JayF> lets land the API side then :D
15:28:20 <TheJulia> okay then!
15:28:23 <TheJulia> :)
15:28:39 <TheJulia> I have two things to follow-up on and I can shift gears to taht
15:29:18 <JayF> the other item that one or both of us owe
15:29:25 <JayF> is I think johnthetubaguy wanted us to test sharding
15:29:34 <JayF> and we know Nova will be strict about that B-3 deadline
15:29:45 <JayF> and if client for service steps is a fast follow that's not that bad
15:29:59 <JayF> so I think I might focus on getting my nova-set-lessee patch tested, and then sharding tested, so that can get in
15:30:09 * JayF finally wrangled a devstack late last week
15:30:56 <TheJulia> I'm not sure we have anything there that would be needed/blocking for that on our side
15:31:08 <TheJulia> at least, that I'm conciously aware of, if we do, we should put it on the etherpad
15:31:24 <TheJulia> otherwise it will just get lost in my short term recall
15:31:48 <JayF> I'm saying I think John-the-person wanted us to sanity check the changes
15:31:50 <JayF> and test in devstack
15:31:59 <TheJulia> ahh, ok
15:32:04 <TheJulia> reasonable
15:32:07 <JayF> not that there's some pending technical action so much as one or both of us expressing confidence in the changes
15:32:27 <JayF> I have a devstack up and plans this week to use it to test that and my nova-set-lessee change
15:32:51 <JayF> Either way, lots of stuff to do :) hopefully can keep pointed in a direction and doing good stuff
15:33:02 <JayF> for now I think the meeting is mostly petered out though, I'm going to close it?
15:33:23 <TheJulia> sounds good to me
15:33:55 <JayF> #endmeeting