Bootstrap Debian images for virtualized environments
Find a file
2014-05-10 16:42:35 +02:00
bootstrapvz Merge branch 'master' into development 2014-05-08 23:00:54 +02:00
docs Move taskoverview into docs/ 2014-05-10 16:42:35 +02:00
manifests Fixes #14 and #78 2014-05-03 16:12:34 +02:00
tests/integration Fix log_call test to not give random outcomes. 2014-05-04 15:01:45 +02:00
.gitignore Added manifest checking tests. 2014-04-30 17:21:32 -05:00
.travis.yml Add Travis CI 2014-04-27 10:12:04 -03:00
bootstrap-vz Properly fix imports and make bootstrapvz work like a package 2014-04-02 21:32:10 +02:00
CHANGELOG.md Add changes by Dhananjay to changelog 2014-05-08 22:28:11 +02:00
CONTRIBUTING.md Note about changelog in contribution guidelines 2014-05-08 23:16:00 +02:00
LICENSE Add license 2014-04-02 21:26:14 +02:00
MANIFEST.in bootstrap-vz is now a proper python package 2014-04-02 23:25:50 +02:00
README.md Merge branch 'master' into development 2014-05-08 23:00:54 +02:00
setup.py Depend on boto 2014-04-08 21:58:48 +02:00
tox.ini Added manifest checking tests. 2014-04-30 17:21:32 -05:00

bootstrap-vz

bootstrap-vz is a bootstrapping framework for Debian. It is is specifically targeted at bootstrapping systems for virtualized environments. bootstrap-vz runs without any user intervention and generates ready-to-boot images for a number of virtualization platforms. Its aim is to provide a reproducable bootstrapping process using manifests as well as supporting a high degree of customizability through plugins.

bootstrap-vz was coded from scratch in python once the bash script architecture that was used in the build-debian-cloud bootstrapper reached its limits.

Documentation

The end-user documentation for bootstrap-vz is available at andsens.github.io/bootstrap-vz. There, you can discover what the dependencies for a specific cloud provider are, see a list of available plugins and learn how you create a manifest.

Developers

The API documentation can be found at bootstrap-vz.readthedocs.org.

Contributing

Contribution guidelines are described on the CONTRIBUTING file. There's also a topic on the documentation regarding the coding style.