oVirt
 |
 | |
| Original author(s) | Red Hat |
|---|---|
| Developer(s) | oVirt Project |
| Stable release | 4.5.5[1]
/ December 1, 2023 |
| Repository | |
| Written in | Apache License 2.0 |
| Website | www |
oVirt is a
Architecture
oVirt consists of two basic components, oVirt engine and oVirt node.
The oVirt engine backend is written in
An oVirt node is a
The oVirt engine can be installed on a standalone server, or can be hosted on a cluster of nodes themselves inside a virtual machine (self-hosted engine). The self-hosted engine can be manually installed or automatically deployed via a virtual appliance.[6]
oVirt is built upon several other projects including libvirt, Gluster, PatternFly, and Ansible.
Features
Virtual datacenters, managed by oVirt, are categorized into storage, networking and clusters that consist of one or more oVirt nodes. Data integrity is ensured by fencing, with agents that can use various resources such as baseboard management controllers or uninterruptible power supplies.
Storage is organized within entities called storage domains and can be local or shared. Storage domains can be created using the following storage solutions or protocols:
- NFS
- iSCSI
- Fibre Channel
- POSIX compliant filesystem
- GlusterFS
Network management allows defining multiple
Management features for compute resources include CPU pinning, defining NUMA topology, enabling kernel same-page merging, memory over-provisioning, HA VM reservation etc.
Virtual machine management enables selecting high availability priority,
protocols.oVirt can be integrated with many open source projects, including OpenStack Glance and Neutron for disk and network provisioning, Foreman/Katello for VM/node provisioning or pulling relevant errata information into webadmin portal and can be further integrated with ManageIQ for a complete virtual infrastructure lifecycle management.[7]
oVirt supports hyper-converged infrastructure deployment scenarios.[8] Self-hosted engine and Gluster-based storage domains allow centralized management of all resources that can be seamlessly expanded, simply by adding an appropriate number of nodes to the cluster, without having any single points of failure. oVirt provides deep integration with Gluster, including Gluster specific performance improvements.
See also
- Red Hat Virtualization (RHV)
- Kernel-based Virtual Machine (KVM)
- Comparison of platform virtualization software
References
- ^ "OVirt 4.5.5 Release Notes".
- ^ Gustavo Frederico Temple Pedrosa, Vitor de Lima, Leonardo Bianconi (2014). "Engine support for PPC64". Retrieved 25 January 2020.
{{cite web}}: CS1 maint: multiple names: authors list (link) - ^ Gustavo Frederico Temple Pedrosa, Vitor de Lima, Leonardo Bianconi (2014). "VDSM for PPC64". Retrieved 25 January 2020.
{{cite web}}: CS1 maint: multiple names: authors list (link) - ^ "Nodes [Jenkins]". jenkins.ovirt.org. Retrieved 2021-11-11.
- ^ Ourfali, Oved. "Scripting and integration with oVirt" (PDF). Retrieved 26 December 2015.
- ^ Tiraboschi, Simone. "oVirt self-hosted engine seamless deployment" (PDF). Retrieved 26 December 2015.
- ^ "External Network Providers". oVirt. Retrieved 2023-09-18.
- ^ Chaplygin, Denis (29 January 2018). "Improving Hyperconverged Performance". Retrieved 9 February 2018.
