m (Changed category) |
m (internal link cleaning) |
||
| Line 30: | Line 30: | ||
Things to test, roughly in dependency order: | 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. | 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. | ||
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:
- Paniraja KM, Dell Inc
- add your name here
What's needed to test[edit]
- A fully updated Fedora 12 Rawhide machine. See instructions on the main test day page.
- At least one guest image installed before the test day (suggested reading - Virtualization_Quick_Start)
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 |