kevinheyer/bootstrap-vz
1
0
Fork 0
mirror of https://github.com/kevingruesser/bootstrap-vz.git synced 2025-08-24 15:36:27 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions
bootstrap-vz/bootstrapvz/providers/kvm/README.rst

37 lines
953 B
ReStructuredText
Raw Normal View History

Combine documentation from github wiki with sphinx This is the first step in the effort of combining all documentation about bootstrap-vz into sphinx while still being able to access it from github (github can parse rst as well)
2015-04-11 16:15:49 +02:00
KVM
fix document toctree
2016-03-15 11:13:05 +09:00
===
Combine documentation from github wiki with sphinx This is the first step in the effort of combining all documentation about bootstrap-vz into sphinx while still being able to access it from github (github can parse rst as well)
2015-04-11 16:15:49 +02:00
The `KVM <http://www.linux-kvm.org/page/Main_Page>`__ provider creates
virtual images for Linux Kernel-based Virtual Machines. It supports the
installation of `virtio kernel
modules <http://www.linux-kvm.org/page/Virtio>`__ (paravirtualized
drivers for IO operations).
Add qcow2 as a disk backend for KVM This allows to build an image with qcow2 as a disk backend. The update implements a new class that inherits from QEMUVolume and just needs the extention and file format.
2017-06-14 18:09:27 +02:00
It also supports creating an image with LVM and qcow2 as a disk backend.
Improve providers docs and add loads of manifest examples
2015-12-13 15:24:27 +01:00
Manifest settings
-----------------
Provider
~~~~~~~~
- ``virtio``: Specifies which virtio kernel modules to install.
``optional``
Add LVM as a disk backend Enables the use of Logical Volumes as disk backends. It uses an existing volume group and has no support for creating a new one. It will not override an existing logical volume and fail gracefully. The lv is created, activated and then mounted as a loop device. The boostraping process is then launched on the loop device. Once the process is completed, the lv is unmounted and desactivated. The created lv will be deleted should the boostraping process fail. The lv must be activated before use. A manifest has been included for testing purposes.
2017-05-14 21:09:19 +02:00
- ``logicalvolume``: Specifies the logical volume where the disk image will be built.
``volumegroup``: Specifies the volume group where the logical volume will be stored.
These options should only be used if ``lvm`` was given as a disk backend.
Improve providers docs and add loads of manifest examples
2015-12-13 15:24:27 +01:00
Example:
Compat with new sphinx Changed a lot of code:: to code-block:: Also added sphinx_rtd_theme to deps in tox
2016-03-04 01:19:29 +01:00
.. code-block:: yaml
Improve providers docs and add loads of manifest examples
2015-12-13 15:24:27 +01:00
---
provider:
name: kvm
virtio:
- virtio_blk
- virtio_net
Add LVM as a disk backend Enables the use of Logical Volumes as disk backends. It uses an existing volume group and has no support for creating a new one. It will not override an existing logical volume and fail gracefully. The lv is created, activated and then mounted as a loop device. The boostraping process is then launched on the loop device. Once the process is completed, the lv is unmounted and desactivated. The created lv will be deleted should the boostraping process fail. The lv must be activated before use. A manifest has been included for testing purposes.
2017-05-14 21:09:19 +02:00
volume:
backing: lvm
logicalvolume: lvtest
volumegroup: vgtest
Reference in a new issue Copy permalink