| minimal | Related to Issue #4603, I'm wondering why cloud.cfg.tmpl defines all those various groups for distros - if the distro needs them then I'd assume it should already create them. | 14:25 |
|---|---|---|
| falcojr | off the top of my head, I'm not sure. I need to do some digging | 14:44 |
| === smoser1 is now known as smoser | ||
| holmanb | minimal: https://blog.wikichoon.com/2020/09/virt-install-cloud-init.html | 23:21 |
| holmanb | minimal: I suppose it is probably worth documenting, that virt-installer uses nocloud by default, though I'm not certain where/how would be best | 23:22 |
| holmanb | note to self: #4608 | 23:24 |
| holmanb | ubottu must be out on vacation | 23:25 |
| minimal | holmanb: don't forget that virt-manager is an optional frontend to libvirt (where virt-install comes from). I believe I saw someone had come up with a cloud-init mechanism for libvirt (not upstreamed though) | 23:35 |
| minimal | holmanb: here's a guide using virsh (part of libvirtd, not virt-manager) with NoCloud: https://earlruby.org/2023/02/quickly-create-guest-vms-using-virsh-cloud-image-files-and-cloud-init/ | 23:44 |
| minimal | BTW I only recently realised that dhcpcd support was never actually integrated in cloud-init, just a "stub". I'd thought full support had gone in around the same time as udhcpcd | 23:45 |
| minimal | A lot of these 3rd party guides only mention meta-data and user-data files regarding NoCloud, with no mention of network-config whatsoever | 23:47 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!