Revision as of 07:18, 7 October 2010

KVM-Autotest TODO list

Note: This session is for major, multi-person items. We'll update the status weekly based on the status of the subtasks attributed to persons.

Libvirt integration - Will hold on this work item for the next couple of months due to resources

Make cache=off the default for guest images
Multi host migration
Add a BLOCKED status on the autotest database, that tells the user that some feature testing was left out due to a problem on its dependencies.
Eventually get rid of all dependency on slirp/userspace networking to do any feature testing, since it is not a supported feature. Slipstreaming the kickstart in the install CD is a possibility, and it ends up being simpler than configuring an internal network thing for testing.
Make it possible to install virtio nw driver under windows xp/2003 guests without having to resort to the msi installer

Include support for host kernel install on the KVM default control file - Using autotest standard API to get it done
- needs to resolve bugs in boottool to full functionality

Make WHQL tests run on our internal server
Enable "guest-load" for a VMs before/while tests are running (e.g. migration of a VM, while a movie is playing on it)
Add a way to shutdown the VMs when the whole job completes (compared to doing nothing or shutting-down after every test)
Add docstrings to all functions that still lack them, including the ones in stepmaker.py, stepeditor.py and kvm_tests.py
Rename all Windows ISOs currently used to their official MSDN names
Fill the sections "Working with step files" and "Step file creation tips" in the wiki

Using dnsmasq in unattended_install to replace userspace network with private bridge status: have implemented in internal tree
Bonding test

pxe boot * net types
Further migration
Multiple nics
multiple disks
Test block device cancellation path using device mapper to generate errors ( after we had a crash in de_write_dma_cb)
Extend pci_assignable to support other PCI devices (USB, video cards, TV card etc)
Different CPU flags support
Use private bridge and dnsmasq to do the unattended installation
Passthrough the perf keys of run_autotest to autotest server
Register the virtual machine into autotest server and run benchmark through autotest server

@@ Line 1: / Line 1: @@
 = KVM-Autotest TODO list =
+== general ==
+'''Note:''' This session is for major, multi-person items. We'll update the status weekly based on the status of the subtasks attributed to persons.
+* Libvirt integration - Will hold on this work item for the next couple of months due to resources
 == lmr ==
@@ Line 7: / Line 13: @@
 * Make cache=off the default for guest images
 * Multi host migration
-* Libvirt integration
 * Add a BLOCKED status on the autotest database, that tells the user that some feature testing was left out due to a problem on its dependencies.
 * Eventually get rid of all dependency on slirp/userspace networking to do any feature testing, since it is not a supported feature. Slipstreaming the kickstart in the install CD is a possibility, and it ends up being simpler than configuring an internal network thing for testing.