External/libvirt
1
0
Fork 0
mirror of https://gitlab.com/libvirt/libvirt.git synced 2024-12-22 13:45:38 +00:00
Code Issues Packages Projects Releases Wiki Activity

kbase: Reorder deployments

Browse Source 
List the various options so that the most likely ones come
first.

Signed-off-by: Andrea Bolognani <abologna@redhat.com>
Reviewed-by: Jim Fehlig <jfehlig@suse.com>
This commit is contained in:
Andrea Bolognani 2022-12-14 19:31:47 +01:00
parent db7fdf6de8
commit b271d6f3b0
1 changed files with 26 additions and 26 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

52
docs/kbase/rpm-deployment.rst
View File

@ -23,32 +23,6 @@ listed on this page will exist.
Deployment choices
==================
Client only install
-------------------
If an application is capable of using multiple different virtualization drivers
it is undesirable to force the installation of a specific set of drivers. In
this case the application will merely wish to request a client only install
Alternatively if an application is intended to communicate with a hypervisor on
a remote host there is no need to install drivers locally, only a client is
needed
The only required package is the `libvirt-libs`, however, it is useful to
also install `libvirt-client`.
Every possible virt driver
--------------------------
There is rarely a need to install every virt driver at once on a given host.
In the unlikely event that this is needed, however, the `libvirt` package
should be installed.
Note that this doesn't actually pull in the hypervisors, only the libvirt
code to talk to the hypervisors.
Full features for one virt driver
---------------------------------
@ -65,6 +39,21 @@ footprint of the daemons is also relatively large since a lot of code is
loaded.
Client only install
-------------------
If an application is capable of using multiple different virtualization drivers
it is undesirable to force the installation of a specific set of drivers. In
this case the application will merely wish to request a client only install
Alternatively if an application is intended to communicate with a hypervisor on
a remote host there is no need to install drivers locally, only a client is
needed
The only required package is the `libvirt-libs`, however, it is useful to
also install `libvirt-client`.
Minimal features for one virt driver
------------------------------------
@ -87,6 +76,17 @@ and host devices, leaving only the bare minimum functionality for managing
KVM guests.
Every possible virt driver
--------------------------
There is rarely a need to install every virt driver at once on a given host.
In the unlikely event that this is needed, however, the `libvirt` package
should be installed.
Note that this doesn't actually pull in the hypervisors, only the libvirt
code to talk to the hypervisors.
RPM packages
============