oVirt is a complete virtualization management platform, licensed and developed as open source software. oVirt builds on the powerful Kernel-based Virtual Machine (KVM) hypervisor, and on the RHEV-M management server released by Red Hat to the open source community

A standard oVirt deployment consists of three things, primarily:

• ovirt-engine which is used use to deploy, monitor, move, stop and create VM images, configure storage, network , etc.
  
• One or more hosts (nodes), on which we run virtual machines (VMs)
  
• One or more storage nodes, which hold the images and ISOs corresponding to those VMs
  

Engine-Core Architecture
oVirt engine is a JBoss-based Java application (previously C#) which runs as a web service. This service talks directly to VDSM on the hosts to deploy, start, stop, migrate and monitor VMs, and it can also create new images on storage from templates.


Host Agent (VDSM)
VDSM is a component developed in Python, which covers all functionality required by oVirt Engine for host, VM, networking and storage management.

Prerequisites
*oVirt Engine

• Minimum - Dual core server with 4 GB RAM, with 20 GB free disk space and 1 Gbps network interface.
  
• Recommended - Dual Sockets/Quad core server with 16 GB RAM, 50 GB free disk space on multiple disk spindles and 1 Gbps network interface.
  
• The oVirt Engine must be configured to receive updates from the oVirt project's software repository, as provided by the ovirt-release package.
  
• A client for connecting to oVirt Engine.
  

For each Host (oVirt Node or Fedora Host)

• Minimum - Dual core server, 10 GB RAM and 10 GB Storage, 1 Gbps network interface.
  
• Recommended - Dual socket server, 16 GB RAM and 50 GB storage, two 1 Gbps network interfaces.
  
• The breakdown of the server requirements are as below:
  
• For each host: AMD-V or Intel VT enabled, AMD64 or Intel 64 extensions, minimum 1 GB RAM, 3 GB free storage and 1 Gbps network interface.
  
• For virtual machines running on each host: minimum 1 GB RAM per virtual machine.
  

Storage and Networking

• At least one of the supported storage types (NFS, iSCSI, FCP, Local, POSIX FS).
  
• For NFS storage, a valid IP address and export path is required.
  
• For iSCSI storage, a valid IP address and target information is required.
  
• Static IP addresses for the oVirt Engine server and for each host server.
  
• DNS service which can resolve (forward and reverse) all the IP addresses.
  
• An existing DHCP server which can allocate network addresses for the virtual machines.