| opendevreview | Verification of a change to openstack/ironic master failed: Build PXE config for node in SERVICING state https://review.opendev.org/c/openstack/ironic/+/922006 | 00:06 |
|---|---|---|
| opendevreview | cid proposed openstack/ironic master: Provision ARM (aarch64) fake-bare-metal-vms https://review.opendev.org/c/openstack/ironic/+/915441 | 02:17 |
| opendevreview | Merged openstack/ironic stable/2024.1: fix: Fix class typo for portgroup. Portgroup instead of PortGroup https://review.opendev.org/c/openstack/ironic/+/922250 | 03:42 |
| opendevreview | Verification of a change to openstack/ironic stable/2023.1 failed: fix: Fix class typo for portgroup. Portgroup instead of PortGroup https://review.opendev.org/c/openstack/ironic/+/922252 | 03:43 |
| opendevreview | Merged openstack/ironic stable/2023.2: fix: Fix class typo for portgroup. Portgroup instead of PortGroup https://review.opendev.org/c/openstack/ironic/+/922251 | 04:54 |
| opendevreview | Verification of a change to openstack/ironic master failed: Build PXE config for node in SERVICING state https://review.opendev.org/c/openstack/ironic/+/922006 | 06:03 |
| sylvr | Hello! I'm about to deploy a cloud using kayobe and I have some questions. In the documentation https://docs.openstack.org/kayobe/latest/configuration/reference/network.html it says that control hosts are in the storage network by default, is it a requirement or is it ok if my control hosts are in the management network and the external network only ? (using kolla_vip to access the web-based control pane) | 08:51 |
| dtantsur | sylvr: you may want to check this one with #openstack-kolla, we only know Ironic/Bifrost parts well | 08:52 |
| opendevreview | Merged openstack/ironic master: Build PXE config for node in SERVICING state https://review.opendev.org/c/openstack/ironic/+/922006 | 08:52 |
| sylvr | I'm sorry, I used the wrong channel | 08:53 |
| sylvr | thanks! | 08:53 |
| rpittau | good morning ironic! o/ | 08:53 |
| opendevreview | Verification of a change to openstack/ironic master failed: Remove deprecated xclarity hardware type https://review.opendev.org/c/openstack/ironic/+/922260 | 10:34 |
| opendevreview | Merged openstack/ironic-python-agent-builder master: Remove centos7 specific logic check https://review.opendev.org/c/openstack/ironic-python-agent-builder/+/922248 | 10:42 |
| opendevreview | Verification of a change to openstack/ironic master failed: Remove deprecated xclarity hardware type https://review.opendev.org/c/openstack/ironic/+/922260 | 10:59 |
| adam-metal3 | hello Ironic, is there a possibility to enable disk encryption for disk image streaming ? I have a feeling that in general no but wanted to ask before I start implement some custom hardware manager | 11:02 |
| dtantsur | adam-metal3: there is no built-in support (people tend to have their images already encrypted) | 11:03 |
| adam-metal3 | dtantsur, thanks, makes sense | 11:05 |
| iurygregory | good morning Ironic | 11:37 |
| TheJulia | good morning | 13:25 |
| opendevreview | Merged openstack/ironic master: Remove deprecated xclarity hardware type https://review.opendev.org/c/openstack/ironic/+/922260 | 13:53 |
| JayF | I'm doing the timeline math on those deprecation+removals | 14:32 |
| JayF | https://opendev.org/openstack/ironic/commit/6ac1308050292ab13bd1690f52b2e5c653f1d1ad is when the deprecation was documented, just before 2023.1 | 14:33 |
| JayF | s/2023.1/2024.1/ | 14:33 |
| JayF | If we didn't announce deprecation until 2024.1, doesn't that mean we have to keep 'em through 2025.2? | 14:33 |
| JayF | but I know I always have my thinking on this backwards so trying to think out loud to verify | 14:33 |
| JayF | we also said to be removed in 2024.2 | 14:34 |
| JayF | so probably not a big deal, just want to understand the proper way to think about that | 14:34 |
| JayF | I guess we had a slurp with them deprecated, for users to migrate in (2024.1) and they'll have to migrate before going to next slurp (2025.1)? | 14:35 |
| JayF | I think it feels weird to me b/c if we had done this in 2023.2 we'd have to wait until 2024.2 to deprecate it anyway | 14:35 |
| rpittau | isn't it removal the cycle after deprecation ? | 14:49 |
| rpittau | I mean that can happen | 14:49 |
| rpittau | unless we specifically mentioned a timeline | 14:50 |
| rpittau | at least I would expect that | 14:50 |
| JayF | cycle is slurp now though | 14:55 |
| JayF | so 2023.1->2024.1 | 14:55 |
| rpittau | mmm right | 14:55 |
| JayF | so I think we are OK; because like I said, someone knows in 2023.1 they need to upgrade, it'll be gone in 2024.1 | 14:59 |
| JayF | but I wanted to have this conversation out loud to be certain | 14:59 |
| rpittau | honestly I didn't remember if we mentioned that in 2023.1 or 2023.2, but we're in 2024.2 dev cycle so should be good anyway, no? | 15:02 |
| JayF | https://opendev.org/openstack/ironic/commit/6ac1308050292ab13bd1690f52b2e5c653f1d1ad | 15:02 |
| JayF | nov 2023 would've been 2023.1 | 15:03 |
| JayF | so we marked deprecated in 2023.1, removed in 2023.2 | 15:03 |
| JayF | that's why it seemed a little speedy to me | 15:03 |
| rpittau | ok | 15:03 |
| JayF | er, 2024.1 | 15:04 |
| rpittau | yeah | 15:04 |
| JayF | 2024.1 deprecated, 2024.2 removal | 15:04 |
| JayF | I think with my ironic hat on, it's ok | 15:04 |
| rpittau | yeah I understood :) | 15:04 |
| JayF | if I go put on my TC hat and go look at policy | 15:04 |
| JayF | we might be a little speedy | 15:04 |
| * JayF goes reading | 15:04 | |
| rpittau | well we should've not even mentioned that then | 15:04 |
| JayF | hah, explicitly it's correcet thing to do | 15:05 |
| JayF | https://docs.openstack.org/project-team-guide/deprecation.html | 15:05 |
| JayF | even if it still uses the old tick/tock | 15:05 |
| JayF | it specifically says you can remove something in the "tock" release that was deprecated in the "tick" release, using the exact logic I just did | 15:05 |
| JayF | thank you for playing trust, but verify this morning with me :D | 15:05 |
| JayF | basically it seems like with slurp, anything deprecated this release (for instance) couldn't be removed until 2025.2, because that deprecation has to be released in a slurp release | 15:06 |
| rpittau | ok, I got it | 15:09 |
| *** dtantsur_ is now known as dtantsur | 15:12 | |
| JayF | https://review.opendev.org/c/openstack/ironic/+/915441/ can we land this? it's passing, any existing comments addressed, and I'd like to cash in this win :D | 15:24 |
| JayF | (that is ARM Devstack stuff for cid ) | 15:24 |
| rpittau | JayF: I was looking at it, just checking a couple of things but should be fine | 15:24 |
| JayF | if any of it can be followed up, please land it and I'll ensure the followups get done | 15:25 |
| rpittau | yes, of course | 15:25 |
| * dtantsur probably won't get in the way | 15:26 | |
| JayF | dtantsur: I think all your review comments were good and have been addressed, fwiw | 15:27 |
| rpittau | there's probably something to change in the devstack guide, but we can take that with the rest of the docs change | 15:27 |
| dtantsur | JayF: it's still a ton of repetition in the already unmanageable devstack lib... | 15:28 |
| dtantsur | and the MACHINE_TYPE handling is confusing | 15:28 |
| dtantsur | but also, that's devstack, and I don't really care | 15:28 |
| JayF | I don't understand the confusion over machine type, the rest other issue is more ... please don't charge a decade of tech debt to one of our newest contributors :D | 15:28 |
| dtantsur | We add a new variable for the machine type that has a value incompatible with ARM | 15:29 |
| JayF | that is set for the default for x86 | 15:29 |
| JayF | aiui | 15:29 |
| JayF | just like all the others are | 15:29 |
| dtantsur | which then requires contributors to set it to the magical incantation of "virt-6.2" | 15:29 |
| dtantsur | which requires your famous decoder ring :) | 15:29 |
| JayF | oh, do we not default it correctly | 15:29 |
| dtantsur | dunno, it's still in the contributor guide? | 15:30 |
| JayF | heh, I think it's unneeded but docs are bad | 15:30 |
| JayF | I will look at this specifically with cid this afternoon, we ahve a pairing session | 15:30 |
| JayF | I was thinking re: improving devstack | 15:30 |
| rpittau | I'm going to approve it, I think we can address all the docs + devstack improvement separately | 15:30 |
| JayF | we could write a devstack plugin, a MUCH simpler one, for sushy-tools/vpdu/vbmc and have those installed separately | 15:30 |
| JayF | to get some of the details out | 15:30 |
| JayF | but I suspect the devil of doing that is in the details | 15:31 |
| dtantsur | Left a couple of comments on the documentation specifically (since it's what I care about the most) | 15:31 |
| JayF | ack; I'll make sure those get addressed in a fast follow up | 15:31 |
| dtantsur | Thanks! | 15:32 |
| dtantsur | Note that my testing environment experience is spoiled by simply running `./bifrost-cli testenv && ./bifrost-cli install --testenv --develop` :D | 15:32 |
| JayF | Yeah; I think at some point I became the nova <> ironic driver guy | 15:33 |
| JayF | and that one just snuck up on me lol | 15:33 |
| dtantsur | :D | 15:33 |
| rpittau | :) | 15:33 |
| TheJulia | why am I spending a day off ripping out a driver?! | 15:33 |
| JayF | doesn't sound like a day off to me | 15:34 |
| JayF | i took yesterday afternoon off, I didn't rip out any drivers. Mainly just ate chinese buffet and bought a tie. | 15:34 |
| dtantsur | you Americans have a weird idea of vacationing.. | 15:34 |
| TheJulia | a... tie?! | 15:34 |
| JayF | TheJulia: my brother gets married in October, the groomsmen uniform is "solid color green tie, all in different shades of green", and I don't wanna be the one stuck trying to invent a new color | 15:35 |
| JayF | TheJulia: it's at some lodge up in Banner Elk, NC. Gonna be beautiful, I think. | 15:35 |
| TheJulia | nice! | 15:36 |
| TheJulia | and that is a good reason to get a tie :) | 15:36 |
| JayF | Oh hey, my talk from CERN, I did a version for youtube and I'm gonna flip it public. | 15:37 |
| JayF | I'm going to start doing weekly short videos on Ironic stuff, too | 15:37 |
| JayF | https://www.youtube.com/watch?v=FUGB2e3XP0g (the 10 years of Ironic features talk from CERN, v1.1) | 15:38 |
| * cid Did I really just see ARM CI in the gates :D | 15:41 | |
| rpittau | cid: you did! great job there! :) | 15:42 |
| cid | I can hardly take that win alone, thanks for the reviews and assistance JayF, TheJulia, rpittau, dtantsur, (will def be following up based on your latest reviews) | 15:45 |
| JayF | You're stuck now, my first patch was over 10 years ago and I still haven't escaped ;) | 15:46 |
| cid | lol | 15:47 |
| rpittau | good night! o/ | 16:09 |
| JayF | o/ | 16:10 |
| cardoe | JayF: that sounds like a perfectly good day off! I support you. | 16:10 |
| cardoe | dtantsur: sometimes you just wanna sit there and watch the paint dry after a lot of hectic days | 16:11 |
| dtantsur | possibly :) I usually prefer watching something green and alive or something made of rock and very tell :) | 16:12 |
| opendevreview | Dmitry Tantsur proposed openstack/ironic master: Documentation: migration guide from inspector https://review.opendev.org/c/openstack/ironic/+/922089 | 16:41 |
| dtantsur | This is the last thing I wanted to do before deprecating inspector ^^^ | 16:41 |
| dtantsur | a careful look is appreciated, especially now that we're trying to improve the docs :) | 16:41 |
| opendevreview | Julia Kreger proposed openstack/ironic master: WIP: Remove deprecated idrac wsman driver interfaces https://review.opendev.org/c/openstack/ironic/+/922340 | 16:54 |
| TheJulia | Okay, I'm going to use the rest of the day. ^ was a bit painful, but it is a weird removal, please take a look when you have time | 16:55 |
| cid | 👍 https://www.youtube.com/watch?v=FUGB2e3XP0g | 16:58 |
| opendevreview | Merged openstack/ironic master: Remove ibmc hardware type https://review.opendev.org/c/openstack/ironic/+/922259 | 16:59 |
| opendevreview | Merged openstack/ironic master: Provision ARM (aarch64) fake-bare-metal-vms https://review.opendev.org/c/openstack/ironic/+/915441 | 16:59 |
| opendevreview | Verification of a change to openstack/ironic stable/2023.1 failed: fix: Fix class typo for portgroup. Portgroup instead of PortGroup https://review.opendev.org/c/openstack/ironic/+/922252 | 18:20 |
| JayF | It looks like we are unable to run without ipmitool installed even if ipmi-related interfaces/hardware-types are disabled | 19:36 |
| opendevreview | Jay Faulkner proposed openstack/ironic master: Update ironic-local-dev-guide for single-process https://review.opendev.org/c/openstack/ironic/+/922348 | 20:08 |
| JayF | nevermind, found it | 20:15 |
| opendevreview | Jay Faulkner proposed openstack/ironic master: Update ironic-local-dev-guide for single-process https://review.opendev.org/c/openstack/ironic/+/922348 | 20:17 |
| JayF | ^^ vendor interfaces had to be updated to fake, too | 20:17 |
| JayF | although we could probably make that error a lot less angry if ipmitool driver wasn't dead | 20:17 |
| * JayF notes we loaded up cid's runbooks WIP change into a local dev env and tested CRUD working | 20:40 | |
| JayF | Hmmmmmmmmmmmmmmmmm | 20:47 |
| JayF | cid: I wonder if we could hook all ^^^ that up to a tox target | 20:47 |
| JayF | cid: e.g. tox -elocaldev => spins up an Ironic with those config changes | 20:47 |
| JayF | Just food for thought, that doc is a big upgrade as-is, but getting one command to run and get an ironic api going locally would maybe make life easier for oflks | 20:48 |
| cid | JayF: That will make life way way easier :( | 20:50 |
| JayF | I wonder if it's possible, but even if not, the doc updates are great (I'm working on pep8/linting failures on those now) | 20:50 |
| opendevreview | Jay Faulkner proposed openstack/ironic master: Update ironic-local-dev-guide for single-process https://review.opendev.org/c/openstack/ironic/+/922348 | 20:57 |
| JayF | heh, if I had been in my repo with pre-commit setup instead of another one I did to poke at local-dev, I woulda never pushed it wrongly | 20:57 |
| opendevreview | Merged openstack/ironic stable/2023.1: fix: Fix class typo for portgroup. Portgroup instead of PortGroup https://review.opendev.org/c/openstack/ironic/+/922252 | 20:59 |
| cid | Heh | 21:05 |
| cid | I will start off by enjoying the new discovery | 21:08 |
| cid | Then ... | 21:08 |
| cid | Good night o/ | 21:09 |
| JayF | o/ | 21:10 |
| JayF | Does anyone know if you can run our unit tests natively on mac? | 21:25 |
| * JayF is going to do a video about running tests and that would be useful to include if it works | 21:25 | |
| TheJulia | ... I've never tried | 21:28 |
| *** iurygregory_ is now known as iurygregory | 21:28 | |
| iurygregory | same =( I have a friend with a Mac, I can check if he could run the unit tests | 21:29 |
| TheJulia | I kind of gave up coding on a mac because every time you do updates, xcode wipes everything out and you have to reinstall | 21:30 |
| iurygregory | the only time I had to code on mac, was in 2010 in a project at the university, because it was an app for iOS... | 21:43 |
| JayF | Ack, I'll call that a no then | 21:56 |
| JayF | just wanted to see if someone here was doing it regularly, cool, if not, sad | 21:56 |
| JayF | I will say, I think we have a pretty vested interest in keeping them running on WSL | 21:57 |
| JayF | and I will happily consider any failures there a bug | 21:57 |
| JayF | (as they likely also reflect leaky tests) | 21:57 |
| * JayF saw the "2 RLocks were not greened" message in his ironic singleprocess locally today under python 3.12 | 22:33 | |
| JayF | I'm digging it, have seen no issues it'd be likely to cause, but still seems like worth a dig | 22:33 |
| opendevreview | Jay Faulkner proposed openstack/ironic master: Update ironic-local-dev-guide for single-process https://review.opendev.org/c/openstack/ironic/+/922348 | 22:40 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!