 | This articlerelies excessively onreferences toprimary sources. Please improve this article by addingsecondary or tertiary sources. Find sources: "OVirt" – news ·newspapers ·books ·scholar ·JSTOR(December 2024) (Learn how and when to remove this message) |
| oVirt | |
|---|---|
 | |
| Original author | Red Hat |
| Developer | oVirt Project |
| Stable release | |
| Written in | Java |
| Operating system | Linux |
| Platform | Java |
| Available in | English,Japanese,French,German,Italian,Spanish |
| Type | Virtual machine |
| Licence | Apache License 2.0 |
| Website | www |
| Repository | |
oVirt is afree, open-sourcevirtualization management platform. It was founded byRed Hat as a community project on whichRed Hat Virtualization was based. It allows centralized management ofvirtual machines, compute, storage and networking resources, from an easy-to-use web-based front-end withplatform independent access.KVM onx86-64,PowerPC64[2][3] ands390x[4] architecture are the onlyhypervisors supported, but there is an ongoing effort to supportARM architecture in a future releases.
oVirt consists of two basic components, oVirt engine and oVirt node.
The oVirt engine backend is written inJava, while the frontend is developed withGWT web toolkit. The oVirt engine runs on top of theWildFly (former JBoss)application server. The frontend can be accessed through a webadminportal for administration, or a user portal with privileges, and features that can be fine tuned. User administration can be managed locally or by integrating oVirt withLDAP orAD services. The oVirt engine stores data in aPostgreSQLdatabase.Data warehousing andreporting capabilities depend on additional history and reports databases that can be optionally instantiated during the setup procedure. AREST API is available for customizing or adding engine features.[5]
An oVirt node is aserver runningCentOS Stream or derivatives, with KVM hypervisor enabled and a VDSM (Virtual Desktop and Server Manager)daemon written inPython. Management of resources initiated from a webadmin portal are sent through the engine backend that issues appropriate calls to the VDSM daemon. VDSM controls all resources available to the node (compute, storage, networking) and virtual machines running on it and is also responsible for providingfeedback to the engine about all initiated operations. Multiple nodes can beclustered from the oVirt engine webadmin portal to enhanceRAS.
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 avirtual appliance.[6]
oVirt is built upon several other projects includinglibvirt,Gluster,PatternFly, andAnsible.
Virtualdatacenters, managed by oVirt, are categorized into storage, networking and clusters that consist of one or more oVirt nodes.Data integrity is ensured byfencing, with agents that can use various resources such asbaseboard management controllers oruninterruptible 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:
Network management allows defining multipleVLANs that can bebridged to thenetwork interfaces available on the nodes. Configuration ofbonded interfaces,IP addresses,subnet masks andgateways on managed nodes are all supported within webadmin portal interface, as isSR-IOV on hardware configurations that support this feature.
Management features for compute resources includeCPU pinning, definingNUMA topology, enablingkernel same-page merging,memory over-provisioning,HA VM reservation etc.
Virtual machine management enables selecting high availability priority,live migration, livesnapshots, cloning virtual machines from snapshots, creating virtual machine templates, using cloud-init for automated configuration during provisioning and deployment of virtual machines. Supportedguest operating systems includeLinux,Microsoft Windows andFreeBSD. Access to virtual machines can be achieved from webadmin portal usingSPICE,VNC andRDP protocols.
oVirt can be integrated with many open source projects, includingOpenStackGlance andNeutron for disk and network provisioning,Foreman/Katello for VM/node provisioning or pulling relevant errata information into webadmin portal and can be further integrated withManageIQ for a complete virtual infrastructurelifecycle management.[7]
Disaster recovery features include the ability to import any storage domain into different oVirt engine instances andreplication can be managed from oVirt with GlusterFSgeo-replication feature, or by utilizing synchronous/asynchronous block level replication provided by storage hardware vendors. oVirt enginebackups can be automated and periodically transferred to a remote location.
oVirt supportshyper-converged infrastructure deployment scenarios.[8] Self-hosted engine andGluster-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 anysingle points of failure. oVirt provides deep integration with Gluster, including Gluster specific performance improvements.
{{cite web}}: CS1 maint: multiple names: authors list (link){{cite web}}: CS1 maint: multiple names: authors list (link)
