I sort of want to convert my DIY lab VM setup shell script to cloud-init, but it doesn't seem to have any support for populating /etc/crypttab and the fact that you have to embed files into YAML as base64 is beyond gross; YAML has a | operator for indented text blocks, but keeping files separate means that editing and syntax highlighting work normally.

This week I have experimented a bit with #debian cloud images.
The goal was to automate the provisioning of a small Debian VM.
I've tested various methods :
- debian preseed
- debian generic cloud image with virt-customize
- debian with #cloudinit
Here is the repository with working examples:
https://forge.lefuturiste.fr/mbess/debian-vm-auto-setup

So I upgraded most of my #homelab, migrated to #incus, cleaned up, documented a few things I only had only kept as #cloudinit files etc. and finally got around to putting an #nginx proxy for client side certificate auth in front of a #nextcloud instance, then spent way too much time to get an iOS device to connect - just to find out that #nextcloud mobile app does not support client side cert auth (yet! scheduled to arrive 24th Apr. for Android)

I first thought #cloudinit is wonderful. But… https://gist.github.com/Informatic/0b6b24374b54d09c77b9d25595cdbd47 Yes the documentation is cancer. #cloud #linux

User-data seems to be limited to 16KB, and cloud-init does not seem to have the equivalent of the nice "ignition.config.merge" feature.
Soooo, if you need to deploy a large configuration, do I need to use the ansible config option? (https://cloudinit.readthedocs.io/en/latest/reference/modules.html#ansible)

Am I missing something? Is there a better solution (except the obvious one that is to drop that shit and use #FCOS instead)?

Gzip is already used. What do you do if this is not enough?

72 commits, and +539 −26 changes later, all my tests pass, and a real-life test reveals only one weird failure in my code that makes no sense:

https://github.com/canonical/cloud-init/pull/1779#pullrequestreview-1160802843

If you're running #FreeBSD, #NetBSD, #OpenBSD or any other #BSD in a #cloud environment (VM or hardware), I'd love to see pastes from your ifconfig -a and netstat -r (with --libxo=json on FreeBSD) — especially if they're unusual, or "messy"

I'm trying to write a definite ifconfig parser for #CloudInit

Need #help. Is there anyone who has installed a fedora 30 with #cloudinit and static ip address configuration lately? We have the problem, that the configuration isn't applied with an error mentioning a missing renderer for that config, but this seems wrong. So it would even help to prove a point if you have installed it that way. Thanks

Got the following error on multipass (beta channel) version 0.5:

cannot connect to the multipass socket

If you encounter the same thing, refreshing the snap to version 0.5-27-g49baef0 fixed it for me:

sudo snap refresh multipass --edge --classic

Likely related to this issue: https://github.com/CanonicalLtd/multipass/issues/555

If you want to know what multipass is or how it will be used in #hypha, see https://ar.al/2019/01/05/hypha-spike-deployment-1/