[Users] oVirt Roadmap feature requests - Summary

so, a lot of input post my question for 3.4 planning on "what do you want next"[1] I've just aggregated the replies here at this point for easier processing going forward: Infra - ability to give permissions to group of objects (namely, VMs) - support users/groups in oVirt DB as an authentication provider - support keystone as an authentication provider - kerberos login to webadmin/user portal - stateless host (pxe boot, no local disks) - detect updates and update host accordingly - embedded pxe/tftp boot server, setup to deploy the nodes - snmp & snmp trap monitoring Virt - template versions (ability to update template of a pool) - pci passthrough for devices like Telephone modem, PCI-express cards, Graphic cards - usbhost hook as supported feature (hardware license tokens) - ability to provide libvirt features directly[2] - dependencies between VMs (start db vm before webapp vm) - Allow to clone a VM without snapshot/template - Integrate v2v into engine - oVirt guest agent for Ubuntu/openSUSE/SLES/Debian - compatibility with OVF 2.0.1 - solaris as supported guest OS Network - private network between VMs - Network NAT for VMs (with buildin DHCP). - openvswitch support (in 3.3, via neutron?) - nic ordering Storage - import existing data domain - live merge (delete snapshot) - ability to resize a storage domain lun - multiple storage domains (local/gluster/FC) - ISO and export domains on FC/iSCSI - Upload ISOs within the GUI to ISO domain - Use an existing share for ISO domain - A backup and restore option - iSCSI EqualLogic SAN support or use standard iscsi tools/configuration - ATA over ethernet (AoE) as an optional storage transport - DR - DRBD, either with CLVM or perhaps GFS - live disk resize - disk ordering SLA - positive/negative affinity between group of VMs - power saving policy moving hosts to sleep - time based policy (SLA during the day, power saving at night) - collect and show power consumption of hosts - allow to give weights to prefer "faster" hosts to other hosts - application level HA (monitor the service inside the VM) Other - Zabbix monitoring [1] http://lists.ovirt.org/pipermail/users/2013-August/015807.html [2] http://lists.ovirt.org/pipermail/engine-devel/2013-August/005364.html