(Created page with '= Feature Name = Features/VirtTCK == Summary == Provide a functional test suite for virtualization and report on hypervisor compatability == Owner == * Name: [[User:berrange| D...') |
(minor tweaks) |
||
| Line 1: | Line 1: | ||
= Feature Name = | = Feature Name = | ||
VirtTCK | |||
== Summary == | == Summary == | ||
| Line 11: | Line 11: | ||
== Current status == | == Current status == | ||
* Targeted release: [[Releases/12 | Fedora 12 ]] | * Targeted release: [[Releases/12 | Fedora 12 ]] | ||
* Last updated: | * Last updated: 2009-05-20 | ||
* Percentage of completion: 10% | * Percentage of completion: 10% | ||
| Line 67: | Line 67: | ||
== Comments and Discussion == | == Comments and Discussion == | ||
* See [[Talk:Features/ | * See [[Talk:Features/VirtTCK]] | ||
<!-- Category:FeatureReadyForWrangler --> | |||
[[Category:FeaturePageIncomplete]] | [[Category:FeaturePageIncomplete]] | ||
[[Category:F12_Virt_Features]] | [[Category:F12_Virt_Features|VirtTCK]] | ||
Revision as of 10:28, 20 May 2009
Feature Name
VirtTCK
Summary
Provide a functional test suite for virtualization and report on hypervisor compatability
Owner
- Name: Daniel Berrange
- email: berrange@fedoraproject.org
Current status
- Targeted release: Fedora 12
- Last updated: 2009-05-20
- Percentage of completion: 10%
Detailed Description
The libvirt management API provides drivers for a wide variety of virtualization platforms. Not all platforms have an equivalent level of support in libvirt. The libvirt TCK will provide a tool which will do functional testing of libvirt drivers. It will generate reports demonstrating the functionality available in Fedora for each supported libvirt driver. It will also quickly identify unexpected failures / regressions, allowing quality of virtualization platform in Fedora to be further improved prior to release of new RPMs.
Benefit to Fedora
Application developers will have a clear guide to the level of support in libvirt for each virtualization technology included in Fedora (QEMU/KVM, LXC (containers) and potentially a reappearance of Xen dom0).
Application developers will be able to determine the level of support for 3rd party virtualization technologies not included in the main Fedora repositories (OpenVZ, VirtualBox, etc)
The Fedora testing & virtualization teams will be able to verify correct operation of new packages in Fedora and thus avoid many regressions for users.
End users will see fewer regressions and bugs in the virtualization technologies.
Scope
- libvirt-tck: extend coverage of its test suites
- libvirt-tck: do a formal release upstream
- libvirt-tck: submit package to Fedora for review & inclusion in repo
- libvirt: fix whatever important bugs are identified in QEMU, Xen and LXC drivers (and any other drivers for virt technology shipped in Fedora repositories)
- qemu/xen: fix any low level bugs not fixable in libvirt itself.
How To Test
- Create a configuration file to determine which driver / functionality will be tested
- Run the libvirt-tck command using this configuration
- .....somehow..... determine regressions and file bugs for unexpected failures
NB. really need some report 'diff' tool to distinguish regressions, vs intentionally missing features
User Experience
Users of official Fedora virtualization technology will experience fewer bugs / regressions of functionality.
Dependencies
- libvirt-tck: new RPM
- libvirt, qemu, xen: fixes for bugs identified
Contingency Plan
This is a new testing framework, and no existing functionality will be impacted, so no contingency is required.
Documentation
- Upstream project announcement http://www.mail-archive.com/libvir-list@redhat.com/msg12703.html
- Upstream source repository http://libvirt.org/hg/libvirt-tck
Release Notes
- Proclaim how much more stable & bugfree Fedora 12 virtualization will be.