rpittau | good morning ironic! o/ | 07:10 |
---|---|---|
rpittau | cardoe: yes for sushy release, definitely, we have a guide for the release if you want to take care of that https://docs.openstack.org/ironic/latest/contributor/releasing.html | 07:31 |
opendevreview | Merged openstack/ironic-tempest-plugin master: Drop unnecessary 'x' bit from doc config file https://review.opendev.org/c/openstack/ironic-tempest-plugin/+/932865 | 07:51 |
opendevreview | Merged openstack/ironic-ui master: Drop unnecessary 'x' bit from doc config file https://review.opendev.org/c/openstack/ironic-ui/+/932866 | 07:52 |
opendevreview | Verification of a change to openstack/ironic-python-agent stable/2024.1 failed: Remove non RE2 job config https://review.opendev.org/c/openstack/ironic-python-agent/+/932660 | 07:58 |
opendevreview | Merged openstack/networking-baremetal master: Drop unnecessary 'x' bit from doc config file https://review.opendev.org/c/openstack/networking-baremetal/+/932872 | 07:58 |
dtantsur | JayF: this could be a fallout from the CVE: https://bugs.launchpad.net/ironic-python-agent/+bug/2085331 | 09:06 |
dtantsur | actually... I need to check if Metal3 does the right thing, hold on | 09:09 |
opendevreview | Dmitry Tantsur proposed openstack/ironic-python-agent master: Warn when the provided checksum algorithm does not match the detected https://review.opendev.org/c/openstack/ironic-python-agent/+/932977 | 09:38 |
iurygregory | good morning | 11:10 |
iurygregory_ | power outage :facepalm: | 11:37 |
*** iurygregory_ is now known as iurygregory | 11:38 | |
opendevreview | cid proposed openstack/ironic master: Gracefully handle bad request exception https://review.opendev.org/c/openstack/ironic/+/931849 | 12:02 |
TheJulia | good morning | 12:40 |
rpittau | good morning TheJulia :) | 12:55 |
rpittau | ironic PTG starting in 5 minutes! https://meetpad.opendev.org/ironic-ptg-october-2024 | 12:55 |
cardoe | this conf has a distinct lack of coffee. staggering into the morning keynote and able to just fill up a cup on my way in of $RANDOM blend is what I've become accustomed to. | 12:56 |
dtantsur | Alas! | 12:57 |
cardoe | another random thought while I wait for coffee to brew... how do flat earthers reconcile time zones? | 12:59 |
iurygregory | oh no | 12:59 |
iurygregory | kkkkkkkkkkkk | 12:59 |
rpittau | cardoe: there is no such thing as time zones in flat-heart-world :) | 13:00 |
TheJulia | cardoe: your using logic, be careful or you'll break brains ;) | 14:27 |
cardoe | heh | 14:28 |
* cid :d wait, was I stopping people from speaking? | 15:02 | |
JayF | no, you're good :) | 15:06 |
* cid thought I was moderator just like yesterday (weird) | 15:06 | |
opendevreview | Doug Goldstein proposed openstack/ironic master: dedup reboot request in redfish bios path https://review.opendev.org/c/openstack/ironic/+/933020 | 15:08 |
cardoe | rpittau: can I propose another topic? | 15:16 |
cardoe | Python typing | 15:17 |
rpittau | cardoe: you mean today or in general? | 15:20 |
cardoe | in general | 15:20 |
rpittau | cardoe: sure :) | 15:20 |
JayF | it'd be fun to do this now :) | 15:23 |
cardoe | Let's do it now then | 15:24 |
opendevreview | Pavlo Shchelokovskyy proposed openstack/ironic master: Update some ipmi config option help strings https://review.opendev.org/c/openstack/ironic/+/933023 | 15:33 |
cardoe | skrobul pointed out I broke something so I'll be afk from the session for a bit. ping me here if it's one of my topics. | 16:07 |
opendevreview | Merged openstack/ironic-lib master: add pyproject.toml to support pip 23.1 https://review.opendev.org/c/openstack/ironic-lib/+/932738 | 16:07 |
opendevreview | Dmitry Tantsur proposed openstack/ironic-lib master: Drop the unused capabilities module https://review.opendev.org/c/openstack/ironic-lib/+/933029 | 16:25 |
dtantsur | JayF: ^^^ | 16:25 |
dtantsur | feel free to double-check that it's not used | 16:25 |
opendevreview | Merged openstack/ironic-python-agent master: Warn when the provided checksum algorithm does not match the detected https://review.opendev.org/c/openstack/ironic-python-agent/+/932977 | 16:49 |
cardoe | rpittau: when ya get some time could you weigh in on https://review.opendev.org/c/openstack/sushy/+/932096 | 16:51 |
JayF | is https://review.opendev.org/c/openstack/ironic/+/931849 backportable? WDYT? | 17:07 |
TheJulia | should be, I think | 17:16 |
TheJulia | regardless it should have raised a bad request response | 17:16 |
opendevreview | Jay Faulkner proposed openstack/ironic stable/2024.2: Gracefully handle bad request exception https://review.opendev.org/c/openstack/ironic/+/933036 | 17:18 |
opendevreview | Doug Goldstein proposed openstack/ironic master: WIP: redbios BIOS apply settings support disable_ramdisk https://review.opendev.org/c/openstack/ironic/+/933037 | 17:23 |
cardoe | JayF: My little script to handle "git review" dropped me from the meeting | 17:24 |
JayF | we dropped the meeting anyway because it was outta steam :) | 17:24 |
cardoe | It turns off the VPN and then turns it back on and that blipped me | 17:24 |
JayF | and I've been on for like 4.5 hours | 17:24 |
JayF | chipotle will be required :D | 17:24 |
cardoe | That's the WIP change above I was asking about. | 17:24 |
cardoe | I'll ask about it tomorrow then. | 17:25 |
JayF | I have it open | 17:25 |
JayF | will look and comment async | 17:25 |
JayF | itamarst, same GR-OSS python dev who helped out some with the uplift of eventlet last year, is going to take a look at the virtualpdu upgrade | 17:39 |
JayF | so we'll see if he can apply his magical async python knowledge to help us out | 17:39 |
JayF | cardoe: You know, I wonder if you just want two steps, not one | 17:44 |
JayF | cardoe: one with a guaranteed reboot, one without | 17:44 |
JayF | cardoe: maybe BIOSInterface.stage_configuration | 17:45 |
JayF | which would make sense for "setup the bios config for next reboot" without the reboot | 17:45 |
JayF | and would leave the existing behavior intact for people who want the reboot | 17:45 |
cardoe | Well I'm leaving the reboot behavior intact. | 17:45 |
cardoe | So you have to reboot. | 17:46 |
JayF | So prior to that change: IPA's heartbeat was the "ok the bios config applied" (?) | 17:47 |
JayF | and after that change, the hope is, just the idea that it powered off/on is enough to know the config applied | 17:47 |
JayF | it's not easy code to follow (not really your fault) | 17:47 |
opendevreview | Merged openstack/ironic unmaintained/xena: Fix actual size calculation for storage fallback logic https://review.opendev.org/c/openstack/ironic/+/931285 | 18:08 |
opendevreview | Merged openstack/ironic unmaintained/wallaby: Fix actual size calculation for storage fallback logic https://review.opendev.org/c/openstack/ironic/+/931286 | 18:08 |
cardoe | So the existing code path is run the "reset BIOS" or the "apply pile of BIOS settings" step. You must be booted into the IPA image for this to work. | 18:08 |
cardoe | It hits the redfish endpoints for either of those and then reboots the machine. The BMC is responsible for seeing that someone has staged either of those two operations and then applies them before booting the machine. | 18:09 |
cardoe | It's implementation specific if you DON'T reboot after doing "reset BIOS" or "apply pile of BIOS settings". Some machines are happy to continue servicing other Redfish requests. While others give you various levels of "don't talk to me". | 18:10 |
cardoe | While some will clear the pending request if you do something else. | 18:11 |
cardoe | The box reboots and IPA comes back up and loads back into the current step. Since the first time through we dropped something into driver_internal_info, it says "oh I must have been booted up and the changes applied. hooray." | 18:12 |
cardoe | In the "apply pile of BIOS settings" case, we check if in fact those settings were applied and if not we go into error. | 18:12 |
cardoe | In the "reset BIOS" case we just assume that the BIOS must have been reset. | 18:12 |
cardoe | Looking to provide an escape hatch for https://docs.openstack.org/ironic/latest/admin/drivers/idrac.html#pxe-reset-with-factory-reset-bios-clean-step | 18:13 |
cardoe | Because today if we use UEFI, I cannot reset the BIOS because the box doesn't come back up. | 18:14 |
cardoe | If I'm PXE/HTTP booting. | 18:14 |
cardoe | Now my patch doesn't actually address that (because I didn't touch the BIOS reset case). | 18:14 |
JayF | Aside: WTF WHY WOULD DELL DEFAULT TO BIOS BOOT | 18:14 |
JayF | oh, I see | 18:15 |
cardoe | They don't. If you're in UEFI mode then the boot device enable/disable state comes from the BIOS settings. If you're booting in BIOS mode the PXE enable/disable comes from outside of that path. | 18:16 |
JayF | yeah I read the link after making the statement. very jay of me :D | 18:16 |
cardoe | Right now I'm really just interested in we roll in a rack of boxes. They don't have HTTP boot enabled (or PXE but we're using HTTP boot). So I can't ingest them into Ironic. | 18:17 |
cardoe | So I first need to set some BIOS settings then ingest them into Ironic. | 18:17 |
cardoe | Julia saw James's talk where he mentioned some of this "first touch" steps. | 18:18 |
JayF | but you can't set bios settings, because of how the flow works, without having IPA booted | 18:18 |
cardoe | Yep | 18:18 |
JayF | I still feel like this almost would be nicer composed | 18:18 |
JayF | like some agentless apply configuration step | 18:18 |
JayF | that expects *the caller* to reboot step next if that's the right thing | 18:19 |
cardoe | I’m down for doing whatever is correct. In other things we follow the task. | 18:28 |
opendevreview | Merged openstack/ironic unmaintained/yoga: Fix actual size calculation for storage fallback logic https://review.opendev.org/c/openstack/ironic/+/931283 | 18:48 |
opendevreview | Merged openstack/ironic unmaintained/zed: Fix actual size calculation for storage fallback logic https://review.opendev.org/c/openstack/ironic/+/931282 | 18:48 |
JayF | I'm just thinking out loud | 18:48 |
opendevreview | Merged openstack/ironic master: Enable GLOBAL_VENV in ironic grenade jobs https://review.opendev.org/c/openstack/ironic/+/932016 | 18:48 |
opendevreview | Verification of a change to openstack/ironic master failed: Gracefully handle bad request exception https://review.opendev.org/c/openstack/ironic/+/931849 | 18:49 |
opendevreview | Merged openstack/ironic master: docs: Updates redfish metrics docs with required configuration file settings https://review.opendev.org/c/openstack/ironic/+/932551 | 18:49 |
JayF | like I alluded to before in the review jam, I'm probably not the best person to be talking design for sushy :) | 18:49 |
cardoe | sorry. had a repairman come by | 18:55 |
cardoe | https://opendev.org/openstack/ironic/src/commit/1f740c8a90e1c9bcdd2fb7ee589a5b38d16f8e1e/ironic/drivers/modules/redfish/firmware.py#L395-L404 | 18:57 |
cardoe | https://opendev.org/openstack/ironic/src/commit/1f740c8a90e1c9bcdd2fb7ee589a5b38d16f8e1e/ironic/drivers/modules/redfish/raid.py#L991-L1012 | 18:57 |
cardoe | That's what I was referring to as far as the task tracking. | 18:58 |
cardoe | So on the HPE and Dell gear I've got, once you reboot the machine a task is created. | 18:58 |
JayF | ugh so you can't even be like "do this" and it's "okay" | 19:00 |
JayF | it's literally "do this" "reboot" "okay" | 19:00 |
cardoe | https://review.opendev.org/c/openstack/releases/+/933056 is that correct? | 20:03 |
iurygregory | cardoe, depends are you planning a new release for Dalmatian? if yes, yup looks correct | 20:03 |
cardoe | yeah was looking to make one final release with Python 3.8 support | 20:04 |
cardoe | before we merge the removal of Python 3.8 support | 20:05 |
iurygregory | wait, in this case we need Epoxy release | 20:05 |
iurygregory | not Dalmatian, I would say | 20:05 |
iurygregory | and the only diff of commits is: | 20:06 |
iurygregory | Changes between 5.2.0 and d39c713 | 20:06 |
iurygregory | * d39c713 2024-09-06 13:09:30 +0000 Update TOX_CONSTRAINTS_FILE for stable/2024.2 | 20:06 |
iurygregory | * fc5292e 2024-09-06 13:09:28 +0000 Update .gitreview for stable/2024.2 | 20:06 |
iurygregory | the release team won't do a release because there is no code changes | 20:06 |
cardoe | okay so I need to backport the stuff into stable/2024.2 first? | 20:07 |
iurygregory | if you want a new release for Dalmatian yes, we need backports =) | 20:07 |
iurygregory | aren't we just planning on dropping 3.8 in Epoxy? | 20:08 |
iurygregory | if this is the case we need to release 5.3.0 in Epoxy | 20:08 |
cardoe | Yeah probably | 20:09 |
opendevreview | Doug Goldstein proposed openstack/sushy stable/2024.2: drop usage of pkg_resource for newer python compat https://review.opendev.org/c/openstack/sushy/+/933058 | 20:10 |
cardoe | So like ^ that first and then re-do that 5.2.1 with the commit ID that lands. | 20:11 |
cardoe | sushy doesn't really seem tied to OpenStack releases to me | 20:11 |
iurygregory | ok I'm puzzled, why we would need https://review.opendev.org/c/openstack/sushy/+/933058 in Dalmatian? | 20:12 |
cardoe | So I'm gonna speak PyPi packages if that's okay and maybe you can tell me where I'm wrong? | 20:13 |
iurygregory | because looking at the setup.cfg we support till 3.11 in Dalmatian | 20:13 |
iurygregory | so things shouldn't break | 20:13 |
iurygregory | .-. | 20:14 |
iurygregory | https://github.com/openstack/sushy/blob/stable/2024.2/setup.cfg | 20:14 |
cardoe | So we released sushy 5.2.0 before we added the Python 3.8 -> 3.12 support. | 20:14 |
iurygregory | correct | 20:14 |
cardoe | We said we'd drop Python 3.8 from sushy but we wanted 1 release (5.2.1) which supported both as a migration path. | 20:14 |
cardoe | So 5.2.1 would support 3.8 -> 3.12 | 20:14 |
opendevreview | Pavlo Shchelokovskyy proposed openstack/ironic master: Expand detected strings in check_cipher_suite_errors https://review.opendev.org/c/openstack/ironic/+/932915 | 20:14 |
opendevreview | Pavlo Shchelokovskyy proposed openstack/ironic master: Update some ipmi config option help strings https://review.opendev.org/c/openstack/ironic/+/933023 | 20:14 |
cardoe | And then 5.3.0 would support 3.9+ only | 20:15 |
iurygregory | so in Epoxy we have 3.8 -> 3.12 currently correct? | 20:15 |
cardoe | yes | 20:15 |
cardoe | But we'll release Epoxy with 3.9+ | 20:15 |
iurygregory | so we just need to release 5.3.0 in Epoxy first, after that we drop the 3.8 and do another release 5.4.0 (probably) | 20:16 |
iurygregory | at least this would be my understanding, we shouldn't backport https://review.opendev.org/c/openstack/sushy/+/933058 to Dalmatian I would say | 20:16 |
cardoe | I'm just trying to land what was asked. | 20:17 |
cardoe | I had to get stuff into global-requirements.txt to make a version that supported 3.8 -> 3.12 | 20:17 |
iurygregory | what was added to global-requirements? | 20:18 |
cardoe | the pkg_resources backport | 20:18 |
iurygregory | ok, found the patch | 20:18 |
JayF | I am +1 to this backport, fwiw, as long as it's in global reqs for 2024.2 | 20:20 |
cardoe | it is | 20:20 |
iurygregory | ok, it's present in the requirements for Dalmatian | 20:20 |
iurygregory | my concern is basically that in Dalmatian we don't support py3.12, so no need for the https://review.opendev.org/c/openstack/sushy/+/933058 | 20:21 |
iurygregory | and for Epoxy we can follow the idea of doing a release now before dropping py3.8 (but the version will be 5.3.0 probably, not 5.2.1) | 20:21 |
cardoe | I just wanted sushy to support Python 3.12. Folks insisted that I needed to land something that supported Python 3.12 AND Python 3.8. | 20:23 |
cardoe | tkajinam: | 20:23 |
cardoe | tkajinam: has proposed a change that basically drops Python 3.8 and removes all the backport stuff I did. | 20:23 |
cardoe | Which we want to merge for Epoxy | 20:23 |
iurygregory | I understand | 20:23 |
cardoe | I'm just trying to figure out what I need to do to move forward and I don't understand. | 20:24 |
iurygregory | but we can have a release in Epoxy with the 3.8 -> 3.12 | 20:24 |
JayF | My suggestion is: 1) backport to 2024.2, 2) release 2024.2, 3) maybe also release master as an epoxy deliverable before tkaj's changes land | 20:24 |
iurygregory | and after having this release we can merge tkajinam patch to drop 3.8 and have a new release in Epoxy also | 20:24 |
JayF | I am skeptical anyone wants to run the release #3 would be creating, but it's probably nice for completeness anyway | 20:25 |
iurygregory | JayF, i'm puzzled why we need in 2024.2 (since we don't support 3.12 there) | 20:25 |
JayF | iurygregory: 'need' is not really the measuring stick I'm using for this; we have an operator who expressed a need (cardoe) to have it, and I don't see any harm whatsoever it'd cause to meet that need | 20:26 |
cardoe | So that global-requirements piece is being removed from epoxy. | 20:26 |
JayF | plus I assume if he wants it, other folks would | 20:26 |
cardoe | So the only place I can make this release would be in 2024.2 | 20:26 |
JayF | ooh | 20:26 |
cardoe | because epoxy has dropped 3.8 | 20:26 |
JayF | that's the winner then, and only backport+release no master release in that case imo | 20:26 |
iurygregory | cardoe, are you running py3.12 in Dalmatian? (just trying to understand your case) | 20:26 |
cardoe | I'm running "pip install sushy" | 20:27 |
cardoe | I just want a release that works on Python 3.12 | 20:27 |
JayF | cardoe: if you don't care that it /also works on 3.12/ theoretically a release from master after tkaj's change merges would do that | 20:27 |
opendevreview | Pierre Riteau proposed openstack/tenks master: Use openstackdocstheme for release notes https://review.opendev.org/c/openstack/tenks/+/933059 | 20:28 |
JayF | but honestly I also feel bad if the code you wrote for that bridge is just ... never in a useful place | 20:28 |
cardoe | yeah. you guys flogged me over it and I had to harass the requirements repo owners to land that backport piece. | 20:28 |
cardoe | only for it to be reverted out weeks after the release. | 20:29 |
JayF | you guys is not a unanimous thing in an oss community fwiw | 20:29 |
cardoe | yeah fair | 20:29 |
JayF | but like I said, I'm personally +2 to backporting and releasing | 20:29 |
cardoe | iurygregory: I'm pushing our folks and teams to use upstream sushy and contribute to sushy. | 20:29 |
cardoe | I've got a Python 3.12 need for making that happen. | 20:29 |
JayF | iurygregory: cardoe: I'm going to +2 the backport, if you feel strongly it shouldn't be backported lets have that discussion in the change. I don't wanna get in someones' way, especially when they are trying to prove out OSS contribution (and I personally have been on the business end of that business' impatience and would like to save cardoe from that) | 20:31 |
iurygregory | cardoe, right, I understand, in my mind 3.12 is something for Epoxy so our release should be in Epoxy not Dalmatian | 20:32 |
cardoe | So fwiw tkajinam's patch is what I proposed at first. | 20:32 |
JayF | iurygregory: the platform stuff published by the TC is a minimum | 20:32 |
iurygregory | happy to +1, but I don't feel like I would +W | 20:32 |
JayF | iurygregory: I'm very very happy to go above and beyond for a contributor when the effort needed for us to do it is a +2A on a backport | 20:32 |
cardoe | But I was told before I could land 3.12 support I needed to continue to support 3.8 | 20:33 |
cardoe | So I did that part. | 20:33 |
JayF | as much as we ask folks to scratch their own itches we should be accomodating | 20:33 |
cardoe | I'm fine just landing tkajinam's change and making a release too. | 20:33 |
cardoe | But I know I got pushed hard to make the backport style. | 20:33 |
JayF | I think both is probably the best answer | 20:33 |
iurygregory | so maybe adding 3.12 in Dalmatian for sushy as supported? | 20:33 |
cardoe | sushy is used in a bunch more than just OpenStack releases. | 20:34 |
iurygregory | not only the backport, but also updating the setup.cfg there | 20:34 |
cardoe | OpenShift has a bunch of repos that depend on it. | 20:34 |
JayF | https://github.com/openstack/sushy/blob/master/setup.cfg#L23 that's a damned good point | 20:34 |
cardoe | And don't pull in anything else OpenStack-y | 20:34 |
JayF | we can't backport declaration of support for 3.12 | 20:34 |
iurygregory | not really a bunch, only 1 repo in OCP | 20:34 |
JayF | and is this patch worthwhile without a setup.cfg change? | 20:34 |
JayF | cardoe: iurygregory: my downstream utilizes sushy, and they aren't the only one I've heard | 20:35 |
iurygregory | JayF, yup that what I'm wondering | 20:35 |
iurygregory | in Dalmatian we are 3.8 -> 3.11 | 20:35 |
JayF | cardoe: and is this patch useful **to you/rax** without a setup.cfg change? | 20:35 |
opendevreview | Doug Goldstein proposed openstack/sushy master: advertise Python 3.12 support https://review.opendev.org/c/openstack/sushy/+/933060 | 20:35 |
cardoe | There's the setup.cfg change. | 20:35 |
JayF | yeah, but that is not backportable at all | 20:36 |
cardoe | yes this is usable to me without a setup.cfg change. | 20:36 |
JayF | which is what I'm asking, is a 2024.2 release useful to you without the setup.cfg change along with it | 20:36 |
JayF | then I'm still +2 to backporting it | 20:36 |
cardoe | today we're pulling a git commit via requirements.txt | 20:36 |
iurygregory | oh ok, if works without the setup.cfg I'm ok with it | 20:36 |
JayF | setup.cfg only impacts `pip install X` resolution | 20:36 |
cardoe | JayF: nope it doesn't | 20:36 |
JayF | oh, really? | 20:37 |
cardoe | That's just text on pypi.org | 20:37 |
JayF | *blink* | 20:37 |
cardoe | It's not used by the resolver at all. | 20:37 |
JayF | :-O | 20:37 |
* JayF goes to pip install ironic==1 | 20:37 | |
cardoe | python_requires is the line in setup.cfg you'd have to do | 20:37 |
cardoe | python_requires=>3.8,<3.12 | 20:37 |
JayF | ahhh that makes more sense | 20:37 |
JayF | it wouldn't be python if there weren't 4 ways of doing the same thing that mildly overlap | 20:38 |
JayF | maybe add a ^ packaging ecosystem | 20:38 |
JayF | somewhere around ther | 20:38 |
iurygregory | https://review.opendev.org/c/openstack/sushy/+/933058 +W | 20:39 |
JayF | nice | 20:39 |
JayF | and I learned a thing | 20:39 |
iurygregory | we learned =) | 20:39 |
JayF | next super hot python packaging thing should totally swap the metadata it uses for resolution | 20:40 |
JayF | just to mix it up a little more | 20:40 |
iurygregory | in my mind it wouldn't work without the setup.cfg XD | 20:40 |
JayF | when someone writes plp in whatever the next rust is /s | 20:40 |
iurygregory | lol | 20:40 |
cardoe | JayF: that's uv | 20:41 |
JayF | that's the one in rust, not in whatever the cool new rust will be | 20:42 |
JayF | I think it's about time for another interpreted language now, which will knock everything down a peg. perl will turn into bash, php will turn into perl, ruby will turn into php, and python will turn into ruby | 20:43 |
cardoe | oooo someone added httpx into global-requirements for epoxy | 21:15 |
JayF | yeah, things are moving | 21:15 |
JayF | and it's not as hard to get things in g-r as it used to be | 21:15 |
JayF | literally the only thing sending metrics in IPA today are four api methods | 21:28 |
JayF | in a way that is not going to be useful | 21:28 |
JayF | I'm still going through the deprecation motions because I'm basically there, but there's no way anyone is using this | 21:28 |
JayF | or maybe should say, there's no way this is providing value to anyone even if it's hooked up | 21:28 |
opendevreview | Jay Faulkner proposed openstack/ironic-python-agent master: Vendor metrics library from Ironic-Lib & deprecate https://review.opendev.org/c/openstack/ironic-python-agent/+/933063 | 21:37 |
opendevreview | Merged openstack/sushy stable/2024.2: drop usage of pkg_resource for newer python compat https://review.opendev.org/c/openstack/sushy/+/933058 | 21:46 |
iurygregory | cardoe, feel free to update the release patch since the backport is merged | 22:41 |
iurygregory | I can +1 the release | 22:41 |
opendevreview | Doug Goldstein proposed openstack/ironic master: allow running inspection hooks on redfish interface https://review.opendev.org/c/openstack/ironic/+/933066 | 23:05 |
cardoe | Done. I think I did the right thing iurygregory | 23:06 |
iurygregory | checking | 23:06 |
iurygregory | yup, correct =) | 23:08 |
cardoe | that inspection hooks I've marked as a WIP for the PTG topic for tomorrow. | 23:11 |
cardoe | https://review.opendev.org/c/openstack/ironic/+/634373 JayF / dtantsur / TheJulia that's another example of the vendor specific-ness | 23:12 |
opendevreview | Doug Goldstein proposed openstack/ironic master: Enable WSGI module entrypoint for Ironic https://review.opendev.org/c/openstack/ironic/+/927635 | 23:29 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!