Just bumping this thread as a reminder, the list of blockers for the next 
release is to be finalized in this weeks sync meeting. Not much appears to have 
changed on the Wiki page in the interim though.

Please ensure that all proposed blockers are added to the page prior to the 
meeting so we can go through them and ensure everybody is on board. Moran I 
would suggest adding your suggestions directly to the Wiki page so they aren't 
lost. We can always pull those that people don't agree with during the meeting.

    http://www.ovirt.org/wiki/Second_Release

Thanks,

Steve

----- Original Message -----
> From: "Moran Goldboim" <[email protected]>
> To: [email protected]
> Sent: Wednesday, March 7, 2012 11:08:02 AM
> Subject: release blocking features for oVirt 3.1
> 
> 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.
> 
> _______________________________________________
> Arch mailing list
> [email protected]
> http://lists.ovirt.org/mailman/listinfo/arch
> 
_______________________________________________
Arch mailing list
[email protected]
http://lists.ovirt.org/mailman/listinfo/arch

Reply via email to