>
> Hongqing can correct me of course. The challenge is to find a simple
> method to avoid having test clients always re-downloading test ISO
> images (boot.iso isn't so bad, but constantly downloading the
> DVD.iso
> stinks). More specifically, it seemed to me that having our install
> testsuite saturate the download servers was a bad idea.
>
> The ideas that came to mind where to either support a multi-stage
> event
> watcher where stage#1 would download the ISO images to the autoqa
> server, and then stage#2 would expose the downloaded images to test
> clients (either via http/ftp/nfs). Another thought was to use a
> proxy
> on the autoqa server to accomplish the same thing behind the scenes.
> I'm sure we can come up with some additional ideas to either reduce
> ISO
> downloads outside the autoqa network.
>
> Thanks,
> James
I have modified the watchers/iso/watcher.py, James wrote before, to
monitor and download the images
from
http://dl.fp.org/alt/stage to directory
/var/cache/autoqa/install-isos, this will not trigger
the event, and I also created watchers/iso/watcher.py to monitor
/var/cache/autoqa/install-isos,
which will trigger the event.
I have discussed this with Kamil, we both do not have any experience
to use squid, Kamil would like
to explore it, I will also test it on my machine.
And if we solved the downloading issue, I would like to add Ticket
#186 Automate media kit sanity tests
into AutoQA 0.7.0.
Hongqing
My question is different. Do we need to use those DVD images multiple times? Because if we
test every image just *once* (we run mediakit_sanity test and that's all) there's
no reason to complicate it (at the moment), the mediakit_sanity test can download the ISO.
The bandwidth si the same, regardless whether it's downloaded by watcher or by a
test.