Hi. Vincent Bernat <[email protected]> writes:
> ❦ 1 février 2017 19:05 +0100, Olivier Berger > <[email protected]> : > >> I have already some basic knowledge of bootstrap-vz, which I've used >> with VirtualBox and Vagrant providers, thanks. But I'm wondering whether >> anyone documented the specifics of OpenStack. >> >> Maybe you're missing some specifics of deploying the VM on the OpenStack >> IaaS, which requires some provisioning at first boot (like setting some >> specific way to connect to that specific VM instance: IP address and >> user password for instance... well I'm guessing here, actually, as I >> haven't checked how OpenStack does that). >> >> AFAIU, that's the job that cloud-init does. And as there may be other >> nifties involved, that's why I asked. > > cloud-init just has to be installed. There is nothing else special to > do. The OpenStack provider is enabled by default. You can however > restrict the list to "ConfigDrive, OpenStack" for a faster boot (either > with debconf, cloud-init/datasources or by overwriting > /etc/cloud/cloud.cfg.d/90_dpkg.cfg). > This may be true post jessie, but AFAIU, the 'OpenStack' data source isn't supported out of the box in Jessie's version of cloud-init (see #841315), and one may have to explicitely customize with a change of the config file for it to be fully recognized. Still, ConfigDrive or the Ec2 may be enough, depending on the target cloud. Hth, Best regards, -- Olivier BERGER http://www-public.telecom-sudparis.eu/~berger_o/ - OpenPGP-Id: 2048R/5819D7E8 Ingenieur Recherche - Dept INF Institut Mines-Telecom, Telecom SudParis, Evry (France)
