On Wed, 2011-08-10 at 08:00 -0600, Tim Flink wrote:
On Wed, 10 Aug 2011 08:03:06 -0400 (EDT) Kamil Paral kparal@redhat.com wrote:
Let's do an email discussion this time. I don't see any topic we need to discuss at real-time and I think emails are more convenient in this case.
Either way - I'm flexible.
My proposals are holdovers from 0.6.0 that didn't get finished:
- #347 - Test results are sometimes linked incorrectly in bodhi
Definitely, I'd like to see this ticket at 0.7.
Especially since it got re-reported yesterday.
- #355 - Determine Use Cases for Functional Self Tests
- #353 - Create AutoQA Functional Self Test Cases
This is #352. Which one do you have on mind?
Whoops, my bad. I was trying to keep the number of tickets down since I don't think that 355, 353 and 352 are going to be practical in 2-3 weeks.
To be honest, I'm all for 355 and pull in 353 and/or 352 as time permits.
I believe the above-mentioned tickets will take time. We can put it into the milestone, or we don't have to, it doesn't matter, as long as we know we want to work on that continuously.
Yeah, let's just pull in 355 for 0.7.0.
Any other proposals?
I was contacted by hongqing. He wants to provide a new test mediakit_sanity into 0.7, which will check ISO images of Branched composes. He needs to download those images. Now he uses a two stages method, first downloading the iso from remote to a local dir, then another watcher monitoring the dir. He says implementing this ticket would reduce the complexity.
#350 Add support for using file proxy https://fedorahosted.org/autoqa/ticket/350
I'm willing to work on this ticket. But as I've written this down, I realized I don't know the reason why hongqing needs to cache those ISOs. We need to cache those files only if: a) we run multiple tests on it b) we run the same test several times of the same ISO
Can you clarify, hongqing? Thanks.
Yeah, I'd like to get more information on this one. I'm unclear on why a file proxy would be a good solution for caching ISOs but I also don't pretend to understand everything that is being done in the ISO tests.
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