bootstrap-vz/bootstrapvz/providers/kvm
Brendan Harley 511a44f72e 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-06-08 17:05:48 +02:00
..
tasks Systematically use rel_path for relative paths 2016-09-12 19:11:20 +02:00
__init__.py Add LVM as a disk backend 2017-06-08 17:05:48 +02:00
manifest-schema.yml Add LVM as a disk backend 2017-06-08 17:05:48 +02:00
README.rst Add LVM as a disk backend 2017-06-08 17:05:48 +02:00

KVM
===

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).
It also supports creating an image with LVM as a disk backend.

Manifest settings
-----------------

Provider
~~~~~~~~

-  ``virtio``: Specifies which virtio kernel modules to install.
   ``optional``
-  ``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.

Example:

.. code-block:: yaml

    ---
    provider:
      name: kvm
      virtio:
        - virtio_blk
        - virtio_net
    volume:
      backing: lvm
      logicalvolume: lvtest
      volumegroup: vgtest