release blocking features for oVirt 3.1

Moran Goldboim mgoldboi at redhat.com
Wed Mar 7 16:08:02 UTC 2012


for the upcoming ovirt release we have the following 
(http://www.ovirt.org/wiki/Second_Release):


      MUST

    * *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



i would recommend adding (Musts):

    * no blockers on the lower level components - libvirt, lvm,
      device-mapper,qemu-kvm
    * all image related operations work -  copy, move, import, export,
      snapshot (vm and template)
    * ovirt/host installation should work flawlessly (w/o ssl)
    * can do all above operations (define DC hierarchy so you can run
      vm) with gui/cli/python-api/rest-api
    * vm life-cycle is working flawlessly
      (start,suspend,resume,stop,migrate)

additions, objections, thoughts?
Moran.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/arch/attachments/20120307/15de08ab/attachment.html>


More information about the Arch mailing list