Features/VirtTCK

From FedoraProject

< Features(Difference between revisions)
Jump to: navigation, search
(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...')
 
(update status to 100%, add to RejectedByFESCo category)
 
(12 intermediate revisions by 4 users not shown)
Line 1: Line 1:
= Feature Name =
+
= VirtTCK =
Features/VirtTCK
+
  
 
== Summary ==
 
== Summary ==
Line 11: Line 10:
 
== Current status ==
 
== Current status ==
 
* Targeted release: [[Releases/12 | Fedora 12 ]]  
 
* Targeted release: [[Releases/12 | Fedora 12 ]]  
* Last updated: (DATE)
+
* Last updated: 2009-08-05
* Percentage of completion: 10%
+
* Percentage of completion: 100%
  
 
== Detailed Description ==
 
== Detailed Description ==
Line 29: Line 28:
 
== Scope ==
 
== Scope ==
  
* libvirt-tck: extend coverage of its test suites
+
* libvirt-tck: extend coverage of its test suites [DONE]
* libvirt-tck: do a formal release upstream
+
* libvirt-tck: do a formal release upstream [DONE]
* libvirt-tck: submit package to Fedora for review & inclusion in repo
+
* libvirt-tck: submit package to Fedora for review & inclusion in repo [DONE] https://bugzilla.redhat.com/show_bug.cgi?id=513253
* libvirt: fix whatever important bugs are identified in QEMU, Xen and LXC drivers (and any other drivers for virt technology shipped in Fedora repositories)
+
* libvirt: fix whatever important bugs are identified in QEMU, Xen and LXC drivers (and any other drivers for virt technology shipped in Fedora repositories) [DONE]
* qemu/xen: fix any low level bugs not fixable in libvirt itself.
+
* qemu/xen: fix any low level bugs not fixable in libvirt itself. [DONE]
  
 
== How To Test ==
 
== How To Test ==
Line 58: Line 57:
 
== Documentation ==
 
== Documentation ==
  
* Upstream project announcement http://www.mail-archive.com/libvir-list@redhat.com/msg12703.html
+
* Upstream project announcement http://www.mail-archive.com/libvir-list@redhat.com/msg12703.html ([[FWN/Issue171#libvirt-TCK__Technology_Compatibility_Kit |FWN#171]])
 
* Upstream source repository http://libvirt.org/hg/libvirt-tck
 
* Upstream source repository http://libvirt.org/hg/libvirt-tck
  
 
== Release Notes ==
 
== Release Notes ==
  
* Proclaim how much more stable & bugfree Fedora 12 virtualization will be.
+
Fedora now includes the libvirt Technology Compatibility Kit (TCK), a functional test suite which provides detailed reports on functionality available for each libvirt driver and can be used to quickly identify failures or regressions in Fedora's virtualization features.
  
 
== Comments and Discussion ==
 
== Comments and Discussion ==
  
* See [[Talk:Features/YourFeatureName]] <!-- This adds a link to the "discussion" tab associated with your page.  This provides the ability to have ongoing comments or conversation without bogging down the main feature page -->
+
* See [[Talk:Features/VirtTCK]]
  
 
+
[[Category:FeaturePageRejectedByFESCo]]
[[Category:FeaturePageIncomplete]]
+
[[Category:F12_Virt_Features|VirtTCK]]
[[Category:F12_Virt_Features]]
+
[[Category:Virtualization|VirtTCK]]
<!-- When your feature page is completed and ready for review -->
+
<!-- remove Category:FeaturePageIncomplete and change it to Category:FeatureReadyForWrangler -->
+
<!-- After review, the feature wrangler will move your page to Category:FeatureReadyForFesco... if it still needs more work it will move back to Category:FeaturePageIncomplete-->
+
<!-- A pretty picture of the page category usage is at: https://fedoraproject.org/wiki/Features/Policy/Process -->
+
 
+
 
+
<!-- Note that the current Feature guidelines require useful Scope and Test Plans at certain milestones; QA is responsible for checking these, and will change this category as needed. -->
+

Latest revision as of 17:04, 5 August 2009

Contents

[edit] VirtTCK

[edit] Summary

Provide a functional test suite for virtualization and report on hypervisor compatability

[edit] Owner

[edit] Current status

  • Targeted release: Fedora 12
  • Last updated: 2009-08-05
  • Percentage of completion: 100%

[edit] 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.

[edit] 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.

[edit] Scope

  • libvirt-tck: extend coverage of its test suites [DONE]
  • libvirt-tck: do a formal release upstream [DONE]
  • libvirt-tck: submit package to Fedora for review & inclusion in repo [DONE] https://bugzilla.redhat.com/show_bug.cgi?id=513253
  • libvirt: fix whatever important bugs are identified in QEMU, Xen and LXC drivers (and any other drivers for virt technology shipped in Fedora repositories) [DONE]
  • qemu/xen: fix any low level bugs not fixable in libvirt itself. [DONE]

[edit] 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

[edit] User Experience

Users of official Fedora virtualization technology will experience fewer bugs / regressions of functionality.

[edit] Dependencies

  • libvirt-tck: new RPM
  • libvirt, qemu, xen: fixes for bugs identified

[edit] Contingency Plan

This is a new testing framework, and no existing functionality will be impacted, so no contingency is required.

[edit] Documentation

[edit] Release Notes

Fedora now includes the libvirt Technology Compatibility Kit (TCK), a functional test suite which provides detailed reports on functionality available for each libvirt driver and can be used to quickly identify failures or regressions in Fedora's virtualization features.

[edit] Comments and Discussion