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

[Alexandre DERUMIER]

>>It is a perfect fit, because we have that 'pending' API now ;-)
Oh, I forgot about this.. ;)

>>So you simply need to stop/start to apply new values?
I need to check that, but I think yes.


----- 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é: Jeudi 11 Juin 2015 18:00:49
Objet: Re: [pve-devel] RFC: qemu-server : add cloudinit support

> >>OTOH it may be desirable to keep the config datasource attached. That 
> >>way the WEB UI's configuration is the "permanent" one, and changes made 
> >>in the running VM to /etc/ (eg. /etc/network/interfaces) are only 
> >>temporary. 
> >> 
> >>Otherwise the options in the UI would have to be deleted/greyed out with 
> >>it to reflect the new situation, while if the config is kept around 
> >>there'd be some permanently-available settings in the UI. 
> 
> I think that Cloud-init should be only use to setup the vm create|provisioning 
> as I said in a previous mail, I think we should simply pass parameters 
> to qm clone .... -ipddress -gateway -nameserver ... 
> This is what ovirt|rhev are doing currently. 
> http://www.ovirt.org/Features/Cloud-Init_Integration 

I am not sure why you want to add such restriction? IMHO, this would make 
the whole think quite useless. For example, if we have IPs on host side, we can 
also 
have better firewall rules by default... 

> If we would like to manage ips in gui, we could generate a new configdrive, 
> but we can't tell to guest to reforce relaunch of cloud-init. 
> (or maybe with a udev rules trick ?) 

This configuration is simple cold-plug. It is a perfect fit, because we 
have that 'pending' API now ;-) So you simply need to stop/start to apply 
new values?