Jump to: navigation, search

oVirt 3.3 release notes


The oVirt Project is pleased to announce the availability of its fourth formal release, oVirt 3.3.

oVirt is an open source alternative to VMware vSphere, and provides an awesome KVM management interface for multi-node virtualization.

To find out more about features which were added in previous oVirt releases, check out the oVirt 3.2 release notes and oVirt 3.1 release notes. For a general overview of oVirt, read the oVirt 3.0 feature guide and the about oVirt page.

Contents

What's New in 3.3?

OpenStack Integration

  • Neutron Integration adds support for using OpenStack Neutron as an external network provider, which can provide networking capabilities for consumption by oVirt hosts and/or virtual machines. For more information, watch this deep dive presentation on oVirt / Neutron integration.
  • Glance Integration allows oVirt users to consume, export and share images with Glance. These images are exposed as oVirt Templates. For more information, watch this deep dive presentation on oVirt / Glance integration.
  • Cloud-Init Integration facilitates provisioning of virtual machines by enabling oVirt to perform initial setup (including networking, SSH keys, timezone, user data injection, and more) of guest instances configured with cloud-init.

Enhanced Gluster Support

  • GlusterFS Storage Domain is a new storage domain and data center type which uses gluster as the storage backend. VMs created using this domain take advantage of QEMU's gluster block backend for improved performance.
    • This feature is currently only available on Fedora 19. We're working on a solution for EL6 and hope to have it available soon.
  • Gluster Hooks Management allows users to manage Gluster hooks (Volume lifecycle extensions) from oVirt Engine. Read more about Gluster hooks at the Gluster project site.

More Extensibility Options

  • oVirt Scheduler API allows users to implement their own private optimized schedulers y extending or modifying the default oVirt scheduler.
    • This feature is not included in oVirt 3.3, but will be added in an upcoming release during the 3.3 release cycle
  • Device Custom Properties allow administrators to define special parameters per VM virtual device, and pass them down to vdsm hooks, as has previously been possible on a per VM basis. Device custom properties will allow, for instance, for users to connect vNICs to non-standard host networks.
  • External Tasks Support makes it possible for a third-party plugin to inject tasks into oVirt Engine using the REST API, to change task statuses and allow them to be tracked from the UI.
  • Backup-Restore API Integration provides the ability for ISVs to backup and restore VMs. A new set of APIs will be introduced in oVirt to facilitate taking full VM backup, as well as full or file level restore of VMs.
  • Support for Branding the oVirt Management Console
  • Java-SDK is an auto-generated software development kit for the oVirt engine api.
  • Disk Hooks adds VDSM hooking points before and after disk hot plug and hot unplug events, enabling the running of guest-level operations on the disks when they're plugged/unplugged.

Other Enhancements

Virt

  • RAM Snapshots enable users to save (and later restore) the memory state of a VM when creating a live snapshot.
  • noVNC console integration makes it possible to connect to VM consoles using the HTML 5 VNC client called "noVNC" in browsers supporting websockets and the HTML5 postMessage function (webkit browsers, Firefox, IE > 10).

Infra

  • SuperVDSM Service enables Vdsm to be run as an unprivileged daemon, thereby simplifying the handling of crashes and the process of re-establishing communication between Vdsm and Supervdsm after failures.
  • Public Key SSH Authentication is now available as a means of conducting authentication for host-deploy and node upgrade operations, supplementing the existing user/password mechanism.
  • Java SDK (Software Development Kit) is now available.

Networking

  • Migration Networks enable administrators to assign networks for carrying migration data.
  • Normalized ovirtmgmt Initialization involves generating the ovirtmgmt network based on DC definitions using the setupNetworks function, rather than during new host deployment.
  • Feature/NetworkReloaded reimplementation of configNetwork in vdsm. Should have zero (0) effect on users, but required for future support for ovs/NM
  • Multiple Gateways allows users to define a gateway per logical network, where, previously, the gateway defined on the ovirtmgmt logical network had been treated as the host-wide default gateway.

Storage

  • Online Virtual Drive Resize allows oVirt users to resize virtual disks while they are in use by one or more virtual machines without the need of pausing, hibernating or rebooting the guests.
  • Virtio-SCSI is a new para-virtualized SCSI controller device which provides the same performance as the virtio-blk device, while improving scalability, supporting standard SCSI command sets and device naming, allowing for SCSI device passthrough.
  • Read Only Disk enables users to assign a read-only property to the VM-Disk relationship when adding/attaching a disk to a vm through the oVirt engine.
  • Manage Storage Connections adds the ability to add, edit and delete storage connections. The new connection details must match those of the original connection. For example, an NFS storage connection cannot be edited to point to iSCSI.
  • MoveAsCopyAndDelete splits disk moving operations in oVirt into separate copy and delete operations, where, previously, they had been carried out by vdsm in a single operation. This change improves availability and error-handling.
  • Allow resign/force re-election of SPM
  • Disks Block Alignment provides a way in oVirt to find virtual disks with misaligned partitions.

SLA & Scheduling

Node

  • Universal Node Image converts the oVirt Node image into a generic image that can be customized for many different projects using Node Plugins.
  • Node VDSM Plugin converts the generic oVirt Node image into an image customized use with oVirt Engine.
  • oVirt Node works on a different asynchronous release schedule from the rest of oVirt.
    • At the time of the oVirt 3.3 release, the current version of ovirt-node will be 3.0.1.
    • Feature for oVirt node 3.0.0 can be found on the oVirt Node 3.0.0 release page

Integration

  • Otopi Infra Migration involves a complete rewrite of the engine-setup, engine-cleanup, engine-upgrade and All-in-One plugin using otopi.
  • Self Hosted Engine enables administrators to run the Engine as a VM on the hosts that are managed by this Engine, in an HA configuration, when the Engine VM can start on any of the hosts.
    • This feature is not included in oVirt 3.3, but will be added in an upcoming release

UX Enhancements

Deep dives

In anticipation of the 3.3 release, a number of deep dive presentations into 3.3 features are being prepared.