Friday, 2023-03-03

zouyu[m]Hello, do we have any thoughts to support specifying a URL for verify_ca, rather than just a local path?... (full message at <https://matrix.org/_matrix/media/v3/download/matrix.org/vNTYAPHdckzvzSCesnSGOGGG>)02:10
TheJuliazouyu[m]: o/05:01
TheJuliazouyu[m]: ... That seems reasonable to me, would you be willing to propose that as a change to the code base?05:01
TheJuliastevebaker[m]: dtantsur: rpittau: we likely need to go through the settings and consider the same sort of thing for *anything* which could be a file path on the conductor... maybe with the exception of course as I type this I think there is a case where we wouldn't want to, but I'm too tired and depressed right now to actually recall what that setting is/was05:03
TheJuliaw/r/t zouyu[m]'s question05:04
*** fenggw[m] is now known as GuangwenFeng[m]05:37
zouyu[m]TheJulia:  Thanks for your reply. Yes, I plan to submit the proposal to storyboard.06:31
TheJuliazouyu[m]: it may just be easier to do it in a gerrit change, since it seems a bit obvious.06:45
zouyu[m]TheJulia: Thanks! Got it.06:51
dtantsurrpittau: re https://review.opendev.org/c/openstack/ironic/+/863873, wdyt about merging it with a reference to your github?09:16
rpittaugood morning ironic, happy Friday! o/09:21
rpittauJayF: awesome, thanks for taking care of that 09:21
rpittaudtantsur: sounds good to me, I'll reenable the other jobs and clean it a little first 09:22
rpittauAnd I'll have to remember to not close my branch 09:23
dtantsurtrue :)09:32
opendevreviewDmitry Tantsur proposed openstack/ironic bugfix/21.3: Configure CI for bugfix/21.3  https://review.opendev.org/c/openstack/ironic/+/87626409:45
opendevreviewDmitry Tantsur proposed openstack/ironic bugfix/21.3: Configure CI for bugfix/21.3  https://review.opendev.org/c/openstack/ironic/+/87626409:47
dtantsurrpittau: FYI ^^09:48
rpittaudtantsur: thanks for that, going to review ASAP09:57
rpittaummm with all these numbers I'll go crazy(er)10:00
dtantsuryeah10:04
opendevreviewMerged openstack/ironic bugfix/21.3: Do not move nodes to CLEAN FAILED with empty last_error  https://review.opendev.org/c/openstack/ironic/+/87617310:10
kubajjGood morning Ironic o/10:12
opendevreviewMerged openstack/ironic bugfix/21.0: Do not move nodes to CLEAN FAILED with empty last_error  https://review.opendev.org/c/openstack/ironic/+/87617610:15
dtantsurkubajj: morning! JFYI I've seen your email, planning to work on a response over the course of the day. Should I simply reply to you or copy anyone?10:24
kubajjdtantsur: thanks, just reply to the email, I will then extract quotes into the dissertation to do something like a qualitative evaluation 🙂10:25
rpittauquick review if anyone has a minute, thanks! https://review.opendev.org/c/openstack/bifrost/+/87263410:28
dtantsur+210:30
rpittautnx!10:36
opendevreviewRiccardo Pittau proposed openstack/bifrost master: Fix enabling epel repo for rpm distributions  https://review.opendev.org/c/openstack/bifrost/+/87592911:31
rpittauJayF: as soon as virtualpdu has been moved we should request a new release, or can we even do it now?11:35
iurygregorygood morning Ironic11:40
dtantsurrpittau: projects under x/ are not managed by the release team11:42
dtantsurso if you have ACL for pypi, you can release. if not, well. another round of conversations :)11:43
dtantsurgood news: openstackci is a maintainer of the pypi project11:43
dtantsurso you should be able to release11:43
dtantsurHmmmm, why are we trying to PXE-boot an ISO in the CI?14:13
iurygregoryO.o14:14
iurygregorywrong config in the job?14:14
dtantsurmmm, no, it's intended apparently. but with redfish we're supposed to do virtual-media...14:15
TheJuliais this a tempest job on a non-virtual-media job?14:17
dtantsurTheJulia: standalone14:17
opendevreviewOleksandr Kozachenko proposed openstack/networking-generic-switch master: aruba: Override check string for config mode  https://review.opendev.org/c/openstack/networking-generic-switch/+/87636014:18
TheJuliaso yeah, that is intentional then since it is not the explicit virtual media job I think14:18
opendevreviewDmitry Tantsur proposed openstack/ironic-tempest-plugin master: Split the ramdisk ISO test  https://review.opendev.org/c/openstack/ironic-tempest-plugin/+/87636114:18
dtantsurTheJulia: my guess ^^^14:18
TheJuliayeah, that makes sense to do14:19
dtantsurlet's see what the CI says14:20
opendevreviewOpenStack Release Bot proposed openstack/networking-generic-switch stable/2023.1: Update .gitreview for stable/2023.1  https://review.opendev.org/c/openstack/networking-generic-switch/+/87636214:20
opendevreviewOpenStack Release Bot proposed openstack/networking-generic-switch stable/2023.1: Update TOX_CONSTRAINTS_FILE for stable/2023.1  https://review.opendev.org/c/openstack/networking-generic-switch/+/87636314:20
opendevreviewOpenStack Release Bot proposed openstack/networking-generic-switch master: Update master for stable/2023.1  https://review.opendev.org/c/openstack/networking-generic-switch/+/87636414:20
* TheJulia tries to wake up14:20
TheJuliaGood morning everyone14:20
rpittaudtantsur: right! And thanks, going to ask for a release and see what happens :)14:36
JayFrpittau: ++ you got to the ending I was going to suggest14:53
* TheJulia binks at the size of a newer centos stream 9 iso15:10
samuelkunkel[m]Did it get even bigger?15:10
samuelkunkel[m]Are they aiming for the 1GB? ;)15:11
TheJulia8.8GB15:12
samuelkunkel[m]hu? :D15:12
samuelkunkel[m]did they smuggle in all ubuntu releases of the last 2 years in there?15:13
TheJuliano idea...15:13
JayFI honestly gotta say again, it's tough for me to understand why we wanna be on the stream treadmill vs something like rocky :/15:13
JayFespecially given stuff like this can break us15:13
TheJuliathe breaky things actually some of us find them far earlier as opposed to upon the next major upgrade, luckily we've only seen ?2? breaks in stream one intentional changes, the other was a "rutro, revert" if memory servers15:14
dtantsurmorning TheJulia, JayF 15:14
JayFo/15:14
dtantsurrpittau: s/ask for release/make a release/ ;)15:15
dtantsurmake sure you have ACL to push tags15:15
JayFthere's a nonzero chance the ACLs are not setup for custom releases 15:15
JayFwait, they should still be15:15
JayFbecause my project-config change hasn't landed15:15
dtantsurright15:15
JayFvirtualpdu-release can cut releases15:15
JayFhttps://review.opendev.org/admin/groups/cc93c0bed1f8a435b44a06c8539b3dfb5379d0ee,members yeah we're good15:16
JayFironic-core is in virtualpdu-release15:16
JayFso you might have to do it manually but it can be done15:16
dtantsurs/might// the release team does not handle /x/ stuff15:16
JayFif I were doing it, I'd sync with releases team before just yolo-doing it, but expect the answer to be "do your own release"15:16
TheJuliayeah, they don't  handle x namespace stuff15:17
JayFthe actual move from x->openstack is likely not happening until post-release15:17
dtantsurwhich reminds me, I haven't released or touched ironic-staging-drivers for... ahemmmm....15:17
JayFeven though we are, from a governance standpoint, running virtualpdu15:17
TheJuliac'est la vie15:17
JayF(that merged yesterday afternoon)15:17
TheJuliadtantsur: I'd wonder if it makes sense to...15:17
dtantsuryay, ironic-staging-drivers does not even have stable/zed \o/ \o/15:18
TheJuliaw/r/t staging-drivers15:18
dtantsurif we do it, I'd prefer that we switch to a group ownership15:18
dtantsuri.e. bring it under ironic15:18
JayFso we have already done it15:19
JayFhttps://opendev.org/openstack/governance/commit/db8597ad9245ce2c115b4d5140a6d81d63b2a9af15:19
dtantsuryeah, I meant ironic-staging-drivers15:19
JayFoh. 15:19
JayFI would not be in favor of us adopting that...15:20
dtantsursorry, side-tracking. just remembered that it's been dead since zed15:20
dtantsurrpittau and myself cannot keep it alive15:20
dtantsurif we're not taking it in ironic, I suggest adopting the wakeonlan driver and dropping everything else15:20
rpittauforgot about that :/15:20
JayFLet me ask it this way: are you all trying to keep it alive out of courtesy? RH/business requirements? Something else?15:20
dtantsurrpittau: no blame here, we're terribly busy, both of us15:20
JayFthe idea is that like, it's in staging-drivers because there was nobody to maintain it15:20
dtantsurJayF: out of courtesy. OpenShift could not care less.15:21
JayFso it seems like if it doesn't get maintained, that's probably OK? Someone using it should step up and help if they care15:21
dtantsurOSP used to use oVirt, probably not any more15:21
JayFat a certain point we only have so many brains and hands and we have to point them at the primary concerns of the project15:21
TheJuliaI'm starting to wonder if anyone actually uses any of those drivers at this point15:21
dtantsurI could argue that having a WakeOnLan driver in-tree may be pretty cool15:21
dtantsurfor people who don't have fancy hardware at all15:21
TheJuliadunno about iboot, maybe WOL...15:21
dtantsureverything else is a pure burden for me15:21
JayFI think that's neat, I struggle with it being hard to test. I don't have strong opinions about any individual driver in there; I do have opinions about you all throwing your time into an unused black hole lol15:22
dtantsurto be clear, that's all the code: https://opendev.org/x/ironic-staging-drivers/src/branch/master/ironic_staging_drivers/wol/power.py15:22
dtantsurI can live with these 200 lines not having a CI, but I understand the others may feel differently15:23
JayFMy bigger issue is that if it exists as a driver, people will expect a certain level of quality. Not being able to implement, e.g. `reboot`, seems like a serious impediment15:23
dtantsurI sincerely hope that people who know what WOL is also understand that it cannot power off15:24
dtantsurbut dunno. I don't care much in the end.15:24
JayFMy bigger concern is that like, ironic-staging-drivers exists so that we have a place for that potentially-useful code to live even when folks have abandoned it15:25
JayFif you aren't using those drivers, and don't know anyone who is, I implore you to leave it alone 15:25
dtantsurleave it alone = forget or deprecate15:25
dtantsur?15:25
JayFit's x/ namespace, right?15:25
dtantsuryes15:26
JayFlike I'd just not prioritize maintainence of it15:26
JayFwither on the vine is more or less my call15:26
dtantsurI'm not operating this way, sorry15:26
dtantsurIf I'm responsible for it, I either need to keep being responsible or to officially stop15:26
dtantsurI feel bad for not doing anything since Yoga15:26
rpittauso summarizing for virtualpdu, if I create the release patch now, and it gets acceppted, we'll have to create tags and whatever ourselves, like we do for staging-drivers ?15:26
JayFrpittau: that's our understanding, yes15:27
rpittauok, thanks15:27
JayFrpittau: they might not even accept the patch tbh15:27
dtantsurI can put up a call on the ML. If nobody volunteers, I'll deprecate the project and leave it with a warning in the docs.15:27
rpittauI'll give that a try anyway, we need a new release15:27
dtantsurrpittau: it won't be accepted until it's under our governance15:27
JayFdtantsur: ++ I'm OK with that. And if you feel strongly about WoL driver I won't -1 it or anything15:27
rpittauah :/15:27
JayFdtantsur: it is under our governance, just the location hasn't moved15:27
JayFI think releases cares about repo location, not governance15:27
* rpittau grabs a beer15:28
dtantsurJayF: they care about both, they expect the two not to conflict :)15:28
JayFwell we're going to be in the nebulous grey area for a few weeks :D 15:28
dtantsurthen you'll need to bootstrap the openstack/releases repo with the new deliverable15:28
dtantsuryeah15:28
rpittauyeah virtuapdu is not there15:28
dtantsurI'd release first, then finalize the processes (including removing the ACL from us)15:28
JayFmight be valuable to email the list, in that same thread, when we cut a release15:29
JayFit's good to be loud about how efficient we are, and this virtualpdu thing has been annoying, but we've been sprinting ever since we were handed the ball15:29
rpittauit's fun, although it might be the load of the week to talk15:31
dtantsuremail sent15:31
dtantsur(about staging-drivers)\15:31
TheJuliaso intel node-manager became datacenter manager15:32
rpittaushould we treat virtualpdu as virtualbmc? as independent I mean15:37
JayFI trust you alls' take on that. I don't have a strong opinion.15:39
* JayF afk for a few hours15:41
dtantsurI'd keep it the same way, yes15:43
rpittaubtw just found a bug in the new_release script, and filed a fix15:50
opendevreviewMerged openstack/networking-generic-switch stable/2023.1: Update .gitreview for stable/2023.1  https://review.opendev.org/c/openstack/networking-generic-switch/+/87636216:12
opendevreviewMerged openstack/networking-generic-switch stable/2023.1: Update TOX_CONSTRAINTS_FILE for stable/2023.1  https://review.opendev.org/c/openstack/networking-generic-switch/+/87636316:15
opendevreviewMerged openstack/networking-generic-switch master: Update master for stable/2023.1  https://review.opendev.org/c/openstack/networking-generic-switch/+/87636416:15
dtantsurlooking for a 2nd +2 on https://review.opendev.org/c/openstack/ironic/+/876264/ please, needed for the CI16:36
dtantsuralso https://review.opendev.org/c/openstack/ironic/+/855042 has been around since august :) 16:36
opendevreviewDmitry Tantsur proposed openstack/ironic bugfix/21.2: Fixes for tox 4.0  https://review.opendev.org/c/openstack/ironic/+/87640916:39
dtantsurthis is needed for the CI as well ^^16:39
opendevreviewDmitry Tantsur proposed openstack/ironic bugfix/21.2: Update .gitreview for bugfix/21.2  https://review.opendev.org/c/openstack/ironic/+/86782616:39
opendevreviewDmitry Tantsur proposed openstack/ironic bugfix/21.2: Do not move nodes to CLEAN FAILED with empty last_error  https://review.opendev.org/c/openstack/ironic/+/87617416:40
opendevreviewDmitry Tantsur proposed openstack/ironic bugfix/21.2: Configure CI for bugfix/21.2  https://review.opendev.org/c/openstack/ironic/+/87641016:41
dtantsursomeone just came to the metal3 slack with https://orange-opensource.gitlab.io/kanod/reference/architecture/added-value.html#bmaas16:57
dtantsurthis is curious (cc JayF TheJulia for a Friday reading)16:58
dtantsuralso https://orange-opensource.gitlab.io/kanod/reference/kiab/broker.html#kiab-broker17:00
* dtantsur is sad nothing of the ownership work is available to metal3 currently17:01
TheJulialegacy bios support only, wow17:02
TheJuliawell, inherently if you want to use a proejct-scoped user to an existing ironic...17:02
TheJuliabut it all depends on the use case and access model17:03
* TheJulia is flabbergasted that centos9 stream is still installing17:03
dtantsurit's streaming \o/17:04
TheJuliasurprisingly enough, it has 2.2GB of free ram on a 4gb VM17:06
dtantsur$ free -h17:07
dtantsur               total        used        free      shared  buff/cache   available17:08
dtantsurMem:            23Gi       1.6Gi        16Gi       297Mi       5.8Gi        21Gi17:08
dtantsurThis is with a whole bifrost running!17:08
rpittauabout bifrost, in the patch where I'm trying to fix the EPEL repo, removing and reinstalling the epel-release package does the trick17:16
rpittauI have the suspect he pkg is installed but the repos entries are purged from the original node, haven't verified it yet17:16
dtantsurask infra?17:17
rpittauyeah, it's really puzzling17:17
dtantsurwell.. after the issue with wiped tzdata or what was it?17:18
rpittauoh yes, right!17:18
rpittauin the container image17:19
dtantsuryep17:19
dtantsurhttps://zuul.opendev.org/t/openstack/build/1b381b57ef304017b772da1b91d7839a WUT17:22
dtantsurhttps://1183a60a708f5672e1c1-38c49964a79149719549049b602122d6.ssl.cf1.rackcdn.com/876409/1/check/openstack-tox-py310/1b381b5/job-output.txt17:23
samuelkunkel[m]Am I assuming correctly that I need a AMQP based ironic setup to use the ironic prometheus exporter? From scrolling through the docs it reads like that17:24
samuelkunkel[m]s/a/an/17:24
samuelkunkel[m](We use json_rpc currently)17:24
rpittaudtantsur: remove skisdist17:25
rpittauskipsdist17:25
dtantsursamuelkunkel[m]: I don't think so, but I'll let iurygregory answer17:25
dtantsurrpittau: thanks!!17:25
rpittausorry, put +2 and missed that17:25
TheJuliasamuelkunkel[m]: no, it loads as a notifier plugin and afaik can be used without17:25
samuelkunkel[m]That sounds good, thanks!17:26
TheJuliadtantsur: wut indeed17:26
opendevreviewDmitry Tantsur proposed openstack/ironic bugfix/21.2: Fixes for tox 4.0  https://review.opendev.org/c/openstack/ironic/+/87640917:26
opendevreviewDmitry Tantsur proposed openstack/ironic bugfix/21.2: Configure CI for bugfix/21.2  https://review.opendev.org/c/openstack/ironic/+/87641017:26
opendevreviewDmitry Tantsur proposed openstack/ironic bugfix/21.2: Do not move nodes to CLEAN FAILED with empty last_error  https://review.opendev.org/c/openstack/ironic/+/87617417:27
opendevreviewDmitry Tantsur proposed openstack/ironic bugfix/21.2: Update .gitreview for bugfix/21.2  https://review.opendev.org/c/openstack/ironic/+/86782617:27
iurygregorysamuelkunkel[m], AMQP is not required 17:29
dtantsurI'd still love if somebody could take a quick look at https://review.opendev.org/c/openstack/ironic/+/875944 and tell me in which parts I'm too crazy even for me :)17:34
* TheJulia takes a stick and pokes diskiamge-builder17:35
dtantsuris it too early in your day to suggest a flame-thrower?17:36
rpittaubye everyone, have a great weekend! o/17:37
dtantsuro/17:37
dtantsurI'm going as well, enjoy the weekend17:38
samuelkunkel[m]Thanks iurygregory . Is that also the case for the upcoming addition of ironic internal metrics?17:39
TheJuliaguestfish: cannot mix --ro and --rw options <-- i just feel like drinking17:45
TheJuliadtantsur: i dunno, it could be good idea17:45
TheJuliasamuelkunkel[m]: yes17:46
iurygregorysamuelkunkel[m], correct (but you will need to use the antelope version for ironic and for IPE)17:55
opendevreviewMerged openstack/ironic bugfix/19.0: Do not move nodes to CLEAN FAILED with empty last_error  https://review.opendev.org/c/openstack/ironic/+/87617917:56
opendevreviewMerged openstack/ironic bugfix/20.2: Do not move nodes to CLEAN FAILED with empty last_error  https://review.opendev.org/c/openstack/ironic/+/87617718:04
opendevreviewMerged openstack/ironic stable/zed: Do not move nodes to CLEAN FAILED with empty last_error  https://review.opendev.org/c/openstack/ironic/+/87617518:04
opendevreviewMerged openstack/ironic bugfix/21.3: Configure CI for bugfix/21.3  https://review.opendev.org/c/openstack/ironic/+/87626418:04
opendevreviewMerged openstack/ironic master: Add Yoga versions to release notes  https://review.opendev.org/c/openstack/ironic/+/85504218:04
TheJuliadtantsur: done18:08
JayF> Servers can only have one owner. It is not easy to trade servers between different tenants. 18:17
JayFfalse18:17
JayFlol18:17
* JayF is catching up18:17
TheJuliaJayF: I thought the same thing, and I'm fairly sure dissertations have been done on that subject18:18
JayFThis honestly reads like a ... shallow understanding of what already exists and where the pitfalls lie18:18
TheJuliaI had a similar impression, in that it was clearly written from their context, and in their view this is it18:34
JayFwe should try to reach out and talk to them18:34
JayFopen source to me, part of it is about trying to reduce duplication of effort and if we can help them, or convince them to use ironic tools as a part of their project, all the better18:35
JayFhell, maybe another user of virtualbmc/sushy-tools/virtualpdu18:35
samuelkunkel[m]iurygregory sounds good. Once Antelope is released I will give it a try. Is the versioning of the IPE aligned with the openstack versioning? Or is it more like sushy / ipa where certain versions are aligned with certain openstack release versions?18:50
JayFIPA and IPE are both 'cycle-with-intermediary' which means they get a release cut at least once when the openstack integrated release is cut18:54
JayFso there should be a version of it released and maintained directly corrolating to the OpenStack 2023.1 (aka Antelope) release.18:54
JayF(I think sushy is an independent library? but I'm not sure)18:54
TheJuliasushy I think is independent18:59
TheJuliabut we still need to cut releases ourselves 19:00
TheJuliafor ipe/ipa19:00
jlvillalDoes Ironic have a IPA kernel/ramdisk based on aarch config option? Kind of like there is a ipxe_bootfile_name_by_arch option.19:05
JayFWe talked about that, IDR if we actually did it19:06
jlvillalBut this is probably just showing my lack of knowledge on how things are supposed to be done.19:06
JayFlemme check release notes19:06
jlvillalThanks!19:07
TheJuliait is not there19:07
JayFhttps://files.openstack.org/docs/ironic/victoria/install/configure-pxe.html#pxe-multi-architecture-setup19:07
JayFoh, that's pxe bootfile, not ipa19:08
JayFdang19:08
JayFjlvillal: https://etherpad.opendev.org/p/ironic-bobcat-ptg line 3919:08
jlvillalThanks. No worries. Sounds like I should configure the json/yaml file in bifrost with ipa_kernel_url19:08
JayFjlvillal: it's on the schedule to discuss at PTG19:08
TheJuliarealistically, given nodes can vary so much, I would generally just expect they be set on the node level, the general options in ironic.conf are really only for more general user cases19:08
JayFyeah, you can absolutely do it per node, but it's not-ideal to have any "run an API call N times for N nodes" which is what that creates19:09
JayFalias-based assignment, as laid out in that ehterpad, is likely the route to go19:09
JayFprobably not that complex either? we should JFDI for bobcat19:09
jlvillalOkay. Thanks all :)  I think I know what I need to do for my use case. I'm hoping I can set it in the JSON I pass to `./bifrost-cli deploy`19:12
TheJuliayeah, I'd rather just review a patch than discuss it ;)19:12
TheJuliathere is likely a little more complexity in the option handling that might be refactoring19:12
TheJuliabut I don't know if that is really bikeshedable19:12
jlvillaleverything is bikesheddable ;)19:13
jlvillalhehe19:13
* TheJulia gets out the bikeshed paint can labeled "purple"19:13
* TheJulia suggests we debate "purple"19:13
TheJulia;)19:13
jlvillal:)19:15
JayFI don't believe in purple. Can we find some empirical evidence this 'purple' actually exists? 19:19
TheJuliait is purple, it doesn't need to define itself19:21
JayFThat's exactly the attitude I'd expect from a supposed royal color 19:22
JayFlol19:22
TheJuliaThe snails gave their lives for the purple!19:22
* TheJulia suggests next debate is "green", but not to the extent the drazi went to with green and yellow.19:26
jlvillalHmmm. So I set the values `ipa_kernel_url` and `ipa_ramdisk_url` in the JSON file that I passed to `./bifrost-cli deploy`. But it seemed to ignore those values and in the `/var/lib/ironic/httpboot/` directory it created a UUID directory and the config file is pointing at the default `ipa.kernel` file which was copied into the UUID directory. :(19:27
JayFTheJulia: wasn't it purple and red? 19:28
JayFif I've forgotten it's clearly time for a rewatch lol19:29
jlvillalMaybe this will make more sense than my comment: https://paste.opendev.org/show/b2xesiwUW7TOzDQEZvAT/19:29
JayFgreen and purple lol19:29
TheJuliaoh, it was purple!19:30
JayFjlvillal: I'm looking but bifrost is a weak spot so maybe someone else will know off the top of their head19:31
TheJuliasee! purple exists!19:31
JayFdang it, you got me19:31
JayFbut it only exists in sci-fi19:31
JayFclearly :D 19:31
JayFit's a bike shed, not a spaceship, we can't paint it a space color :P  19:31
JayFjlvillal: can you share the JSON, redacted if needed?19:32
* TheJulia urges purple, in accordance with the KSP2 agency color editor19:32
* TheJulia gets does her best corgi side-eye impression with diskimage-builder19:33
jlvillalJayF, Sure. https://paste.opendev.org/show/byi0dSAa0qJx5cR72lUi/19:33
TheJuliajlvillal: under driver_info, deploy_ramdisk and deploy_kernel keys can be set19:34
TheJuliaand those can just be URLs19:34
JayFyeah AFAICT in bifrost, ipa_kernel_url and the like can only be used to set it globally, not per node19:35
JayFso I think you need to move those two keys into driver_info and you'll be set19:35
JayFso bifrost doesn't do anything w/them except plug them into ironic19:35
jlvillalThanks. I was trying to follow this example: https://github.com/openstack/bifrost/blob/0e6be25ee17ea75d60eb4f32fea37db0f79af52d/playbooks/inventory/baremetal.json.example#L28-L2919:35
jlvillalBut I can update that to deploy_kernel/ramdisk19:36
jlvillalI will try your suggestion!19:36
TheJuliahuh...19:36
jlvillalhuh about what part?19:37
TheJuliaI just don't remember that change19:37
JayFthat example appears broken19:37
JayFor I'm bad at reading ansible (very possible)19:37
jlvillalAs a note it is also in the example YAML.  https://github.com/openstack/bifrost/blob/0e6be25ee17ea75d60eb4f32fea37db0f79af52d/playbooks/inventory/baremetal.yml.example#L22-L2319:39
TheJuliaso in theory, I guess it could be used, but in practice I don't see it offhand19:39
TheJuliayeah, looking at the original change it wouldn't have bene a thing19:40
TheJuliabeen19:40
jlvillalWoohoo! Success with `deploy_kernel` and `deploy_ramdisk` :)19:45
JayF\o/19:46
TheJuliaif your using yaml you could also template the key and just rinse/repeat on a variable, fwiw19:50
jlvillalI'm using JSON at the moment. But will keep that in mind. Thanks.19:51

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