mirror of
https://gitlab.com/libvirt/libvirt.git
synced 2024-11-02 19:31:18 +00:00
4591df766d
The Open Nebula driver has been unmaintained since it was first introduced. The only commits have been for tree-wide cleanups. It also has a major design flaw, in that it only knows about guests that it has created itself, which makes it of very limited use. Discussions wrt evolution of the VMWare ESX driver, concluded that it should limit itself to single-node ESX operation and not try to manage the multi-node architecture of VirtualCenter. Open Nebula is a cluster like Virtual Center, not a single node system, so the same reasoning applies. The DeltaCloud project includes an Open Nebula driver and is a much better fit architecturally, since it is explicitly targetting the distributed multihost cluster scenario. Thus this patch deletes the libvirt Open Nebula driver with the recommendation that people use DeltaCloud for managing it instead. * configure.ac: Remove probe for xmlrpc & --with-one arg * daemon/Makefile.am, daemon/libvirtd.c, src/Makefile.am: Remove ONE driver build * src/opennebula/one_client.c, src/opennebula/one_client.h, src/opennebula/one_conf.c, src/opennebula/one_conf.h, src/opennebula/one_driver.c, src/opennebula/one_driver.c: Delete files * autobuild.sh, libvirt.spec.in, mingw32-libvirt.spec.in: Remove build rules for Open Nebula * docs/drivers.html.in, docs/sitemap.html.in: Remove reference to OpenNebula * docs/drvone.html.in: Delete file
62 lines
2.5 KiB
Plaintext
62 lines
2.5 KiB
Plaintext
libvirt library code README
|
|
===========================
|
|
|
|
The directory provides the bulk of the libvirt codebase. Everything
|
|
except for the libvirtd daemon and client tools. The build uses a
|
|
large number of libtool convenience libraries - one for each child
|
|
directory, and then links them together for the final libvirt.so,
|
|
although some bits get linked directly to libvirtd daemon instead.
|
|
|
|
The files directly in this directory are supporting the public API
|
|
entry points & data structures.
|
|
|
|
There are two core shared modules to be aware of:
|
|
|
|
* util/ - a collection of shared APIs that can be used by any
|
|
code. This directory is always in the include path
|
|
for all things built
|
|
|
|
* conf/ - APIs for parsing / manipulating all the official XML
|
|
files used by the public API. This directory is only
|
|
in the include path for driver implementation modules
|
|
|
|
* vmx/ - VMware VMX config handling (used by esx/ and vmware/)
|
|
|
|
|
|
Then there are the hypervisor implementations:
|
|
|
|
* esx/ - VMware ESX and GSX support using vSphere API over SOAP
|
|
* lxc/ - Linux Native Containers
|
|
* openvz/ - OpenVZ containers using cli tools
|
|
* phyp/ - IBM Power Hypervisor using CLI tools over SSH
|
|
* qemu/ - QEMU / KVM using qemu CLI/monitor
|
|
* remote/ - Generic libvirt native RPC client
|
|
* test/ - A "mock" driver for testing
|
|
* uml/ - User Mode Linux
|
|
* vbox/ - Virtual Box using native API
|
|
* vmware/ - VMware Workstation and Player using the vmrun tool
|
|
* xen/ - Xen using hypercalls, XenD SEXPR & XenStore
|
|
* xenapi/ - Xen using libxenserver
|
|
|
|
|
|
Finally some secondary drivers that are shared for several HVs.
|
|
Currently these are used by LXC, OpenVZ, QEMU, UML and Xen drivers.
|
|
The ESX, Power Hypervisor, Remote, Test & VirtualBox drivers all
|
|
implement the secondary drivers directly
|
|
|
|
* cpu/ - CPU feature management
|
|
* interface/ - Host network interface management
|
|
* network/ - Virtual NAT networking
|
|
* nwfilter/ - Network traffic filtering rules
|
|
* node_device/ - Host device enumeration
|
|
* secret/ - Secret management
|
|
* security/ - Mandatory access control drivers
|
|
* storage/ - Storage management drivers
|
|
|
|
|
|
Since both the hypervisor and secondary drivers can be built as
|
|
dlopen()able modules, it is *FORBIDDEN* to have build dependencies
|
|
between these directories. Drivers are only allowed to depend on
|
|
the public API, and the internal APIs in the util/ and conf/
|
|
directories
|