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

[Alexandre DERUMIER]

>>nd it makes me wonder even more why on ubuntu (and apparently on arch
>>too) cloud-init keeps trying to connect to the EC2 ip address rather
>>than just realizing it's already been configured the previous boot.
>>This needs to be dealt with one way or another.

dpkg-configure cloud-init , and choose configdrive as only datasource.

I think at start, cloud-init ask to his datasources if they are a new config.


>>At the same time I can't find my instance's network configuration in 
>>/var/lib/cloud/instances/<id>, while the 'user_data' part (with users 
>>and ssh keys etc.) seems to be in there. 

I think that the metadata config is not write inside /var/lib/cloud/instance


>>But if you change the uuid a new directory appears in 
>>/var/lib/cloud/instances without the old ones disappearing. New files on 
>>every applied update. 
>>
>>Maybe I'm missing something obvious...? 
I need to check that, I thinked that only the the symlink /var/lib/cloud/instance ---> /var/lib/cloud/instances/currentuuid/
was applied.

Maybe this is what about merge is doing ?
http://cloudinit.readthedocs.org/en/latest/topics/merging.html


----- 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é: Vendredi 12 Juin 2015 09:18:43
Objet: Re: [pve-devel] RFC: qemu-server : add cloudinit support

On Thu, Jun 11, 2015 at 08:15:25PM +0200, Alexandre DERUMIER wrote: 
> >>So you simply need to stop/start to apply new values? 
> >>>I need to check that, but I think yes. 
> 
> The config is reapply only if the uuid of the configdrive is changed 
> (they are a uuid symlink with old cloud-init config in /var/lib/cloud/instance) 

It indeed only seems to *apply* use it when the instance id changes, yet 
it *does* update the /var/lib/cloud/instances/<id>/ folder when the 
configuration is changed without updating the instance id. The purpose 
of this seems to elude me. 
And it makes me wonder even more why on ubuntu (and apparently on arch 
too) cloud-init keeps trying to connect to the EC2 ip address rather 
than just realizing it's already been configured the previous boot. 
This needs to be dealt with one way or another. 

At the same time I can't find my instance's network configuration in 
/var/lib/cloud/instances/<id>, while the 'user_data' part (with users 
and ssh keys etc.) seems to be in there. 

> My code is wrong, because I take the smbios1 uuid. 
> The config uuid is just a random uuid. 
> 
> I'll send new patchs tomorrow. 

But if you change the uuid a new directory appears in 
/var/lib/cloud/instances without the old ones disappearing. New files on 
every applied update. 

Maybe I'm missing something obvious...?