oVirt 3.2 release-management

Timeline

  • General availability: 2013-02-14
    • Beta release: 2013-01-24
    • Feature freeze: 2013-01-14
    • Test Day: 2013-01-29

Tracker Bug

Release Criteria

Tracker bug: https://bugzilla.redhat.com/881006

General

  • All sources must be available on ovirt.org

MUST

  • MUST: No blockers on the lower level components - libvirt, lvm,device-mapper,qemu-kvm, Jboss, postgres, iscsi-initiator
  • MUST: All image related operations work - copy, move, import, export, snapshot (vm and template)
  • MUST: Ovirt/host installation should work flawlessly (w/o SSL)
  • MUST: Fully operational flow (define DC hierarchy so you can run vm) with GUI/CLI/Python-API/REST-API
  • MUST: vm life-cycle is working flawlessly (start,suspend,resume,stop,migrate)
  • MUST: Upgrade from previous release
  • MUST: ovirt-node full cycle (register, approve and running VM)
  • MUST: No known data corruptors
  • MUST: Can define NFS, iSCSI, FC and local based storage domains
  • MUST: Can define VLAN based networks, bond interfaces, and have VLANs over bonded interfaces
  • MUST: Can authenticate users against at least one external LDAP server
  • MUST: Can run multiple VMs
  • MUST: Can connect to VMs using SPICE
  • MUST: Have Release Notes with feature specific information
  • MUST: Have updated quick start guide available
  • MUST: No regressions from 3.1 Release

SHOULD

  • SHOULD: Can run full cycle with gluster storage
  • SHOULD: have updated installation guide available

Features

Features being considered for inclusion/already in master: