[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Building OpenStack images with bootstrap-vz and cloud-init ?



On Wed, Feb 1, 2017 at 6:30 PM Olivier Berger <olivier.berger@telecom-sudparis.eu> wrote:
Hi.

I haven't found yet any clear example of using bootstrap-vz to build
Debian images for OpenStack.

I'd like to be able to do so, and I think cloud-init could help here,
with the cloud-init plugin in bootstrap-vz.

My target would be the OVH public cloud, FWIW.

Any one could provide an example (documented ?) manifest or other
reference, which would save me reimplementing the wheel, and could be
added, at least to https://github.com/andsens/bootstrap-vz/issues/185
maybe ?

Thanks in advance.

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)


Hi Olivier

Checkout out the virtualbox provider (1) and its examples (2).
It's as barebones and simple as it gets. Most of the custom tasks in that provider are just niceties, such as virtualbox guest additions.
The rest is mostly pulled from the common taskset, where the task groups module (3) can assemble the appropriate tasks for you given a manifest, that part is completely provider agnostic.
So in essence, copy & paste the vbox provider, removing the virtualbox specifics and then add some openstack niceties (like registering the image or similar things).
If you don't want to go through the hassle of creating a new provider, you could probably just use virtualbox images without the guest additions.

1: https://github.com/andsens/bootstrap-vz/blob/7de914728e2dc25408399d52d0ecff55b663f72f/bootstrapvz/providers/virtualbox/__init__.py
2: https://github.com/andsens/bootstrap-vz/blob/7de914728e2dc25408399d52d0ecff55b663f72f/manifests/examples/virtualbox/jessie-vagrant.yml
3: https://github.com/andsens/bootstrap-vz/blob/7de914728e2dc25408399d52d0ecff55b663f72f/bootstrapvz/common/task_groups.py 
--
Anders Ingemann

Reply to: