Bootstrap Debian images for virtualized environments
Find a file
Tiago Ilieve 17b0e6e57a Add information about coding style checking
Added a note about this to the CONTRIBUTING.md file. [skip ci]
2014-04-27 10:50:07 -03:00
bootstrapvz PEP8 fixes 2014-04-27 10:14:02 -03:00
docs Add support for adding APT preferences 2014-04-04 12:22:46 +02:00
manifests ASwitch manifests ot explicitly use Ec2 for metadata. Swap S3 to use a 4GB root FS. 2014-04-08 12:34:25 +00:00
.gitignore Add Travis CI 2014-04-27 10:07:53 -03:00
.travis.yml Add Travis CI 2014-04-27 10:07:53 -03:00
bootstrap-vz Properly fix imports and make bootstrapvz work like a package 2014-04-02 21:32:10 +02:00
CONTRIBUTING.md Add information about coding style checking 2014-04-27 10:50:07 -03: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 Add contribution guidelines 2014-04-08 08:30:43 -03:00
setup.py bootstrap-vz is now a proper python package 2014-04-02 23:25:50 +02:00
tox.ini Add Travis CI 2014-04-27 10:07:53 -03: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.