opendevreview | Iury Gregory Melo Ferreira proposed openstack/ironic master: Move BFV job to non-voting https://review.opendev.org/c/openstack/ironic/+/903267 | 01:09 |
---|---|---|
iurygregory | JayF, dtantsur, rpittau ^ we probably need to disable till we can figure out the reason (I think is probably something related to the changes Jay mentioned, since on Thursday everything was ok) | 01:12 |
JayF | iurygregory: I am -0 to that move; I'd instead prefer us move quickly to identify+revert the breaking change on the nova side, right now master state is broken which is not awesome. This will be a big focus for me tomorrow. | 02:34 |
opendevreview | paresh proposed openstack/ironic master: Fixes Raid creation in iLO6 and other BMC with latest schema https://review.opendev.org/c/openstack/ironic/+/902744 | 07:40 |
opendevreview | paresh proposed openstack/ironic master: Fixes Raid creation in iLO6 and other BMC with latest schema https://review.opendev.org/c/openstack/ironic/+/902744 | 07:46 |
rpittau | good morning ironic! o/ | 07:50 |
opendevreview | Vasyl Saienko proposed openstack/networking-baremetal master: Do not try to bind port when we can't https://review.opendev.org/c/openstack/networking-baremetal/+/903252 | 08:00 |
rpittau | JayF, TheJulia, dtantsur, iurygregory: I see some changes in nova between December 7 and 8 that may have caused the bfv issue, all involving migration to openstacksdk, chain starts here https://review.opendev.org/c/openstack/nova/+/659691 | 08:02 |
dtantsur | JayF: I don't agree with this take. If the regression was in our project, we could say that fixing it quickly is preferred. But we cannot wait for the turnaround on the nova side. | 09:49 |
dtantsur | Especially with https://review.opendev.org/c/openstack/ironic/+/903185 hanging in limbo breaking unclear number of redfish deployments | 09:54 |
dtantsur | JayF: https://review.opendev.org/c/openstack/nova/+/903324 | 10:05 |
dtantsur | let's see what gets merged first, I'll throw a testing patch in | 10:05 |
opendevreview | Dmitry Tantsur proposed openstack/ironic master: [DNM] Test the BFV job fix https://review.opendev.org/c/openstack/ironic/+/903325 | 10:07 |
dtantsur | rpittau, iurygregory ^^^ | 10:08 |
dtantsur | meanwhile, | 10:13 |
dtantsur | TheJulia: do you know if https://docs.nvidia.com/networking/display/bluefield2dpuenug/supported+interfaces#src-37852583_SupportedInterfaces-NC-SIManagementInterface means that they also rely on NC-SI? Or is it just an option? | 10:13 |
opendevreview | Dmitry Tantsur proposed openstack/bifrost master: Switch IPA building to Debian Bookworm https://review.opendev.org/c/openstack/bifrost/+/903162 | 10:40 |
jrosser | dtantsur: that connector is to allow the host system BMC to share the physical port on the DPU | 10:55 |
dtantsur | jrosser: yep, but is it mandatory? | 10:56 |
jrosser | well that entirely depends | 10:56 |
dtantsur | or do you expect the most people to have a separate BMC NIC? | 10:56 |
jrosser | if you manage the host through a dedicated OOB port, or it shares an existing onboard port and the use case is OK with that, then so be it | 10:57 |
jrosser | but if the use case mandates that host OOB is presented on the DPU physical port then it would be mandatory | 10:57 |
dtantsur | The background of my question is: we know that some NC-SI implementation have problems with Ironic because such nodes cannot be powered off (you lose your BMC access) | 10:58 |
jrosser | not all motherboards present the other end of that connector either | 10:58 |
jrosser | tbh that does not surprise me | 10:58 |
dtantsur | So, if we're going to see more such hardware, it's a reason for us to raise the priority of fixing NC-SI support. | 11:00 |
jrosser | i have bluefields and don't use the NCSI connector, so in that sense it's not mandatory | 11:00 |
dtantsur | aha. good to know, thanks! | 11:01 |
jrosser | but in other situations i have other NIC which absolutely have to use NCSI, and it has been difficult | 11:01 |
dtantsur | I see | 11:01 |
jrosser | relatedly we have some newer hosts where the ncsi is wired to an OCP slot rather than being presented as a ribbon cable connector, so you have no choice but to select an OCP NIC if you want to use it | 11:05 |
jrosser | dtantsur: one issue we did have with ncsi in general was wildly different performance between nic vendors | 11:07 |
opendevreview | Verification of a change to openstack/ironic-python-agent master failed: Fix referencing to the raid_device var which is not set https://review.opendev.org/c/openstack/ironic-python-agent/+/900324 | 11:07 |
jrosser | on one vendor you could straightforwardly boot from virtual media over it, on another vendor the performance was so incredibly slow that uploading the virtual media to the BMC was essentially impossible | 11:09 |
dtantsur | fun times | 11:17 |
iurygregory | good morning Ironic | 11:22 |
opendevreview | Dmitry Tantsur proposed openstack/sushy-tools master: Expose VirtualMedia on Systems in addition to Managers https://review.opendev.org/c/openstack/sushy-tools/+/903331 | 11:48 |
opendevreview | Vasyl Saienko proposed openstack/networking-baremetal master: Do not try to bind port when we can't https://review.opendev.org/c/openstack/networking-baremetal/+/903252 | 12:39 |
opendevreview | Dmitry Tantsur proposed openstack/sushy-tools master: Expose VirtualMedia on Systems in addition to Managers https://review.opendev.org/c/openstack/sushy-tools/+/903331 | 12:44 |
iurygregory | FYI: today I won't be able to join the upstream meeting | 13:07 |
TheJulia | good morning | 13:38 |
n0ob | good afternoon | 13:40 |
JayF | dtantsur: the redfish breakage needing to land is a good point | 15:00 |
JayF | dtantsur: ty for the fix after looking yesterday I suspected the shape would be something like that | 15:01 |
JayF | no idea how this ever passed our CI in the first place though | 15:01 |
JayF | #startmeeting ironic | 15:01 |
opendevmeet | Meeting started Mon Dec 11 15:01:29 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 |
opendevmeet | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 15:01 |
opendevmeet | The meeting name has been set to 'ironic' | 15:01 |
JayF | #topic Announcements/Reminder | 15:01 |
JayF | #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:01 |
TheJulia | o/ | 15:03 |
TheJulia | dtantsur: w/r/t ncsi, just an option afaik | 15:03 |
JayF | No action items from last week, skipping that one | 15:03 |
JayF | #topic Caracal release schedule | 15:03 |
JayF | #info Next milestone C-2, Jan 11 | 15:03 |
JayF | #topic Meeting schedule for holiday | 15:03 |
JayF | I propose we cancel the 12/25 and 1/1 meetings. Well, I propose I won't be here, you all can do what you want with Christmas + New Years Day :D | 15:04 |
JayF | If I don't hear an objection going to move ahead with that plan | 15:05 |
rpittau | o/ | 15:05 |
JayF | #action JayF to email mailing list about Christmas + New Year's Day meetings being cancelled | 15:06 |
JayF | #topic Review Ironic CI Status | 15:06 |
JayF | So Ironic CI is currently busted, BFV job was broken by some Ironic driver changes that landed | 15:06 |
dtantsur | The bfv fix hasn't merged yet.. | 15:06 |
JayF | the fix is in the nova gate, if it gets clogged up we can push a quick -nv to get things free | 15:07 |
JayF | I'm a bit confused how this landed broken, I had a patch w/Depends-On on the tip that passed all our jobs | 15:07 |
opendevreview | Verification of a change to openstack/ironic-python-agent master failed: Fix referencing to the raid_device var which is not set https://review.opendev.org/c/openstack/ironic-python-agent/+/900324 | 15:07 |
TheJulia | I don't know what patches in question, but it looked like it was lacking a key we expected to be present | 15:08 |
TheJulia | possibly a race condition?! | 15:08 |
JayF | Well, there was a comment on the original change that it could be racey, but with dtantsur's fix, it doesn't look like it could've ever worked | 15:08 |
JayF | so I'm thinking maybe a follow up just to ensure our jobs are running nova from git | 15:08 |
JayF | well, we know it is, because they broken | 15:09 |
JayF | Either way, we know the path forward, path behind matters less, not like we push major changes to Ironic<>Nova driver often. | 15:09 |
JayF | Anything else on CI/Nova breakage? | 15:09 |
dtantsur | We cannot run nova NOT from git | 15:10 |
JayF | fair | 15:11 |
JayF | moving on | 15:11 |
JayF | #topic Bug Deputy | 15:11 |
JayF | I was the bug deputy. I triaged some bugs. I did not put together a report. | 15:11 |
JayF | I'll note for whoever is taking it next (I can go another week if needed), there's something mildly screwy with the dashboard | 15:11 |
JayF | I didn't have time to look, but either launchpad API returns bad data or something in our bug deduplication breaks on non-Ironic projects | 15:11 |
JayF | but I managed to triage most new bugs | 15:12 |
rpittau | I can go for it this week | 15:12 |
JayF | #action rpittau to be bug deputy this week | 15:12 |
JayF | well, I say I didn't have time to look; I looked; I didn't solve lol | 15:12 |
rpittau | :D | 15:12 |
JayF | We have lots of RFEs up | 15:13 |
JayF | including some I proxied as bug deputy | 15:13 |
JayF | #topic RFE Review | 15:13 |
JayF | dtantsur: has three, going to link them in and let you talk about them | 15:13 |
JayF | #link https://bugs.launchpad.net/ironic/+bug/2045548 | 15:13 |
JayF | #link https://bugs.launchpad.net/ironic/+bug/2045551 | 15:13 |
JayF | both carryovers from last week, we didn't have many folks in the meeting and wanted more people to see these | 15:13 |
JayF | they were provisionally approved | 15:13 |
dtantsur | Yeah, thanks! | 15:13 |
JayF | #link https://bugs.launchpad.net/sushy-tools/+bug/2046153 "Testing the minimal subset of Redfish features" is the new one for dtantsur | 15:14 |
TheJulia | no objection to 2045548, only concern about the kernel command line length limit | 15:14 |
dtantsur | TheJulia: do you remember the limit from the top of your head? | 15:14 |
TheJulia | 1024 chars | 15:14 |
TheJulia | total | 15:14 |
dtantsur | I think we're quite good still | 15:14 |
TheJulia | yeah, maybe move it to the end *just in case* | 15:15 |
TheJulia | I think the kernel truncates it, if memory serves it is also configurable and at one point was 256 charts | 15:15 |
TheJulia | chars | 15:15 |
dtantsur | I'll how doable that is (without relying on Python dict ordering) | 15:15 |
TheJulia | I was thinking template wise | 15:15 |
TheJulia | fwiw | 15:16 |
dtantsur | I think all these arguments end up in a dict.. anyway, technical details | 15:16 |
TheJulia | they do, but the actual line draws from several different fields in the tempalate, the actual consumption side, yes hits dict and entires may be truncated | 15:16 |
JayF | how long until ipa-b64-config=dgjskljdfhgksljdhg | 15:16 |
dtantsur | lol | 15:17 |
JayF | I'm only half-joking, we're getting more complex in the preboot configuration we need | 15:17 |
dtantsur | with virtual media, we should start embedding it as a file already (we actually have all the code there) | 15:17 |
JayF | that is worthy of being written up | 15:17 |
* JayF notes he is +1 to all the proposed RFEs | 15:17 | |
dtantsur | I'll try to.. but I cannot do everything at once | 15:18 |
TheJulia | The second rfe, I guess I'm trying to understand why we feel the need to create the second script/why we feel it is explicitly needed. I.e. is there a path not to have it, and do we need more, or less complexity to get there | 15:18 |
TheJulia | everything at once is impossible | 15:18 |
dtantsur | 2045551 is a bit more interesting. It's continuation of the whole "self-configuring ironic" thing | 15:18 |
dtantsur | to be clear: this script exists now, it's just normally hand-written | 15:18 |
dtantsur | we *could* roll this logic into boot.ipxe, but then we won't be able to reuse the ipxe_script_template | 15:19 |
dtantsur | like, I don't want https://github.com/metal3-io/ironic-image/blob/main/ironic-config/inspector.ipxe.j2 to be handwritten any more | 15:19 |
TheJulia | I'm personally pro all together, if possible | 15:19 |
dtantsur | Not sure I know what you mean | 15:20 |
TheJulia | from my pov, there is no technical reason why we've kept that pattern, out of "this is the way we always did it" | 15:21 |
TheJulia | and we should evolve that. What that looks like exactly, more so depends on the overall requirements | 15:21 |
dtantsur | it falls the loop <MAC1>, <MAC2>, ..., fallback | 15:21 |
dtantsur | where do you suggest it goes, https://opendev.org/openstack/ironic/src/branch/master/ironic/drivers/modules/boot.ipxe ? | 15:21 |
TheJulia | yes, except what did we do in bifrost? | 15:21 |
dtantsur | same as in metal3: a separate file | 15:22 |
dtantsur | it's also the approach we document for ironic-inspector | 15:22 |
TheJulia | we could take boot_failed path | 15:22 |
TheJulia | oh, so bifrost got changed way from the single file ? | 15:22 |
dtantsur | if we add that to boot.ipxe, then the operators who customize boot.ipxe and ipxe_config.template will need to change their templates | 15:22 |
TheJulia | yes | 15:22 |
dtantsur | bifrost has always worked like that | 15:22 |
TheJulia | that is unavailable | 15:22 |
dtantsur | nothing I touched implemented inspection as part of boot.ipxe | 15:23 |
dtantsur | (I don't think TripleO either) | 15:23 |
TheJulia | maybe bifrost for the past five years, but a very long time ago it was a single file | 15:23 |
dtantsur | possibly? if so, it's long gone | 15:23 |
TheJulia | yeah | 15:23 |
dtantsur | I'm not sure why we'd ask people to duplicate their templates though | 15:23 |
TheJulia | it worked quite nicely, from my point of view, but that was a long time ago | 15:23 |
TheJulia | nor am I | 15:23 |
dtantsur | (not my pain any more since we don't customize ipxe_config.template, but still) | 15:23 |
TheJulia | other than hardware discovery | 15:24 |
dtantsur | I'm afraid your memory misleads you | 15:24 |
dtantsur | https://opendev.org/openstack/bifrost/commit/c1f9beac6358efd70a4197f57f71ef98499fa7d6 is your patch that introduced inspector support, and it uses the separate file | 15:25 |
TheJulia | sweet! | 15:25 |
dtantsur | The value I see in the separate file is to reuse ipxe_config.template out of box | 15:25 |
* TheJulia shrugs | 15:26 | |
dtantsur | so, people who customized something for cleaning, deployment and managed inspection will get the same thing for the unmanaged inspection | 15:26 |
dtantsur | I'm worried about managed and unmanaged inspection ever diverging | 15:26 |
TheJulia | yeah, I just worry how much debt we're carrying for that and if we should make it more streamlined, or not | 15:26 |
JayF | I need to step away for a minute; if you all get done with this next up are those two sushy-tools RFEs which I'm +1 with very low context on (I put them on the agenda from seeing them in triage) | 15:27 |
JayF | #chair TheJulia dtantsur | 15:27 |
opendevmeet | Current chairs: JayF TheJulia dtantsur | 15:27 |
TheJulia | I guess i always thought we were going to try and drift everything towards managed | 15:27 |
TheJulia | anyway, we should carry on | 15:27 |
dtantsur | We will try, but we don't succeed right away | 15:27 |
TheJulia | naturally :) | 15:27 |
dtantsur | People want auto-discovery all the time... | 15:27 |
TheJulia | true | 15:27 |
TheJulia | and we have to still soft of have that as a path, but that doesn't mean things can't evolve | 15:27 |
TheJulia | Onward? | 15:28 |
dtantsur | Mmmm, so no consensus? | 15:28 |
TheJulia | dtantsur: lazy consensus? | 15:28 |
dtantsur | I thought you were against the RFE as it's written? | 15:28 |
TheJulia | eh, not a fan, but doesn't mean I'm going to take a hardline stance on it | 15:29 |
TheJulia | I'm more asking question for the big picture | 15:29 |
TheJulia | #link https://bugs.launchpad.net/sushy-tools/+bug/2045906 | 15:29 |
TheJulia | #link https://bugs.launchpad.net/sushy-tools/+bug/2045908 | 15:29 |
dtantsur | I don't have anything against extending sushy-tools as long as we have some understanding why people are doing it | 15:30 |
dtantsur | i.e. they're not doing it in production | 15:30 |
TheJulia | ++ | 15:30 |
TheJulia | The first one, seems like a "non-issue"/"just do it" | 15:30 |
JayF | I think these are the folks who came by here the other day | 15:30 |
JayF | someone dropped in and asked if we'd be OK with getting features into sushy-tools | 15:30 |
dtantsur | yeah, SKU,Serial are not even RFE-worthy | 15:30 |
JayF | and I gave them the usual interrogation; sounds like they are building a product in the category of Ironic | 15:30 |
JayF | and want to enhance the testing suite in sushy-tools more | 15:31 |
TheJulia | the latter one, yeah, I'm trying to understand why | 15:31 |
dtantsur | if it's for testing their product - no problem | 15:31 |
dtantsur | as long as it does not end up putting more burden on us | 15:31 |
JayF | TheJulia: I could easily see a datacenter management product monitoring power usage, especially if it's oriented differently than OpenStack | 15:31 |
JayF | dtantsur: if anything, getting another project depending on sushy{,-tools} may reduce our overall burden | 15:32 |
TheJulia | JayF: of course, which I think kind of goes to dtantsur's comment | 15:32 |
dtantsur | by the way, we should rename sushy-tools | 15:32 |
dtantsur | it causes too much confusion with sushy proper | 15:32 |
TheJulia | ++++ | 15:32 |
* dtantsur has recently learned there is an alternative to sushy-tools called ksushy | 15:32 | |
TheJulia | ..... | 15:32 |
dtantsur | ikr? | 15:33 |
JayF | too bad we didn't get OIF to (tm) sushy | 15:33 |
JayF | lol; | 15:33 |
dtantsur | :D | 15:33 |
JayF | I'd be OK with a sushy-tools rename, maybe start a next-PTG etherpad with that? | 15:33 |
dtantsur | possibly | 15:33 |
TheJulia | or send something to the mailing list | 15:33 |
TheJulia | deferring to a PTG is a bad habit | 15:33 |
TheJulia | because it forces discussion to halt until high bandwidth discussion | 15:33 |
JayF | Maybe; but in this case I'd say halfway thru the cycle is a bad time to rename it | 15:34 |
dtantsur | I'm +1 to both proposals if they don't end up dumping a lot of obscure code on us | 15:34 |
TheJulia | which casues the topic to drop | 15:34 |
JayF | which is the only reason I punted it; not for the high-bw but for the "after release" :) | 15:34 |
TheJulia | JayF: would need to be well communicated and we would already be into the next cycle once we reach the PTG | 15:34 |
TheJulia | I've left a comment on the first sushy-tools rfe | 15:34 |
JayF | good point | 15:34 |
dtantsur | We could have renaming by forking fwiw | 15:34 |
JayF | so we are approving all those RFEs, right? | 15:35 |
dtantsur | Also dropping the static emulator that I'm afraid nobody uses | 15:35 |
dtantsur | yeah | 15:35 |
JayF | #info All RFEs evaluated at meeting are approved. | 15:35 |
JayF | #topic Open Discussion | 15:35 |
dtantsur | mmm, also mine? :) | 15:35 |
TheJulia | uhh, we did't get to the last one | 15:35 |
dtantsur | I don't mind it :D | 15:35 |
JayF | #undo | 15:35 |
opendevmeet | Removing item from minutes: #topic Open Discussion | 15:35 |
JayF | #undo | 15:35 |
opendevmeet | Removing item from minutes: #info All RFEs evaluated at meeting are approved. | 15:35 |
* JayF presses << on the tape player | 15:35 | |
JayF | What last one TheJulia? | 15:35 |
JayF | TheJulia: we batched dtantsur' | 15:35 |
dtantsur | #link https://bugs.launchpad.net/sushy-tools/+bug/2046153 Testing the minimal subset of Redfish features | 15:36 |
JayF | **we batched dtantsur's three together, so even though we did them out of order, I thought we discussed all 5? | 15:36 |
dtantsur | It's not even really an RFE, more of a heads-up | 15:36 |
dtantsur | I want us to avoid relying on a redfish implementation having ALL features we support | 15:36 |
TheJulia | the last one wasn't linked until when dtantsur just did so | 15:36 |
TheJulia | thought we were going in order | 15:36 |
dtantsur | for that, I want a CI job that runs with a bare sushy-tools with no extras at all | 15:36 |
dtantsur | objections, concerns? | 15:36 |
TheJulia | dtantsur: none really | 15:37 |
TheJulia | it *should* be a test scenario in the tempest plugin explicitly instead of a separate CI job itself, if at all possible. | 15:37 |
JayF | TheJulia: some mornings I can hide when I didn't get my coffee made before meeting... others... :) | 15:37 |
dtantsur | TheJulia: I was thinking to just changing one non-vmedia job | 15:38 |
TheJulia | or just, run the emulator on minimal and make sure none of the advanced features are turned on | 15:38 |
dtantsur | all I care about is that we don't e.g. depends on firmware versions being available as we've just accidentally done | 15:38 |
TheJulia | ok | 15:38 |
dtantsur | (context: https://review.opendev.org/c/openstack/ironic/+/903185) | 15:38 |
dtantsur | (in the past, we accidentally made EthernetInterfaces required, breaking mmm Cisco?) | 15:39 |
TheJulia | sweet! | 15:39 |
JayF | sounds like a pretty good diea then | 15:39 |
TheJulia | yeah, every redfish feature we do, we should be checking "if the value is not none" | 15:40 |
TheJulia | stupidly easy thing to miss though | 15:40 |
dtantsur | on that note, I also want to document which resources we require and which we can use if they are present | 15:40 |
dtantsur | (quite unfortunately, that the profiles work stagnated..) | 15:41 |
TheJulia | so a profile merged, but it is not quite clear | 15:41 |
dtantsur | Background: from time to time, our partners ask me for a list of Redfish APIs we require | 15:41 |
dtantsur | so I essentially have this document downstream. I can just publish it. | 15:42 |
TheJulia | makes sense, the profile is rather broad | 15:42 |
TheJulia | And I'm not sure anyone is using it :\ | 15:43 |
JayF | IDK how to go about this; but if we could document quirks too that'd be cool | 15:43 |
JayF | e.g. the bug around gigabyte servers wanting a different payload for boot mode than anything else | 15:43 |
dtantsur | We're trying to fix such things instead :) | 15:43 |
TheJulia | Did we get a reply to that one? | 15:43 |
JayF | https://bugs.launchpad.net/ironic/+bug/2045191 yes | 15:44 |
JayF | In fact it looks very good | 15:44 |
JayF | I left it incomplete because I wanted someone more redfishy to verify it was enough info | 15:44 |
JayF | but it LGTM | 15:44 |
-opendevstatus- NOTICE: Zuul jobs reporting POST_FAILURE were due to an incident with one of our cloud providers; this provider has been temporarily disabled and changes can be rechecked. | 15:44 | |
JayF | I also reached out a handful of different ways trying to get a contact in Gigabytes' server engineering team | 15:44 |
JayF | #topic Open Discussion | 15:45 |
JayF | (we are basically already doing this, just reflecting the reality) | 15:45 |
dtantsur | another fishy item, just as a heads-up: https://review.opendev.org/c/openstack/sushy-tools/+/903331 | 15:45 |
TheJulia | oh joy, yeah, what we have to do with them was semi-incompatiable with some of the other vendors | 15:45 |
TheJulia | ..... hmmmmmm | 15:46 |
JayF | This is part of why I'm trying to work out a contact in their server group :D | 15:46 |
JayF | Seems like the sort of thing that ... collaboration could improve future versions of | 15:46 |
TheJulia | yeah | 15:46 |
JayF | (I do not think I was/will be successful FWIW) | 15:46 |
TheJulia | I don't know if I'll have time to take a look this week, this week is shaping up already to be a very busy week | 15:47 |
JayF | I'm going to be focusing primarily on nova driver bits, trying to get sharding spec mergable and getting all the code lined back up | 15:48 |
JayF | so I can work on those tempest tests again | 15:48 |
TheJulia | I suspect we could likely just teach ironic to recognize such a constrant and send back the same value or something slightly wicked | 15:48 |
TheJulia | but where in that sequence is sort of a question, I'll need to look a little deeper | 15:48 |
JayF | Makes sense. | 15:49 |
JayF | Oh, one thing I wanted to mention for open discussion | 15:50 |
JayF | right now there are patches up in openstack/releases to retire Ironic Train/Ussuri branches due to the unmaintained branches migration | 15:50 |
JayF | AIUI devstack/various supporting CI cast things are going away for Train/Ussuri | 15:50 |
opendevreview | Riccardo Pittau proposed openstack/bifrost master: Fix disable-dhcp option in playbook https://review.opendev.org/c/openstack/bifrost/+/903135 | 15:50 |
JayF | if anyone wants to keep these up, and in unmaintained/* branches, they have [slightly less than, at this point] a month to go -1 that patch and volunteer to be the steward of those branches | 15:51 |
JayF | https://review.opendev.org/c/openstack/releases/+/903199 | 15:51 |
JayF | #info Train is scheduled to be EOL: https://review.opendev.org/c/openstack/releases/+/903199 -- if you wish it to not EOL, you must -1 that patch and volunteer to steward the branch. | 15:51 |
JayF | Anything else about that or for open discussion? | 15:52 |
TheJulia | I guess the Train is soon departing the last station | 15:52 |
JayF | 4+ years is too good of a run for a single release of software :D | 15:53 |
JayF | I'm going to close out the meeting if there's nothing else? | 15:53 |
TheJulia | ... unless we're required to release for 5 years | 15:54 |
TheJulia | https://www.digitalsme.eu/cyber-resilience-act-the-eu-strikes-a-deal-on-security-requirements-for-digital-products/ | 15:54 |
JayF | I think this is confirmation we're off the Ironic path for the day :D | 15:55 |
JayF | #endmeeting | 15:55 |
opendevmeet | Meeting ended Mon Dec 11 15:55:36 2023 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 15:55 |
opendevmeet | Minutes: https://meetings.opendev.org/meetings/ironic/2023/ironic.2023-12-11-15.01.html | 15:55 |
opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/ironic/2023/ironic.2023-12-11-15.01.txt | 15:55 |
opendevmeet | Log: https://meetings.opendev.org/meetings/ironic/2023/ironic.2023-12-11-15.01.log.html | 15:55 |
JayF | TheJulia: put that up there with "nobody outside the US deserves >40 bits of encryption" in the crappy tech law hall of fame | 15:56 |
TheJulia | lolz | 15:56 |
TheJulia | so does that mean the 128bit encryption service pack accidently applying to the 40 bit NT4 machine... comes in, third? | 15:57 |
JayF | aha, https://review.opendev.org/c/openstack/nova/+/867798 was what I tested on top of | 15:58 |
JayF | so we broke in the middle of the patch chain | 15:58 |
JayF | that at least explains why things happened to break up | 15:58 |
JayF | s/up/us | 15:58 |
JayF | dtantsur: I'll point out, eventlet maintainer just handed over keys to other maintainers | 16:01 |
JayF | dtantsur: so we might have a path outta your py3.6 pain | 16:01 |
dtantsur | \o/ | 16:02 |
rpittau | wow | 16:03 |
JayF | https://github.com/eventlet/eventlet/issues/824 | 16:03 |
TheJulia | wow, sweet | 16:03 |
JayF | I feel like all I did was send like, 3-4 emails and have a bunch of conversations and then hand over to Herve | 16:03 |
JayF | but somehow still feels like the most impactful thing I've gotten moving in a while lol | 16:03 |
TheJulia | well, short term wise :) | 16:04 |
JayF | I think it' | 16:04 |
JayF | *it's pretty obvious I follow the "sunshine and rainbows and inspirational" viewpoint of OSS | 16:04 |
TheJulia | lol | 16:05 |
JayF | and "saving a decade+ old project from lack of maintainership to provide an offramp with a peaceful transition of power" is the Mona Lisa of inspirational OSS moments lol | 16:05 |
TheJulia | eh, yeah | 16:05 |
JayF | That's one of the things I appreciate the most about OpenStack; we do a decent job (at least on the primary projects) of having continuity of maintainership over time | 16:06 |
dtantsur | ++ | 16:28 |
opendevreview | Dmitry Tantsur proposed openstack/sushy-tools master: Add feature sets to test with different available feature https://review.opendev.org/c/openstack/sushy-tools/+/903360 | 16:49 |
opendevreview | Dmitry Tantsur proposed openstack/ironic master: [DNM] Test with reduced sushy-tools feature set https://review.opendev.org/c/openstack/ironic/+/903361 | 16:51 |
opendevreview | Dmitry Tantsur proposed openstack/ironic master: [DNM] Test with reduced sushy-tools feature set https://review.opendev.org/c/openstack/ironic/+/903361 | 16:53 |
rpittau | good night! o/ | 17:08 |
JayF | \o | 17:09 |
mnasiadka | dtantsur: tried c9s based IPA on Yoga - but getting Unexpected exception performing clean step delete_configuration. UnboundLocalError: local variable 'raid_device' referenced before assignment - and fresh c8s builds suffer from eventlet issue (I think) - so I'm a bit stuck with my sw raid problem ;-) | 17:32 |
stevebaker[m] | good morning | 19:07 |
TheJulia | good morning | 19:13 |
opendevreview | Baptiste Jonglez proposed openstack/networking-generic-switch master: Introduce NGS agent design https://review.opendev.org/c/openstack/networking-generic-switch/+/897047 | 19:25 |
opendevreview | Iury Gregory Melo Ferreira proposed openstack/ironic master: [WIP] RedfishFirmwareInterface - Unit Tests & More logs https://review.opendev.org/c/openstack/ironic/+/903379 | 20:20 |
JayF | > tempest-integrated-compute TIMED_OUT | 20:21 |
JayF | nooooooooooooo | 20:21 |
JayF | after 5 hours and 30 minutes in the gate | 20:21 |
iurygregory | yeah | 20:21 |
JayF | the nova driver fix went boom :( nova gate is really unstable and everything getting batched makes it more painful | 20:21 |
iurygregory | I just saw that | 20:21 |
iurygregory | =( | 20:21 |
JayF | iurygregory: fwiw, when I say -0, I just mean *I personally* don't wanna +2/-1 such a change | 20:21 |
JayF | iurygregory: doesn't mean you couldn't have done it anyway or I wouldve been upset if you did | 20:22 |
iurygregory | JayF, I totally understand =) | 20:22 |
JayF | for now we need to -nv it I suspect :( | 20:22 |
iurygregory | probably, I think it's valid going to nv (if we are in a hurry), but 5hrs and 30min to get the timed-out hurst quite a lot | 20:26 |
JayF | well, let me put it this way, at last TC meeting (or maybe one before?) someone reported needing 10+ rechecks to land something in nova | 20:33 |
JayF | so while I was gung-ho this weekend to find a fix, get it in the gate, and be hopeful, I only have hope for one ride around the block :D | 20:34 |
JayF | lol | 20:34 |
iurygregory | 10 rechecks? | 20:35 |
JayF | yep | 20:35 |
JayF | we do a gate health check in tc meetings, so I hear when the shared pieces are in especially bad shape | 20:36 |
JayF | (fwiw we are usually in good shape in Ironic comparatively .... except when we're not LOL) | 20:36 |
iurygregory | if we consider 7h:30min (since the job that failed took 2hrs in check) I hope my math is correct.. each run takes 450min, 4500min is 75hrs | 20:37 |
iurygregory | OMG! | 20:37 |
JayF | well remember that the 5:30 represents multiple failures due to how the gate is stacked | 20:38 |
JayF | when I first checked that change this morning, it was like, #12 down the list | 20:38 |
JayF | random failures took out changes above it in the gate list over and over for hours, until finally it got a chance to get far enough to fail on its own lol | 20:38 |
JayF | (because we try to, for instance, if 10 things wanna merge across devstack/nova/cinder/etc -- anything with a shared gate -- we merge them all together and try to get them landed with *one* shared CI job) | 20:39 |
* TheJulia wonders if the gate should maybe just have a depth limit on speculativeness | 20:39 | |
JayF | That's about as deep as I've seen one, I suspect on Monday mornings it might get silly as people start approving things first thing | 20:39 |
*** dmellado2 is now known as dmellado | 23:16 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!