meena | cjp256: any chance i could get access to one of these for my project: https://learn.microsoft.com/en-us/azure/virtual-machines/workloads/hpc/enable-infiniband ? | 00:31 |
---|---|---|
zaphod_b | hiya lads; I am trying to use cloud-init on a bare-metal Dell server using the ubuntu cloud image and Dell's Redfish API to expose a nocloud config | 08:12 |
zaphod_b | My first attempts are a little disconcerting; I am new to cloud-init I should add | 08:13 |
zaphod_b | I was kind of assuming that mounting a 'cidata' ISO image in the drac environment would suffice for cloud-init to find my config, but it does not seem to | 08:14 |
zaphod_b | so I guess my first question is, is this scheme supposed to work at all ? | 08:14 |
aciba | Hello zaphod_b: that should work, assuming Nocloud is detected as datasource. One can see that in the file: /run/cloud-init/result.json | 08:29 |
aciba | documentation about Nocloud: https://cloudinit.readthedocs.io/en/latest/reference/datasources/nocloud.html | 08:30 |
aciba | a good source of information is: /var/log/cloud-init.log | 08:31 |
zaphod_b | aciba: thank you; it's already a great help to know that it's feasible ! | 08:35 |
zaphod_b | My next issue then would be to gain access to the OS so that I can inspect these locations; since my config is not found I don't know how to enter the OS at all | 08:35 |
zaphod_b | ok sorry, I found my way through an alternate console... thanks ! | 08:38 |
waldi | and was what the cause? | 08:40 |
aciba | zaphod_d: a useful command to collect debugging informat: https://cloudinit.readthedocs.io/en/latest/howto/bugs.html#collect-logs | 08:45 |
aciba | if you could minimally share the log (redacting any sensible information) we could try to see what's going on | 08:46 |
zaphod_b | aciba: so actually a lot more than I thought was working ! cloud-init did find my input ! | 08:49 |
zaphod_b | I guess I've been confused because (*) I could see for a long time a message at boot-time saying "connecting.... waiting for cloud-init..." | 08:50 |
zaphod_b | and also because the ubuntu boot went on and asked for a language; but I guess this is something that I can now configure | 08:51 |
zaphod_b | so I guess I'll just do my homework and come back here if anything goes south | 08:52 |
aciba | that sounds great! maybe the locale module can help there: https://cloudinit.readthedocs.io/en/latest/reference/modules.html#locale | 08:53 |
aciba | please tell us if you find any problem/difficulty | 08:53 |
zaphod_b | just one last question maybe: I was interested in provisioning fedora also with a similar approach; is there any publicly available fedora image that comes with cloud-init ? | 08:55 |
zaphod_b | it looks like fedora has their own ignition thing... | 08:55 |
zaphod_b | in any case aciba: thanks for your help ! | 09:01 |
=== caribou_ is now known as caribou | ||
=== esv_ is now known as esv | ||
holmanb | zaphod_b: nice nick :) | 14:32 |
holmanb | zaphod_b: fedora has cloud images with cloud-init, but not autoinstall support | 14:35 |
cjp256 | meena: will see what i can do, anything in particular that you need to see? | 15:24 |
meena | cjp256: I need a few hours with freebsd on a machine with infiniband, because programming from hearsay isn't working out so great | 15:38 |
blackboxsw | community notice: upstream release 23.1 published https://github.com/canonical/cloud-init/releases/tag/23.1. Thanks aciba for driving the release this round | 19:54 |
blackboxsw | upload of 23.1 accepted and published to Ubuntu 23.04: cloud-init 23.1-0ubuntu1 (Accepted) expect it available in tomorrow's cloud-images. | 19:56 |
blackboxsw | Our plan is start StableReleaseUpdate of 23.1 to Ubuntu Bionic. Focal, Jammy and Kinetic over the next week. | 19:56 |
blackboxsw | thank you all for the contributions to various clouds and improved distribution support this release! | 19:58 |
=== blackboxsw changed the topic of #cloud-init to: 23.1 Released 02/22 | Bugs: https://bugs.launchpad.net/cloud-init/+filebug | PRs: https://git.io/JeVed | release schedule: https://discourse.ubuntu.com/t/cloud-init-2022-release-schedule/25413 | ||
=== rharper_ is now known as rharper | ||
meena | anyone know if lxd --vm will run a current (or soon to be released) FreeBSD? | 20:33 |
meena | (CURRENT is the development branch… it's a bit confusing) | 20:33 |
falcojr | meena: if there are no published images for it, there are ways of importing your own images. IIRC, people can gotten windows running through LXD | 20:35 |
* meena snap installs lxd | 20:35 | |
meena | This laptop has 64 GiB of RAM, so I better make good use of that | 20:35 |
meena | i don't see any published ones: https://us.lxd.images.canonical.com/ so I'll just grab a current image and resize it and use that | 20:39 |
meena | falcojr: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=269767 | 21:30 |
-ubottu:#cloud-init- bugs.freebsd.org bug 269767 in Base System "13.1-RELEASE VM IMAGE panics on boot under LXC / LXD" [Affects Only Me, New] | 21:30 | |
falcojr | interesting | 21:31 |
meena | i'm hoping to test 14.0-CURRENT or STABLE… | 21:37 |
meena | But, alas, someone broke the release / mirror: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=269764 | 21:38 |
-ubottu:#cloud-init- bugs.freebsd.org bug 269764 in Services "14.0-CURRENT CI-IMAGES yield 404" [Affects Only Me, New] | 21:38 | |
meena | (and, while I could use the not-CI-IMAGES images, they are awful) | 21:39 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!