[GH-ISSUE #3] [test] Cloud-Init Support #3

New issue

Closed

opened 2026-03-03 14:44:34 +03:00 by kerem · 0 comments

kerem commented

2026-03-03 14:44:34 +03:00

Owner

Originally created by @luthermonson on GitHub (Aug 3, 2021).
Original GitHub issue: https://github.com/luthermonson/go-proxmox/issues/3

Would like to try and offer support for taking a cloud-config and metadata file as string and then auto-generate an iso, upload it and then mount it before booting to get caught in the no-cloud boot options for cloud-init. See code I wrote for the (vsphere machine driver)[https://github.com/rancher/machine/blob/master/drivers/vmwarevsphere/cloudinit.go#L128-L202] and see if we can get full support for cloud-init using this as it would greatly improve the machine driver as well as a terraform module if we decide.

Just note... as per some things we came across with while doing the vsphere driver...

cleanup is important, leaving a bunch of isos lying around on the disk is annoying
perhaps keeping track on the qemu vm with a note about the cloud-init.iso name and we delete the associated iso when the vm is deleted
After boot give you should be able to safely unmount and remove the iso from the proxmox, on boot cloud-init copies everything and stores a local cache on disk so the iso should be able to be safely removed fairly quickly and deleted

Originally created by @luthermonson on GitHub (Aug 3, 2021). Original GitHub issue: https://github.com/luthermonson/go-proxmox/issues/3 Would like to try and offer support for taking a cloud-config and metadata file as string and then auto-generate an iso, upload it and then mount it before booting to get caught in the no-cloud boot options for cloud-init. See code I wrote for the (vsphere machine driver)[https://github.com/rancher/machine/blob/master/drivers/vmwarevsphere/cloudinit.go#L128-L202] and see if we can get full support for cloud-init using this as it would greatly improve the machine driver as well as a terraform module if we decide. Just note... as per some things we came across with while doing the vsphere driver... * cleanup is important, leaving a bunch of isos lying around on the disk is annoying * perhaps keeping track on the qemu vm with a note about the cloud-init.iso name and we delete the associated iso when the vm is deleted * After boot give you should be able to safely unmount and remove the iso from the proxmox, on boot cloud-init copies everything and stores a local cache on disk so the iso should be able to be safely removed fairly quickly and deleted