Comment 2 for bug 1209421

I'm not really convinced that the test_virt_drivers test case is useful at all. For a start it can only work if the virt driver has a way to fake all its external interaction.. This works for libvirt thanks to fakelibvirt, but then by virtue of using fakelibvirt this is not really achieving any useful test coverage that we don't already have via the main libvirt test cases.

On the subject of generating a hypervisor support matrix, I think this test case is even more useless. For libvirt you would need to be able to run it for QEMU, KVM, LXC, Xen, etc and report results for each of them. This is impossible with fakelibvirt, and the unit tests can't use the real libvirt since that would make them heavily dependant on external system state.

If we want to have generated reports of supported APIs per hypervisor, then I think that realistically this has to be done using the tempest test suite, or some similar thing which validates a real world deployment of Nova against a live hypervisor.

So I think this bug should be closed as wontfix, or re-assigned to some other project. The unit tests just aren't the right place to generate a useful hypervisor support matrix.