[pve-devel] [PATCH qemu-server] api: cloud-init support for mtu and userdata
Julien Escario
julien.escario at altinea.fr
Mon Jul 13 17:06:59 CEST 2020
Hello,
First, sorry, I'm taking the thread from the archive, don't have much
history.
To the question :
"Any reason why snippets [0] are not enough for custom userdata?"
Yes, there's one : in the generated, there's a few vm-specific options,
like "fqdn:" and "hostname:" parameters. Having them auto-generated in
PVE is really nice and remove the need to have a snippet file per VM.
With snippets, one can only REPLACE generated user-data. So, the fqdn
and hostname parameters are completely gone which leads to the need of
one snippet file per VM.
Having the ability to EXTEND the generated user-data is really needed.
So we can add only vm-agnostic parameters like sshkeys, packages and so
on ...
On another approach, I wrote a (really) small patch adding the
vendor-data custom file [1] but I'm not a developer and submitting a
proper usable patch is out of my capacity.
vendor-data never supersede user-data [2] so no other change should be
required.
cloud-init support in Proxmox is almost complete, please consider
integrating one of the 2 solutions inside your code base so we could
full automate VM deployment using the API and 'plug' the VM into a
config management system like puppet, ansible, chef, whatever.
Thanks a lot !
1 :
https://forum.proxmox.com/threads/combining-custom-cloud-init-with-auto-generated.59008/page-2
2 : https://cloudinit.readthedocs.io/en/latest/topics/vendordata.html
More information about the pve-devel
mailing list