KVM-Autotest/TODO: Difference between revisions

From KVM
No edit summary
m (Add categories)
 
(53 intermediate revisions by 9 users not shown)
Line 1: Line 1:
= KVM-Autotest TODO list =
= KVM-Autotest TODO list - DEPRECATED =


== raw idea ==
KVM autotest is the set of kvm tests implemented on top of the [http://autotest.github.com/ autotest] framework. The current documentation can be seen on the [https://github.com/autotest/autotest/wiki/KVMAutotest autotest wiki], please refer to it. We'll port the remaining items to the autotest issue tracker.


* more vhost_net test
== Pradeep ==
* Add Multi-guests transfer test
* transfer test between guest(s) and extra boxs
* add more whql tests (virtio_net,virtio_blk)


== general ==
* SLES support - 
** Owner - Onkar n Mahajan (currently working)
** Expected delivery to community -


'''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.
* virtio-blk disk serial # test (extend physical_resource_check test)
** Owner -
** Expected delivery to community-


* Libvirt integration - Will hold on this work item for the next couple of months due to resource constraints.
* enhance virtio-blk hotplug test
** virsh based attach-disk/detach disk
** enumerate cloud scenarios (live add, reboot after, shutdown, etc.)
** migration after live add
** Owner -
** Expected delivery to community- 1-Oct-2011


== lmr ==
* Add use QED image format during tests.
** Owner -
** Expected delivery to community- 1-Dec-2011


=== TODO ===
* virsh stream.
** Owner -
** Expected delivery to community-


* Multi host migration - priority increased
* pci-multi function testing (>32 virtio devices, disk and network)
** test out max number of virtio blk and nic devices
** Owner -
** Expected delivery to community-


* Infrastructure for testing different vm storage backends: file/lvm/iSCSI
* virtfs patch inclusion to autotest.
* Work on setting up the conmux server for our internal test grid
** Owner -
* Research how to trigger jobs based on events rather than using the web interface setting recurrent jobs
** Expected delivery to community-
* Set up a qemu-block job, with kwolf's qemu-block tree
* Set up a vhost job, with the upstream job (mst's trees for kernel and userspace)
* 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


=== Done ===
* Windows support (ping, file_transfer, ... network tests needs to be added)
** Owner -
** Expected delivery to community-


* Send code to retrieve host kernels based on koji/brew tags upstream
* Svirt - sVirt is a community effort aimed at integrating Mandatory Access Control (MAC) security and Linux-based virtualization (KVM, lguest et al).
* Resolved UUID mount point check problem
** Owner - Onkar N Mahajan (currently working)
* QMP suite integrated upstream
** Expected delivery to community-
* Wrote code to retrieve kernels based on koji/brew tags


== mgoldish ==
* "Migration + other task with parallel "
** Owner -
** Expected delivery to community-


* Make WHQL tests run on our internal server
* Network rate limiting
* Enable "guest-load" for a VMs before/while tests are running (e.g. migration of a VM, while a movie is playing on it)
** Owner -
** This may just be a matter of moving useful code from tests to kvm_test_utils.py to make it reusable
** Expected delivery to community-
* Post-commit review of new network patches (committed on Oct 7 2010)
* Use more exceptions in utility functions:
** Add convenience functions to kvm_subprocess.py to make running shell commands shorter
** Add convenience functions to the VM class
* Refactor _get_command_output() and friends in kvm_monitor.py and add cmd_raw(), cmd_obj() and cmd_qmp() as required by Luiz Capitulino's test suite
* Use select() instead of sleep() in kvm_monitor.py
* Simplify migration code if possible (in kvm_vm.py and kvm_test_utils.py)
* Fix VM.get_ifname() somehow (uses self.vnc_port -- bad)


== akong ==
* Fix old autoetst patches/bugs
** Owner -
** Expected delivery to community-


* Report problem with multiple NICs and MAC address tracking
* Include libvirt_cim in autotest
* Using dnsmasq in unattended_install to replace userspace network with private bridge
** Owner -
* Bonding test
** Expected delivery to community-
* Add a new test: check if guest transmits packets when link is up/down


== jason ==
* Power Support
** Owner - IBM
** Expected Delivery to the community - Oct. 2011


* Tests in parallel with migration (reboot/unattended installation/file transfer/ autotest client tests / guest_script,autoit? / memtest86+(steps?)), need modifications to framework?
[[Category:Docs]][[Category:Historical]][[Category:Testing]][[Category:Redirects]]
* Refactor hotplug test using qdev and netdev_del/drive_del
* Refactor the network cmdline generation, using peer when possible and vlan for elder qemu-kvm
* Port network tests into windows
* Migration to exec test suggested by mst
 
== yolkfull ==
 
* Run netperf test between two guests
* Migration with/without workload(dbench,lmbench etc)
* Verify SMBIOS/DMI data (UUID, for example)
* Disk serial number (for IDE, SCSI, VirtIO drives)
 
== Beijing QE ==
 
* 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
* Passthrough the perf keys of run_autotest to autotest server
* Register the virtual machine into autotest server and run benchmark through autotest server
 
== Bugs ==
 
* Please open bugs on the [[http://autotest.kernel.org/newticket autotest defect tracking system]]

Latest revision as of 16:11, 16 May 2015

KVM-Autotest TODO list - DEPRECATED

KVM autotest is the set of kvm tests implemented on top of the autotest framework. The current documentation can be seen on the autotest wiki, please refer to it. We'll port the remaining items to the autotest issue tracker.

Pradeep

  • SLES support -
    • Owner - Onkar n Mahajan (currently working)
    • Expected delivery to community -
  • virtio-blk disk serial # test (extend physical_resource_check test)
    • Owner -
    • Expected delivery to community-
  • enhance virtio-blk hotplug test
    • virsh based attach-disk/detach disk
    • enumerate cloud scenarios (live add, reboot after, shutdown, etc.)
    • migration after live add
    • Owner -
    • Expected delivery to community- 1-Oct-2011
  • Add use QED image format during tests.
    • Owner -
    • Expected delivery to community- 1-Dec-2011
  • virsh stream.
    • Owner -
    • Expected delivery to community-
  • pci-multi function testing (>32 virtio devices, disk and network)
    • test out max number of virtio blk and nic devices
    • Owner -
    • Expected delivery to community-
  • virtfs patch inclusion to autotest.
    • Owner -
    • Expected delivery to community-
  • Windows support (ping, file_transfer, ... network tests needs to be added)
    • Owner -
    • Expected delivery to community-
  • Svirt - sVirt is a community effort aimed at integrating Mandatory Access Control (MAC) security and Linux-based virtualization (KVM, lguest et al).
    • Owner - Onkar N Mahajan (currently working)
    • Expected delivery to community-
  • "Migration + other task with parallel "
    • Owner -
    • Expected delivery to community-
  • Network rate limiting
    • Owner -
    • Expected delivery to community-
  • Fix old autoetst patches/bugs
    • Owner -
    • Expected delivery to community-
  • Include libvirt_cim in autotest
    • Owner -
    • Expected delivery to community-
  • Power Support
    • Owner - IBM
    • Expected Delivery to the community - Oct. 2011
Retrieved from "https://linux-kvm.org/index.php?title=KVM-Autotest/TODO&oldid=173292"