[pve-devel] RFC: qemu-server : add cloudinit support

[Alexandre DERUMIER]

Hi Wolfgang,

I didn't have time to work on it yestarday (too busy at work),

Seem great, but I don't known if it's working with windows cloud-init ?
https://github.com/cloudbase/cloudbase-init

?


Another way is to use virtio-9p-pci device (but I don't known if it's working with all guest os)

https://coreos.com/docs/cluster-management/setup/cloudinit-config-drive/

qemu-system-x86_64 \
    -fsdev local,id=conf,security_model=none,readonly,path=/tmp/new-drive \
    -device virtio-9p-pci,fsdev=conf,mount_tag=config-2 \


----- Mail original -----
De: "Wolfgang Bumiller" <w.bumiller at proxmox.com>
À: "aderumier" <aderumier at odiso.com>
Cc: "dietmar" <dietmar at proxmox.com>, "pve-devel" <pve-devel at pve.proxmox.com>
Envoyé: Jeudi 18 Juin 2015 15:16:34
Objet: Re: [pve-devel] RFC: qemu-server : add cloudinit support

Hey Alexandre, 
I don't know if you're already tinkering with rsyncing the iso images, 
and wanted to let you know that I'm currently experimenting with qemu's 
vvfat drive option. According to the source it should work across 
migrations as long as it's used read-only. I tested migrating in a 
virtual testcluster and it seemed to work. 
It basically takes a directory, loads the list of contained files and 
presents the guest OS with a fat16 formatted partition on a block device. 
The downside of it is that we need the qemu patch I posted earlier to 
label the partition, as cloud-init needs it to be labeled "config-2", 
but qemu's vvfat default is hardcoded to "QEMU VVFAT". 
The change is small enough though, so maybe they even accept it 
upstream... 

On Wed, Jun 17, 2015 at 12:58:53PM +0200, Alexandre DERUMIER wrote: 
> >>I would generate a Digest using all cloud-init related values, and re-gererate 
> >>the iso at VM start 
> >>if the digest has changed. 
> 
> Ok. Maybe can be generate the cloudinit iso file with vmid-digest.iso ? 
> Like this no need to store the dgest in vmid.conf ? 
> 
> Also, Do we need to set theses changed values in pending or not ? 
> 
> 
> ----- Mail original ----- 
> De: "dietmar" <dietmar at proxmox.com> 
> À: "Wolfgang Bumiller" <w.bumiller at proxmox.com>, "aderumier" <aderumier at odiso.com> 
> Cc: "pve-devel" <pve-devel at pve.proxmox.com> 
> Envoyé: Mercredi 17 Juin 2015 11:40:24 
> Objet: Re: [pve-devel] RFC: qemu-server : add cloudinit support 
> 
> > I would like to known when do you want to generate the cloudinit iso. 
> > 
> > If user change settings (ips,hostname,...), do we want to apply them directly 
> > to configuration ? 
> > or do we want to put them as pending ? (for ip can be ok, for hostname that 
> > seem strange if user want to rename his vm). 
> > 
> > Advantage to pending, is that we can simply regenerate the iso at vmstart if 
> > pending changes exist. 
> > and user can also revert with if wrong settings. 
> 
> I would generate a Digest using all cloud-init related values, and re-gererate 
> the iso at VM start 
> if the digest has changed. 
> 
>