# AutoQA ResultsDB Discussion
# Date: 2010-04-16
# Time: 14:00 UTC (10:00 EDT, 15:00 CET)
# Attendees: kparal, jskladan, wwoods, jlaska
= Previous action items =
* [jskladan+kparal] Create updated DB schema according to the discussion
**
https://fedoraproject.org/wiki/AutoQA_resultsdb_schema#Result
-> rename 'Test' table to 'TestCase'
-> type of the test is not stored in the DB, add it somewhere, or use
tags? We must have the mandatory keyvals stored in the database (cached?
from wiki) to have fast access to the keyval pairs
->-> we don't have to keep this data inside DB if we are just happy with
that result not displaying in the frontend; DB itself doesn't care about
invalid data
* [wwoods?] Study MediaWiki RPC mechanism
* [kparal] Define default (common) key-values for basic test classes
(installation tests, repo tests, package tests)
**
https://fedoraproject.org/wiki/AutoQA_resultsdb_schema#Default_key-values...
-> install key/val pairs exist in .treeinfo
(
http://download.fedoraproject.org/pub/fedora/linux/development/13/i386/os...)
* [jskladan] Communicate with Autotest developers how to get Job ID in
autotest client
**
https://fedorahosted.org/pipermail/autoqa-devel/2010-March/000326.html
* [jlaska] Try to set up a qpid instance and send some test data through
it (from provider to listener)
(jkeating (Oxf13) is a good person to talk to about this!)UI
**
https://fedorahosted.org/autoqa/ticket/132#comment:1
= ResultsDB API =
* 'Input' interface
<
https://fedoraproject.org/wiki/AutoQA_resultsdb_API>
* Is this satisfactory? Do we any other methods for pushing data
into
the ResultsDB
* Tagging - kparal and I discussed, if there could be any reasonable
tag, which one would like to use _from inside_ the testrun. (All the
tags I could think of were either about Tests, not Testruns, or they'd
make sense to be applied after a real person went through the results.)
* 'Output' interface
* Fedora Message Bus (FMB)
* What's the state?
-> In progress, Bodhi will may soon talk over the bus,
* Will we set up some testing instance?
-> There should be running Qpid instance somewhere
-> talk to infrastructure guys about current state and if/how can
we use it
* My understanding of using the FMB is, that we'll just post new
'events' to the FMB, and whoever wants to will consume that
information,
is that right? If so, will the consumers be responsible for storing the
data, for their further use, or will they be able to query ResultsDB?
-> Mostly we'll send events, that will inform users that 'new data
is in the resultsDB'
* Querying ResultsDB
* What is the best approach
1) Set of predefined functions
2) Possibility to execute SQL queries
-> not secure, if needed we should add API
3) Combination of both
* Predefined functions:
* What functions will we provide at the beginning?
-> we'll create a set of functions _we_ need at the beginning
(we'll find out, while creating the front-end)
* Will we add more if somebody asks?
* How to tell, if the demand is valid?
= Open Questions =
Q. Whether or not front-ends will be message bus consumers, or query the
resultsdb directly?
A.
Q. Are we at the point where we can add a built-in unit test suite for
resultsdb?
A. Jskladan noted there is a ticket for this already (see
https://fedorahosted.org/autoqa/ticket/144)
Q. How to proceed with prototyping?
A. Jskladan plans to experiment with a python xmlrpc to get started.
Wwoods recommended moving to TurboGears when the time is right.
Q. Next steps?
A. Prototype the API ... use this to get data in and out of resultsdb.
Wwoods noted that it can be helpful to think of a specific use case
first (installation, package acceptance).
Q. What front-end should we focus on first.
A. Wwoods+jlaska felt the current draft package acceptance test plan
(
https://fedoraproject.org/wiki/User:Kparal/Proposal:Package_update_accept...)
was best to start with.
Q. What to do with 'Is rawhide broken' test plan?
A. One suggestion was to rename it to 'Is branched broken'.
= Action Items =
* [all] *Keep It Simple*
* [ ] - talk to Fedora Infrastructure to figure out current msgbus state
and how to use it
* [ ] - ask lmacken || toshio whether TurboGears2 is still prefered
Fedora solution