[pve-devel] RFC : cloudinit : PATCH V8

[Wolfgang Bumiller]

I'd like to pick this up again. Have you made any more changes?
Currently generating the cloudinit image is a one-shot mechanism (and
also currently fails if the image already exists.), it ends up as a
"normal" (persistent) image in a cd drive.
I'm wondering if this is ideal, and how this would be represented in the
UI. (Probably a simple «generate cloudinit» button?)
Do we still like to have a way to auto-regenerate it when changing
network configuration? Because for this the current situation is
somewhat inconvenient as we'd have to match the existing drives for a
disk named vm-${vmid}-cloudinit.

On Tue, Jul 07, 2015 at 09:14:32AM +0200, Alexandre Derumier wrote:
> - changelog (patch 5/5):
> 
>   - support any storage and not only qcow2
> 
>   - cloudinit drive volume no more generated at start.
> 
>     we can now enable|disable cloudinit with
> 
>     qm set vmid -(ide|sata)x  storeid:cloudinit
>     qm set vmid -delete (ide|sata)x
> 
>     
>  improve me : add digest as drive property, to avoid commit_cloudinit_disk
>              at each start
> 
> 
> _______________________________________________
> pve-devel mailing list
> pve-devel at pve.proxmox.com
> http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
>