From Fedora Project Wiki

oVirt engine 3.1


The oVirt engine is the management application of the oVirt virtualization platform. Version 3.1 is the latest version, including the GUI and many important new features.


Current status

  • Targeted release: Fedora 18
  • Last updated: 3 Oct 2012
  • Percentage of completion: 100%

Jhernand (talk) The feature is complete now, however we had to use the first alternative of the contingency plan, as GWT is not yet available in Fedora.

Jhernand (talk) 20:37, 9 August 2012 (UTC) - The first Fedora 18 build (after branching) is completed and available here.

Jhernand (talk) 20:09, 9 August 2012 (UTC) - A new rawhide build based in the just released upstream version 3.1.0 is now available here.

Jhernand (talk) 14:52, 7 August 2012 (UTC) - A new rawhide build containing all the new features in upstream 3.1 is now available here. It doesn't contain the GUI applications as GWT is not yet available. We will probably go for the first alternative in the contingency plan.

Jhernand (talk) 20:38, 1 August 2012 (UTC) - The first Koji scratch build based in latest rawhide and in the latest upstream 3.1 branch finished correctly.

Detailed Description

Version 3.0 of the oVirt engine was already included in Fedora 17, but we want to bring the new features provided by version 3.1 and we want also to include the GUI applications (web admin and user portal) that were not included because they require GWT.

Benefit to Fedora

Adding version 3.1 of the oVirt engine and the GUI applications to Fedora will attract users that are currently using the upstream project and will provide a complete and seamless virtualization management solution, with a web interface that can be used from virtually any place.


The scope of the feature includes the update to upstream version 3.1 and the addition of the GUI applications that were not included in Fedora 17.

How To Test

In order to test the user will need to install the ovirt-engine package in any Fedora supported platform (the packages are noarch):

yum install ovirt-engine

Once the feature is 100% completed this will download and install all the required packages, including the GUI applications.

After the installation the user will need to run the engine-setup command line tool. This tool will ask for the details of the environment (ports, passwords, host names, etc), will take care to do all the required configuration changes and will start the required services.

Once the setup is completed and the services up and running the user will use the GUI applications to add hypervisors (using oVirt node or Fedora itself), configure storage and manage virtual machines.

See the testing section of the oVirt wiki for detailed instructions.

User Experience

Users will have the ability to setup a complete virtualization management environment using GUI tools.


The major dependencies of this feature is GWT 2.4.0 (Google Web Toolkit [1]) and GWT-P (GWT Platform [2]). The rest of the dependencies of oVirt engine where added to Fedora as part of the effort to include version 3.0 of the oVirt engine.

We intend to work closely with the owners of other features that also require GWT.

In addition some of the oVirt engine sub-packages have been converted to standalone packages. These are the review request bugs:

Package Bug
ovirt-log-collector RHBZ #831878
ovirt-iso-uploader RHBZ #831881
ovirt-image-uploader RHBZ #831883

Contingency Plan

In case we can't complete the feature by freeze date we have two alternatives:

  • Update to upstream version 3.1 of the oVirt engine, but don't include the GUI. We will need to do this if we are not able to have GWT packaged by freeze date.
  • Keep the current 3.0 version, as no other package in Fedora depends on the oVirt engine packages at the moment.

The second alternative is extremely unlikely to happen, as we think that the update to upstream 3.1 will be very smooth.


Release Notes

The version 3.1 of the oVirt engine includes the web based user interface for administrators and users, and many new features, for example:

  • Live snapshots
  • Shared disks
  • External disks
  • Disk and network interface hotplug
  • Quotas
  • CPU pinning
  • Jumbo frames
  • Pre-started virtual machine pools
  • Clone virtual machine from snapshot
  • POSIX file system storage
  • Support for Red Hat directory server and IBM Tivoly Directory Server
  • Support for remote database
  • Use of ports 80 and 443 for the web interface
  • All in one (engine and hypervisor in the same machine)

Comments and Discussion