diff options
| author | Mark Goddard <mark@stackhpc.com> | 2022-01-19 13:21:17 +0000 |
|---|---|---|
| committer | Mark Goddard <mark@stackhpc.com> | 2022-03-21 11:54:31 +0000 |
| commit | 4e41acd8f0ccc8dee432f72cfafcca16d01a11b7 (patch) | |
| tree | 5d23b7dbc67220a064770614903cc01499d9c29b /doc | |
| parent | ed148cd8dd9345c8a0fe0e2c56bc743269c29de4 (diff) | |
| download | kolla-ansible-4e41acd8f0ccc8dee432f72cfafcca16d01a11b7.tar.gz kolla-ansible-4e41acd8f0ccc8dee432f72cfafcca16d01a11b7.zip | |
libvirt: make it possible to run libvirt on the host
In some cases it may be desirable to run the libvirt daemon on the host.
For example, when mixing host and container OS distributions or
versions.
This change makes it possible to disable the nova_libvirt container, by
setting enable_nova_libvirt_container to false. The default values of
some Docker mounts and other paths have been updated to point to default
host directories rather than Docker volumes when using a host libvirt
daemon.
This change does not handle migration of existing systems from using
a nova_libvirt container to libvirt on the host.
Depends-On: https://review.opendev.org/c/openstack/ansible-collection-kolla/+/830504
Change-Id: Ia1239069ccee39416b20959cbabad962c56693cf
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/source/reference/compute/libvirt-guide.rst | 21 |
1 files changed, 18 insertions, 3 deletions
diff --git a/doc/source/reference/compute/libvirt-guide.rst b/doc/source/reference/compute/libvirt-guide.rst index 6776c1f98..6a33a0177 100644 --- a/doc/source/reference/compute/libvirt-guide.rst +++ b/doc/source/reference/compute/libvirt-guide.rst @@ -7,7 +7,7 @@ Overview Libvirt is the most commonly used virtualisation driver in OpenStack. It uses libvirt, backed by QEMU and when available, KVM. Libvirt is executed in the -``nova_libvirt`` container. +``nova_libvirt`` container, or as a daemon running on the host. Hardware Virtualisation ======================= @@ -42,6 +42,21 @@ The list of enabled authentication mechanisms is configured via ``libvirt_sasl_mech_list``, and defaults to ``["SCRAM-SHA-256"]`` if libvirt TLS is enabled, or ``["DIGEST-MD5"]`` otherwise. +Host vs containerised libvirt +============================= + +By default, Kolla Ansible deploys libvirt in a ``nova_libvirt`` container. In +some cases it may be preferable to run libvirt as a daemon on the compute hosts +instead. + +Kolla Ansible does not currently support deploying and configuring +libvirt as a host daemon. However, since the Yoga release, if a libvirt daemon +has already been set up, then Kolla Ansible may be configured to use it. This +may be achieved by setting ``enable_nova_libvirt_container`` to ``false``. + +Migration of hosts from a containerised libvirt to host libvirt is currently +not supported. + .. libvirt-tls: Libvirt TLS @@ -77,13 +92,13 @@ will have to supply Kolla Ansible the following pieces of information: they can verify that all the certificates being used were signed by the CA and should be trusted. -* serverkey.pem +* serverkey.pem (not used when using a host libvirt daemon) - This is the private key for the server, and is no different than the private key of a TLS certificate. It should be carefully protected, just like the private key of a TLS certificate. -* servercert.pem +* servercert.pem (not used when using a host libvirt daemon) - This is the public certificate for the server. Libvirt will present this certificate to any connection made to the TLS port. This is no different |