Re: Should cloud-init be used only for initial setup of the VM, or left active during the VM lifetime ?
On Thu, Jun 11, 2015 at 2:58 PM, Emmanuel Kasper <firstname.lastname@example.org> wrote:
> Hi List
> I am building with the nice folks at Proxmox a virtualization
> platform, based on Debian, KVM and LXC, with a rest api and a web front end.
> We are considering adding cloud-init support in our API to add an
> out-of-VM way of doing the system.
> As I don't have preliminary experience with cloud-init, I am not sure
> what is the best way to use cloud-init. Is it meant to be always run on
> start, overwriting local settings in /etc/network/interface, or only
> once during the provisioning the machine ?
It depends. cloud-init runs a whole bunch of services (configured in
/etc/cloud/cloud.cfg), some of them run at every boot, some of them
run only once at first boot. But cloud-init will run at every boot and
will try to contact a metadata service.
> It seems if I remove the config drive, the startup process hangs
> waiting, so it seems to me cloud-init is meant to be run at each boot,
> or am I missing something ?
It's trying to find a metadata service. It should time out after 2
mins and boot should resume. cloud-init supports a variety of metadata
services but requires to find one to function properly. Well, more
precisely, you can configure it for local (no metadata service) use as
well but then it's not that useful IMHO.
>  https://pve.proxmox.com/wiki/Main_Page