call for tests

[James Laska]

On Fri, 2010-12-03 at 14:01 -0500, Chris Lumens wrote:
> > > Install / to a LV over raid10 after first reducing the LVs in the VG to 
> > > gain the space, /boot on an available partition, mount all other LV 
> > > distros and their /boot partitions, mount all other non-LV partitions.
> > 
> > Chris: Another case that would need partition resize kickstart support?
> 
> Yep.  We may be able to do something very clever and override some part
> of anaconda to inject a ResizeAction into the action list, but I'm
> worried that will be: (1) complicated, (2) fragile, (3) difficult for
> anyone else to use.
> 
> Adding kickstart resize syntax doesn't seem easy to me either.

I think you may have stated this already, which of the manual
installation validation storage tests [1] are now automated using your
unittests?

Trying to think of additional tests ...

I think bcl (or pjones) mentioned creating a iSCSI test case where we
start an iSCSI target on the virt host, and include iSCSI initiator
information in the kickstart.  Might be fun, but I likely not in the
category "easy".

With regards to different devices, is there any value in testing
different qemu storage drivers (PATA, SATA, SCSI, USB)?

Thanks,
James

[1] http://fedoraproject.org/wiki/QA:Fedora_14_Install_Results_Template
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part
Url : http://lists.fedoraproject.org/pipermail/test/attachments/20101203/dd2f79bc/attachment.bin