Tuesday, 2024-09-03

opendevreviewJay Faulkner proposed openstack/ironic master: Support Automatic Lessee from instance metadata  https://review.opendev.org/c/openstack/ironic/+/92488701:15
opendevreviewIury Gregory Melo Ferreira proposed openstack/ironic master: Firmware Update via Firmware Interface Docs  https://review.opendev.org/c/openstack/ironic/+/92696101:38
opendevreviewTakashi Kajinami proposed openstack/ironic master: Remove skip check for Python 3.6  https://review.opendev.org/c/openstack/ironic/+/92778007:06
opendevreviewAdam Rozman proposed openstack/ironic-python-agent master: WIP - root device encryption  https://review.opendev.org/c/openstack/ironic-python-agent/+/92642511:24
opendevreviewcid proposed openstack/ironic master: Upgrade pysnmp-lextudio  https://review.opendev.org/c/openstack/ironic/+/92780411:42
opendevreviewcid proposed openstack/ironic master: Upgrade pysnmp-lextudio  https://review.opendev.org/c/openstack/ironic/+/92780411:48
*** jlejeune_ is now known as jlejeune12:30
cardoeGood morning ironic12:43
TheJuliaGood morning!13:12
opendevreviewcid proposed openstack/ironic master: Upgrade pysnmp-lextudio  https://review.opendev.org/c/openstack/ironic/+/92780413:38
cardoeI hope it's okay but I closed out a few launchpad issues that said "fix committed" but now that sushy 5.2.0 is released I moved them to "fix released"13:39
cardoedtantsur: ping to release sushy-oem-idrac and potentially abandon https://review.opendev.org/c/openstack/ironic/+/90210713:43
dtantsurthanks!13:43
cardoeDid you guys want to look at bringing sushy-oem-idrac into sushy proper in the future?13:44
dtantsurIt was my idea, at least. I don't know what the others think13:44
dtantsurBefore I do the release, is anyone available to review https://review.opendev.org/c/openstack/sushy-oem-idrac/+/917021 and https://review.opendev.org/c/openstack/sushy-oem-idrac/+/917020 ?13:44
dtantsurTheJulia or JayF maybe ^^13:44
* TheJulia looks up from vim13:45
cardoehttps://review.opendev.org/c/openstack/ironic/+/926899 should be good for a workflow review or a core reviewer. That would have given some of my folks a friendlier message.13:46
* dtantsur does not object :)13:46
TheJuliaAny other quick reviews?13:47
cardoehttps://review.opendev.org/q/project:openstack/sushy-oem-idrac all I see that's opened.13:48
cardoeI'm working on bringing our LLDP inspector code to sushy and sushy-oem-idrac13:48
TheJuliaworkflowed13:48
cardoeBut that'll be another release.13:48
dtantsurTheJulia: thx!13:49
opendevreviewMerged openstack/sushy-oem-idrac master: Add OEM DellAttributes to DellManagerExtension  https://review.opendev.org/c/openstack/sushy-oem-idrac/+/91702113:50
opendevreviewJulia Kreger proposed openstack/ironic-python-agent master: WIP: Provide operator an idea why the deploy failed  https://review.opendev.org/c/openstack/ironic-python-agent/+/92782313:51
TheJuliaSo on the subject of 4k block devices: what do folks think about ^13:51
dtantsurTheJulia: generally in favour, although:13:53
dtantsur$ sudo file /dev/nvme0n1p113:53
dtantsur/dev/nvme0n1p1: block special (259/1)13:53
dtantsurdoes not seem to match what you expect?13:53
cardoeYeah I'm a +1 on better error messages / details.13:54
opendevreviewMerged openstack/sushy-oem-idrac master: Added method for getting kvm session  https://review.opendev.org/c/openstack/sushy-oem-idrac/+/91702013:56
cardoeyour error message says "looing" and I'm thinking that's Freud coming out in how you feel about 4k blocks13:56
* dtantsur learns new English words nearly daily, lol13:57
dtantsurcardoe: here goes https://pypi.org/project/sushy-oem-idrac/6.0.0/14:06
cardoeawesome. thank you14:06
TheJuliadtantsur: nvme is... special that way14:08
TheJuliaI've not figured out what to do with that14:08
cardoeSo I know we commit the fake redfish json data from their spec for testing. How would you folks feel if I scrapped a real box as well?14:08
TheJuliasince it *should* return raw data on the target device14:09
TheJuliap1 is also the partition14:09
dtantsurcardoe: it's probably a copyright issue14:09
dtantsurjanders actually maintains a repo with scrapped real boxes internally, but I doubt we can put something like that in an opensource repo14:09
opendevreviewDerek Higgins proposed openstack/ironic master: Set node "alive" when inspection finished  https://review.opendev.org/c/openstack/ironic/+/92782814:09
opendevreviewDmitry Tantsur proposed openstack/sushy-oem-idrac master: Replace github links in README  https://review.opendev.org/c/openstack/sushy-oem-idrac/+/92782914:09
dtantsura trivial (and sad) change to approve ^^^14:09
TheJuliaapproved14:10
TheJuliacardoe: Freud might be coming out, but I was also messaged by folks while writing just that for dates on 4k devies to be "fully supported"14:11
cardoeSince we're talking sushy, I'm not sure if https://review.opendev.org/c/openstack/sushy/+/927670 is correct but it would fix the issue for that user.14:16
dtantsurcardoe: hardware vendors and specifications, right? :-/14:17
TheJuliadtantsur: so I *could* just copy off the first megabyte of data from the nvme device using dd and file that14:17
TheJuliathat works like a charm to detect a filesystem14:18
dtantsurcardoe: I don't mind this change, but maybe we should apply it consistently to all resources?14:18
dtantsurTheJulia: lol, ship it!14:18
TheJuliaoh14:20
TheJuliaadd -s to the command and it should be good14:20
TheJuliayup, that works14:21
TheJulia"treat special files as ordinary files"14:21
dtantsuryep14:30
dtantsurbtw this is how the UEFI partition looks:14:30
dtantsur$ sudo file -s /dev/nvme0n1p114:30
dtantsur/dev/nvme0n1p1: DOS/MBR boot sector, code offset 0x58+2, OEM-ID "mkfs.fat", sectors/cluster 8, Media descriptor 0xf8, sectors/track 32, heads 64, hidden sectors 2048, sectors 1048576 (volumes > 32 MB), FAT (32 bit), sectors/FAT 1024, reserved 0x1, serial number 0xb83a89ab, unlabeled14:30
dtantsurTheJulia: not sure if you handle this ^^14:30
TheJuliathat is your first partition14:30
TheJuliathe check should be looking at the overall device14:30
dtantsurI mean, you're checking for ext4, xfs, btrfs and ntfs14:31
dtantsurdo you want to check for FAT32 and ISO 9660?14:31
TheJuliaHmm... I guess I could add "mkfs.fat" to it14:31
dtantsurI can easily imagine someone accidentally writing an ISO image, for instance14:31
TheJuliavfat as in fat32, at least locally came back as "filesystem data"14:31
TheJuliaI'll add on to it14:32
dtantsurwanna be fancy, also add Linux Logical Volume Manager14:33
opendevreviewcid proposed openstack/ironic master: Upgrade pysnmp-lextudio  https://review.opendev.org/c/openstack/ironic/+/92780414:33
TheJuliaoh, yes14:33
TheJuliaif you have one handy!14:33
dtantsur$ sudo file -s /dev/nvme0n1p314:33
dtantsur/dev/nvme0n1p3: LVM2 PV (Linux Logical Volume Manager), UUID: hn3P2a-hksA-UlUQ-UFmW-6wuZ-WeXP-5MeETY, size: 47902831411214:33
cardoedtantsur: so in some places we use "identity" and in some places we use odata.id14:33
dtantsurconsistency \o/14:34
cardoeI was thinking odata.id is more correct14:34
cardoeSo I was gonna update to that.14:34
cardoeI was talking to JayF about adding pre-commit from ironic (and looking at what some other projects do)14:34
cardoeAnyway, I'm happy to make it consistent and abandon that change. I was just proposing that for 1 user.14:35
dtantsuras I said, I don't mind working around a real world problem14:35
dtantsurjust wanted to give consistency a thought14:35
cardoeTechnically the "Id" and "Name" field are required on all Redfish models. But we don't require them on a lot and the links are suppose to be via odata.id so I don't see why "Id" and "Name" need to be required.14:35
dtantsurI don't see why Id is even needed..14:36
dtantsurRedfish is wildly inconsistent in requiring or not requiring Name14:36
dtantsurI've literally fixed one instance in the RAID code recently14:36
cardoeAbsolutely. So lemme do a bigger consistency clean up and we can abandon that one change (unless you wanna land it for that user with the bug).14:36
dtantsurUp to you14:37
cardoeSo the spec says Name is required but their own test data misses Name a large percentage of the time.14:37
TheJuliaso, I wonder how many bioses would actually boot an ISO9660 filesystem written to a disk14:37
cardoeI guess for the user's sake lets land it and then I'll work on the bigger clean up14:37
cardoeI have a convo later this week about Dell testing with the Ironic interop profile.14:38
dtantsurTheJulia: hmmmmmmmm. good point.14:38
TheJuliadtantsur: *today* that *just won't work*14:38
TheJuliaso, I could see checking and erroring, for now14:38
TheJuliabut I wouldn't object to a slightly smarter path14:39
TheJuliathen again....14:39
TheJuliathere is no guarentee the operator's ISO and onboard logic will work properly in that sort of case as well14:39
opendevreviewDoug Goldstein proposed openstack/sushy master: WIP: add Port resource  https://review.opendev.org/c/openstack/sushy/+/92783814:40
cardoeSo no tests for that but just to get an idea of what I was aiming for.14:41
cardoeThere's LLDP info in those hills. So want to use that for the redfish inspector.14:41
dtantsurIt's even present in actual real hardware?14:42
cardoeUnfortunately Dell doesn't use the standardized fields and uses their own OEM section. So I'll have to add that into sushy-oem-idrac14:42
dtantsurahhh, of course14:42
cardoeoh yeah my non-Dell stuff returns LLDP in those fields.14:42
dtantsur\o/14:42
dtantsurThis is really nice, I'd never expect it14:42
cardoePart of my convo this week is to waggle a PO in Dell's face if they fix some of this stuff.14:42
dtantsurIf we get it working, this will significantly reduce the need for in-band inspection14:43
dtantsurcardoe++14:43
TheJuliawheeee, by default file only detects ExFAT if you add -k to it14:43
TheJuliaotherwise it just goes "this is an dos mbr"14:43
cardoeSo our goal is to make the out of band inspector just as feature full as the in band inspector.14:43
cardoeI'm just not sure the best way to upstream this.14:43
cardoeBecause I don't know if upstream really wants to see "idrac-redfish" inspector interface make a comeback.14:44
cardoeOr if we merge sushy-oem-idrac into sushy proper14:44
dtantsurThe way things work now, you'll need to make idrac-redfish come back14:44
dtantsurHow we want to move forward, is a great PTG discussion IMO14:45
cardoeIf we just make interfaces like today we've got https://opendev.org/openstack/sushy/src/commit/033287f8c2d254cd3a51dd2ba2e414e04311eb16/sushy/resources/system/ethernet_interface.py#L5914:45
opendevreviewJulia Kreger proposed openstack/ironic master: docs: Add context around asynchronous device initialization  https://review.opendev.org/c/openstack/ironic/+/92751814:45
dtantsurWe already have quite a few workarounds for Supermicro, Lenovo and Huawei right in sushy14:45
cardoeOkay. Next PTG I'll add it as an item.14:46
dtantsur++14:46
cardoeI'm happy to figure out a way to donate hardware to test against as well.14:46
cardoeHence why the ask around real data.14:46
dtantsuran upstream 3rd party CI could be awesome14:47
TheJuliawe, unfortunately, have also seen some vendors, dell included, changing stuff between releases where they didn't think anyone would notice14:55
cardoeYep. I plan to hold their feet to the fire.14:58
cardoeI had a decently sized PO in my hands.14:58
opendevreviewMerged openstack/ironic master: Better handle missing inspection_network  https://review.opendev.org/c/openstack/ironic/+/92689914:58
TheJuliahehe :)14:58
cardoeThey've made a number of engineering resources available to me and setup some calls.14:59
cardoeThey're at least going to have to listen to me give them a disappointed dad lecture.15:00
opendevreviewMerged openstack/sushy-oem-idrac master: Replace github links in README  https://review.opendev.org/c/openstack/sushy-oem-idrac/+/92782915:02
dtantsursounds fun :D15:03
cardoeIf you guys are on a merge kick... https://review.opendev.org/c/openstack/sushy/+/927444 https://review.opendev.org/c/openstack/sushy/+/927598 are two small ones.15:07
cardoeand https://review.opendev.org/c/openstack/sushy/+/92699515:07
dtantsurAny chances for a 2nd +2 on https://review.opendev.org/c/openstack/ironic-tempest-plugin/+/925981 and https://review.opendev.org/c/openstack/ironic/+/926647?16:36
groundnutyHello, I'm trying to create two software raids using ironic-python-agent. This is a target_raid_config that is applied: {'logical_disks': [{'controller': 'software', 'physical_disks': [{'serial': 's== S664NN0W200258'}, {'serial': 's== S664NN0W200257'}], 'raid_level': '1', 'size_gb': 447}, {'controller': 'software', 'physical_disks': [{'serial': 's==16:52
groundnutyBTYJ2296059C1P9CGN'},{'serial': 's== BTYJ22960A7H1P9CGN'}], 'raid_level': '1', 'size_gb': 'MAX'}]}16:52
groundnutyI would expect two mdadm raids to be created each having 2 disks. While the first one is created, the second one for some reason uses wrong index for partitions: 16:54
groundnutymdadm --create /dev/md1 --force --run --metadata=1 --level 1 --name md1 --raid-devices 2 /dev/sdh2 /dev/sdg216:54
groundnutythere is no /dev/sdh2 but I assume there is /dev/sdh116:54
groundnutythe guilty party is this line of code that for reasons I cannot understand assumes that each new raid will have a higher partition number: https://github.com/openstack/ironic-python-agent/blob/master/ironic_python_agent/raid_utils.py#L22216:55
groundnutyplease advice, if it's me who maybe does not understand the API or is it a bug and my usecase is not supported16:56
TheJuliahmm16:57
TheJuliaSo I *know* there are specific restrictions around software raid support16:57
TheJuliaI16:58
TheJuliaI'm not sure two mirror sets are in that matrix of what it will do out of the box16:58
TheJuliaBut, it has been a long time since I've looked at that code. Largely CERN folks did that code to support their use cases and I've had a couple customers leverage it as well, but not as a mirror set for a second volume.16:59
TheJuliahmm, I'm not sure I understand exactly what the raid_utils is trying to do off hand17:00
* TheJulia also has a migraine brewing17:00
opendevreviewDerek Higgins proposed openstack/ironic master: Set node "alive" when inspection finished  https://review.opendev.org/c/openstack/ironic/+/92782817:00
groundnutyI come come from https://github.com/metal3-io/baremetal-operator usecase and we intend to run k8s clusters using metal3, our servers came with 2 sets of disks - one for boot and second for the rest. Hence the need for two raids.17:02
groundnutyI know from the longs that for the first raid when size_gb is set to 447 it runs: parted /dev/sdg -s -a optimal -- mkpart primary 551MiB 480GiB17:03
groundnutyso the /dev/sdg1 is created and the first raid is also created17:03
TheJuliagroundnuty: I think the coded intent was the second set was RAID5, fwiw17:10
TheJuliathat does sound correct, fwiw17:11
JayFI'd also suggest generally, if I had your problem, I'd have Ironic setup the root disk raid set and provision the second raid set in cloud init17:22
JayFdtantsur: I dealt with your concerns on https://review.opendev.org/c/openstack/ironic/+/924887 if you want to revisit; TheJulia also had a +2 on the previous version.17:24
JayFWe've landed the Nova side of this so I'd be keen on getting the feature fully landed17:24
TheJuliaI'm pretty sure we documented the weird edges on the software raid stuffs, but maybe we didn't?!17:25
dtantsurOn my queue for tomorrow17:25
JayFack, ty17:25
opendevreviewMerged openstack/ironic-tempest-plugin master: A simple standalone test for in-band inspection  https://review.opendev.org/c/openstack/ironic-tempest-plugin/+/92598117:49
opendevreviewMerged openstack/ironic master: Enable the inspection test in the redfish standalone job  https://review.opendev.org/c/openstack/ironic/+/92664717:49
opendevreviewJulia Kreger proposed openstack/ironic-python-agent master: WIP: Provide operator an idea why the deploy failed  https://review.opendev.org/c/openstack/ironic-python-agent/+/92782317:56
TheJuliadtantsur: ^ for you to take a look at tomorrow17:56
JayFI like that change17:59
JayFwill poke it with a sharp stick after the TC meeting17:59
JayFI suspect I can create some extra cases for us to catch :D18:00
TheJuliaI'm just sitting here trying to figure out how to make it easier to deal with those pesky 4k devices18:01
TheJuliasince apparently in my customer's case, there is just no way to reset the raid controller to anything else18:01
JayFsomeone go tell the hdd manufacturers to put it in metadata someplace standard :/18:01
TheJuliawhich.. sucks18:01
TheJuliaeh, in this case, go back in time18:01
TheJuliaand *fix* it so we start GPT at byte 51218:02
TheJulia*not* block 118:02
JayFI mean, at a minimum, documentation around which controllers behave that way would be a start at all18:02
JayFI'm assuming that doesn't work on !4k18:02
JayFthe 512 byte trick, I mean18:02
TheJuliayeah, no18:03
TheJuliaand by fix it18:03
TheJuliaI mean, fix the standard18:03
JayFyes18:03
TheJuliaso, go back and time and whack people upside the head with clue-by-fours from the future18:03
JayFI do have a bit of a platform18:03
JayFcould make a video about it or something18:03
TheJulia*this* *will* *cause* *pain*18:03
JayF"GR-OSS moment in hardware" 18:04
* TheJulia takes a short break18:05
JayFhttps://news.ycombinator.com/item?id=41431244 I think most folks here would find this interesting18:33
JayFtl;dr HN discovered IPMI exists18:33
opendevreviewcid proposed openstack/ironic master: Upgrade pysnmp-lextudio  https://review.opendev.org/c/openstack/ironic/+/92780419:18
mnaseri'm trying to find docs for spine-leaf (l2 per rack) with ironic + ovn19:38
mnaseri cant find much, is it even possible, my concern here is how to dhcp would work19:39
JayFI assume you've seen the big Ironic OVN doc?19:39
JayFhttps://docs.openstack.org/ironic/latest/admin/ovn-networking.html19:40
mnaseryeah, i was on that page, i can successfully use it over a l2 network19:40
mnaserleads to https://docs.openstack.org/neutron/latest/admin/ovn/baremetal.html19:41
JayFLet me put it this way: all I know about OVN is in that document, which Julia wrote :D 19:41
mnaserlool19:41
JayFso I just wanted to make sure you had seen it, but I can't be helpful beyond that19:41
JayFMaybe she'll come around and have an idea? 19:42
JayFbut I suspect you may be trailblazing19:42
mnasernow im wondering if i cant use ovn if i am doing relay dhcp and might do neutron-dhcp-agent19:42
JayFI think there was some bug around OVN and baremetal dhcp19:42
JayFbut I don't remember what it was19:42
JayF> As of the 2023.2 Release of Ironic, The Ironic project can confirm that OVN’s DHCP server does work for PXE and iPXE operations when using IPv4, OVS version 3.11, and OVN version 23.06.0. 19:42
JayFso I guess i t kinda works at least19:42
JayFnot with v6 though, I think that might have been the limitation I'm remembering19:42
mnaseryeah no i can confirm it works fine directly with ovn in the same l2 network19:45
mnaserbut unsure on how we can make it work over another network19:45
mnaseri am wondering about using the `dnsmasq` driver though19:46
mnaserftr i think this is more of a neutron issue than ironic for what its worth19:51
TheJuliaPossibly semi-trail blazing20:00
TheJuliaIPv6, I believe landed in ovn later, I think the question is if it supports dhcp relays at all20:05
TheJuliahjensas might know20:05
*** ubuntu is now known as Guest239920:18
Guest2399JayF: that seems like a resonable wokradound, tho the resulting configuration will be much less clear ;-(20:25
JayFGuest2399: you lost your name, friend :)20:26
JayFGuest2399: I always took the approach of "OpenStack provides raw material of an OS and a root device" and then any config on top was done after the fact... mainly because the array of things people want to do with "storage disks" is MUCH larger than the array of things people want to do with "root disks"20:26
*** Guest2399 is now known as groundnuty20:30
JayFdtantsur: cardoe: I'm punting on enum-ifying stuff in Ironic. Given behavior changes between e.g. BootDevices.LOL and boot_device.LOL and BootDevices.LOL.value  ... I just think it'll be a lot of churn for dubious value ... but it's also possible I'm overthinking this :)20:31
cardoeYeah punt away.20:32
JayFI was working on a refactoring change to do it, on top of my lessee change, just a lot of code churn to make it look actively worse20:32
cardoeSo some of the differences are cause you might want to use StrEnum instead of regular Enum.20:33
cardoeI know Sean brings up a point about frozen enums but a lot of that is mitigated via static checkers like mypy and even flake8.20:34
JayFwell, freezing it is trivial20:36
JayFI have that solved20:36
JayFbut StrEnum sounds interesting20:36
JayFor even RefrEnum()20:37
JayFhttps://docs.python.org/3/library/enum.html#enum.ReprEnum20:37
JayFthank you for the pointer!20:37
* cid 's EOD. o/20:41
JayF\o20:42
JayFcardoe: This seems to be happier for our purposes. For the few times we need the list of items in an enum, we can call Blah.list() https://www.irccloud.com/pastebin/LDlP3VmS/21:06
JayFI know I could reduce that down into one class def, but I think the way it's written makes it more clear what's happening21:07
TheJuliaAnyone seen anything like this where Tianocore says "nope"21:09
TheJuliahttps://usercontent.irccloud-cdn.com/file/VxBBU0Wb/centos9-not-secureboot.png21:09
JayFThat's a new one on me21:09
JayFmight wanna ask in -nova?21:10
JayFThey might have a better idea but idk21:10
TheJuliaOh, I think i grok it now21:13
JayF?21:18
groundnutyJayF: I was hoping to find the world of infrastructure automation ready for declarative gitops where you can setup your server with single yamls :-)21:51
groundnutyJayF: as for cloud-init it does not support mdadm natively https://github.com/canonical/cloud-init/blob/5a74d19d066e932c6d8925c858acf92b1406654b/doc/examples/cloud-config-disk-setup.txt#L12121:51
JayFgroundnuty: I just saw a great clip from my next podcast episode, where Dejan (a guy who works on K8s) gave this great quote: Devops is just a big box of yaml :D 21:51
groundnutyso I guess to do anything one would have to write custom scripts/one-liners ;-(21:51
JayFgroundnuty: When doing this in the past, I used bash21:51
JayFhttps://github.com/jayofdoom/onmetal-fast-docker21:52
JayFThe timestamps on that repo will tell you how dusty my knowledge in this specific space is LOL21:52
JayFgroundnuty: seriously though, it's just a matter of where the lines are drawn: OpenStack is more about getting you a platform to put things on, and then using config management, image management, etc for config21:53
JayFIn other solutions, they draw the lines in different places21:53
JayFFor instance, my downstream uses Ironic via Nova via Terraform :)21:53
JayFso their users get the "write yaml -> recieve infra" you just need another layer (also rip Terraform, long live opentf)21:53
groundnutyJayF: in my case baremetal-operator will be the yaml layer, embeding bash in yaml while doable is not perfered :-)21:55
JayFAhh. I wonder if dtantsur (author of said operator) would have any ideas that might be more k8s-flavored :)21:55
groundnutyI looked at the pull request that introduced raid - it's very bare bones and supports small portion of ironic features ;-(21:56
groundnutyin that baremetal-operator reapo I mean21:56
JayFyeah, the operator is extremely new22:06
JayFDmitry started on it a few months back iirc22:06
JayFI'm sure he'd love patches if you can find a way to map in more of the interface22:06
opendevreviewJulia Kreger proposed openstack/ironic-python-agent master: WIP: Provide operator an idea why the deploy failed  https://review.opendev.org/c/openstack/ironic-python-agent/+/92782322:07
cardoeThat’s a good solution JayF.22:33
JayFif you get one second22:34
JayFI'm almost done with boot_devices and boot_modes22:34
JayFwas going to stop there and push a WIP/Prototype22:34
cardoeSee and I’m using GitOps to ensure we have an Ironic, Neutron, Nova that is in a good state.22:34
JayFbefore mechanical-turking the rest of it22:34
JayFDevops is a big box of yaml.22:34
cardoeAnd 20 years ago life was a big box of XML.22:36
JayFno, I lived in the jsoniverse22:41
JayFthe great schism 22:41
mnaseri found a thing22:44
mnaserhttps://bugs.launchpad.net/neutron/+bug/169248622:44
mnaserthis could be very handy for ironic folks :)22:44
opendevreviewJay Faulkner proposed openstack/ironic master: WIP/PoC: Move constants to enum, constants module  https://review.opendev.org/c/openstack/ironic/+/92787922:45
JayFcardoe: dtantsur: ^ let me know how you all feel about this direction22:45
cardoemnaser: agreed. Almost wanna make a k8s friendly dhcp server. I’m the one that suggested the OSH operator that Vlad pinged you about btw.22:51
mnasercardoe: oh nice!  yeah, well ironic already has a dnsmasq dhcp driver fwiw :P22:52
cardoeYeah but dnsmasq is well… dnsmasq.22:53
mnaserhaha.. yep22:53
mnasercardoe: i have started and decided not to write an OSH operator about 15 times now because ENOTIME22:54
cardoeThat’s how I feel.22:54
mnaseri did end up with https://github.com/vexxhost/openstack-service-operator and learned about https://github.com/k-orc/openstack-resource-controller after22:54
mnaserto get rid of those pesky jobs at least :)22:56
cardoeI saw yours. That’s roughly what I wanted to do. Just get rid of the bootstrap scripts basically.22:56
cardoeYeah bootstrap and jobs.22:56
mnaserfunny how same frustrations develop over time aross operators :P22:56
cardoeAbsolutely22:57
cardoeWhen I get some cycles I’m going to make the secrets in OSH work by ref.22:58
mnaseryeah fitbeard did do some cool work around that with the idea of potentially using vault and dynamic secrets, that would be cool as heck22:59
cardoeI wish keystone wasn’t so painful with OIDC as well.23:05
TheJuliamnaser: Ahh yes, except that was dhcp-agent, not ovn23:09
TheJulia(referring to the launchpad link earlier)23:09
mnasercardoe: we've mostly solved that with keycloak native + keystoneauth-websso23:11
mnaserTheJulia: yeah, i dont think there's actually a way with non-ovn because there's no actual ip to send that traffic too23:11
TheJuliaThat is... saddening23:11
opendevreviewMerged openstack/ironic-python-agent master: Fix series in release notes  https://review.opendev.org/c/openstack/ironic-python-agent/+/92699223:18
opendevreviewMerged openstack/sushy master: Fix versions in release notes  https://review.opendev.org/c/openstack/sushy/+/92699523:24

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!