oVirt 3.0 release notes

The oVirt Project is pleased to announce the availability of its first formal release, oVirt 3.0.

  1. oVirt 3.0 release notes
    1. Software Development Kit
      1. Features
      2. Resolved Issues
      3. Known Issues
      4. Known Issues
    2. Engine
      1. Features
      2. Resolved Issues
    3. Packaging & Installer
      1. Features
      2. Resolved Issues
      3. Known Issues
    4. Node
      1. Features
      2. Resolved Issues
      3. Known Issues
    5. VDSM
      1. Features
      2. Resolved Issues
    6. Data Warehouse and Reports

Software Development Kit

The oVirt Engine Software Development Kit provides an enhanced Python environment to support the development of custom software utilizing the APIs exposed by the engine.

Features

  • This is the initial formal release of the oVirt Engine SDK.

Resolved Issues

  • Use direct URI on get(id=x) rather than search pattern.
  • Extension to support the addition of new clusters (BZ#782707).
  • Added connectivity check and disconnect methods (BZ#781820).

Known Issues

  • An application can only create one proxy to the API.

Known Issues

The following items are not yet supported, but are on the roadmap:

  • Command history.
  • Command auto completion.

Engine

The oVirt Engine is a feature-rich server virtualization management system that provides advanced capabilities for managing open virtualization infrastructure.

Features

Resolved Issues

Packaging & Installer

The packaging & install subproject deals with the creation of the packages for the oVirt Engine and associated subcomponents. This subproject also delivers the engine-setup and engine-cleanup utilities. The engine-setup utilitiy is used to configure oVirt Engine while the engine-cleanup utility is used to remove it.

Features

  • Support for JBoss AS7 on Fedora 16

Resolved Issues

Known Issues

  • No upgrade procedure is currently available, to upgrade between releases, both nightlies and stable, it is necessary to run engine-cleanup and reinstall oVirt Engine.
  • As JBoss AS7 does not follow symlinks, some files are currently copied in the %post section of the ovirt-engine package.(BZ#782567)

Node

The oVirt Node is distributed as a compact image for use on a variety of installation media. It provides a minimal Linux installation including all the packages necessary to register and communicate with the oVirt Engine while functioning as a virtualization host. For a more detailed release note for this component see please see the Node_Release_Notes page. Some highlights are included here.

Features

  • Support for UEFI has been added.
  • Node now successfully registers and functions with oVirt Engine.

Resolved Issues

  • Automatically log out sessions that are inactive for 15 min
  • validate the iscsi iqn name
  • persist dns entries correctly when adding manually and also using dhcp
  • various spec file cleanup

Known Issues

  • Bugzilla queries listing known outstanding issues and feature requests relevant to the oVirt Node are listed at Node_Backlog.

VDSM

The VDSM service is used by a virtualization manager to interface with Linux based virtualization hosts. VDSM manages and monitors the host’s storage, memory and networks as well as virtual machine creation, other host administration tasks, statistics gathering, and log collection. This initial oVirt Project release provides and supports vdsm-4.9.3.3.

It is important to use your most up-to-date Fedora, with `iscsi-initiator-utils-6.2.0.872-16.fc16.x86_64` or later.

Features

  • It is now possible to install VDSM on existing Fedora instances, providing an alternative to consuming it as deployed with ovirt-node.
  • It is now possible to successfully register VDSM hosts with ovirt-engine, instead of just Red Hat Enterprise Virtualization Manager as was previously the case.
  • The mount subsysttem has been refactored, adding support for generic filesystem storage servers (not only NFSv3).
  • A new verb, migrateCancel, has been added.

Resolved Issues

Data Warehouse and Reports

No packaging for the components will be released as part of the inital oVirt Project release.