From Fedora Project Wiki

m (internal link cleaning)
 
(One intermediate revision by one other user not shown)
Line 30: Line 30:
Things to test, roughly in dependency order:
Things to test, roughly in dependency order:


https://fedoraproject.org/wiki/Features/VirtStorageManagement#How_To_Test
[[Features/VirtStorageManagement#How_To_Test]]


Note that the NPIV test case requires a SAN that supports NPIV, which costs a non-trivial amount of money.  If you are reading this and don't have a SAN, you won't be able to do that test, but testing discovery with an iSCSI or other SCSI adapter will still be helpful.
Note that the NPIV test case requires a SAN that supports NPIV, which costs a non-trivial amount of money.  If you are reading this and don't have a SAN, you won't be able to do that test, but testing discovery with an iSCSI or other SCSI adapter will still be helpful.
Line 43: Line 43:
|}
|}


[[Category:Test Days]]
[[Category:Fedora_12_Test_Days]]
[[Category:Virtualization]]
[[Category:Virtualization]]

Latest revision as of 09:19, 18 September 2016

DATE TIME WHERE
Thursday Sep 17, 2009 All day #fedora-test-day (webchat)

What to test?[edit]

This part of today's Fedora Test Day will focus on testing the virtualization storage management feature in F12.

If you come to this page after the test day is completed, your testing is still valuable, and you can use the information on this page to test libvirt and provide feedback.

Who's available[edit]

David Allan is your host for today.

The following people have also agreed to be available for testing, workarounds, bug fixes, and general discussion:

What's needed to test[edit]

Test Cases[edit]

Things to test, roughly in dependency order:

Features/VirtStorageManagement#How_To_Test

Note that the NPIV test case requires a SAN that supports NPIV, which costs a non-trivial amount of money. If you are reading this and don't have a SAN, you won't be able to do that test, but testing discovery with an iSCSI or other SCSI adapter will still be helpful.

Issues that were identified[edit]

Tester Description Bug references Status
#XXXXX ASSIGNED