Oh wow. This looks like a very, very promising start. I'm really excited to get some time to test this some more. First, a quick comment:
----- "James Laska" jlaska@redhat.com wrote:
I spoke to Richard Jones on IRC about this. Richard has been developing libguestfs (http://libguestfs.org - a library for accessing virtual disk images). He suggested that guestfs (aka python-libguestfs) could be used to accomplish this and provided a sample python snippet that might help accomplish what you'd need (see attached python file). This looks promising, might be worth exploring as a way to provide the ks.cfg to the guest without needing to modify the initrd.img.
Yeah, you could definitely create the disk image in advance and pull the ks.cfg off it before installing - or we could create an *extra* disk image and pretend it's a USB flash drive or similar. We'd just need to remember to modify the kickstart to not format all drives (or to use libvirt to remove the drive once we've loaded the ks.cfg/updates.img/etc.)
Either way would work equally well, but to test all of the stuff in the installation test plan we'll eventually need to implement both methods *and* the http/ftp methods.
I think the local-disk methods are probably simpler to start out with, though.
Anyway: thanks for all your hard work, Liam!
-w
On 02/02/2010 06:30 AM, Will Woods wrote:
Oh wow. This looks like a very, very promising start. I'm really excited to get some time to test this some more. First, a quick comment:
----- "James Laska"jlaska@redhat.com wrote:
I spoke to Richard Jones on IRC about this. Richard has been developing libguestfs (http://libguestfs.org - a library for accessing virtual disk images). He suggested that guestfs (aka python-libguestfs) could be used to accomplish this and provided a sample python snippet that might help accomplish what you'd need (see attached python file). This looks promising, might be worth exploring as a way to provide the ks.cfg to the guest without needing to modify the initrd.img.
Yeah, you could definitely create the disk image in advance and pull the ks.cfg off it before installing - or we could create an *extra* disk image and pretend it's a USB flash drive or similar. We'd just need to remember to modify the kickstart to not format all drives (or to use libvirt to remove the drive once we've loaded the ks.cfg/updates.img/etc.)
Either way would work equally well, but to test all of the stuff in the installation test plan we'll eventually need to implement both methods *and* the http/ftp methods.
I think the local-disk methods are probably simpler to start out with, though.
Anyway: thanks for all your hard work, Liam!
Thanks Will, your guide is very helpful, we need to make both local ks and network ks work in the future.I will add this to the script if I can do it. :)
Regards, Liam
autoqa-devel@lists.fedorahosted.org