Hi
We have been doing some lab testing on creating a prebuilt image of Ubuntu for various application types where things like the qemu-guest-agent is preinstalled etc.
These images are based off the official ubuntu cloud-images and we therefore use cloud-init inside Proxmox to do the configuration of network and initial administrative user with SSH-keys.
We have however noticed one issue, which is that when we add the cloud-init drive, it is married to the chosen storage.
So if I have a mix of local storage in LVM/ZFS and a Ceph storage pool and by accident set the VM to have the cloud-init drive stored on local-lvm, then I cannot move it without deleting it and adding it again.
In the above case, if we find out to have been using the incorrect storage just after VM creation or clone from template, we can always document any configurations done in cloud-init and then recreate the VM.
But if this ís discovered after production deployment it will be a bit harder. Similarly if we deploy everything on Ceph and then later find out with 200 VMs running this way, that there is a new and better distributed storage solution, then we cannot switch since we cannot move the cloud-init drive.
Are there any options as of now to move the cloud-init drive, as there seems no option to move the disk inside the GUI or at least edit the location of it?
We have been doing some lab testing on creating a prebuilt image of Ubuntu for various application types where things like the qemu-guest-agent is preinstalled etc.
These images are based off the official ubuntu cloud-images and we therefore use cloud-init inside Proxmox to do the configuration of network and initial administrative user with SSH-keys.
We have however noticed one issue, which is that when we add the cloud-init drive, it is married to the chosen storage.
So if I have a mix of local storage in LVM/ZFS and a Ceph storage pool and by accident set the VM to have the cloud-init drive stored on local-lvm, then I cannot move it without deleting it and adding it again.
In the above case, if we find out to have been using the incorrect storage just after VM creation or clone from template, we can always document any configurations done in cloud-init and then recreate the VM.
But if this ís discovered after production deployment it will be a bit harder. Similarly if we deploy everything on Ceph and then later find out with 200 VMs running this way, that there is a new and better distributed storage solution, then we cannot switch since we cannot move the cloud-init drive.
Are there any options as of now to move the cloud-init drive, as there seems no option to move the disk inside the GUI or at least edit the location of it?
