As we were discussing in the latest threads, we will probably need some results database server in the future so we can then access it by different front-ends or RPC calls. I tried to think about the whole concept of AutoQA and create a picture that would correspond to my ideas. Have a look at it at: http://kparal.fedorapeople.org/misc/autoqa/architecture_idea.png
What are your opinions on this topic, which things need to be discussed, what do you disagree with? I believe we should discuss these issues properly so won't implement something that would need to be re-worked soon after.
I see the database server as the biggest and nearest challenge now, because the current irb site can easily display installer tests results, but you can hardly use it for displaying package update results (rpmlint, rpmguard). When we want to do something more with it than just sending it to the mailing list, we will need the results server, I reckon.
Will, is it possible to separate the current irb database from the irb front-end itself, so we could use it as a basis for the results database server? And then connect the current front-end to it, as well as other front-ends?
Thanks for responses, Kamil