2010-06-09 - AutoQA reprioritization discussion

[James Laska]

# AutoQA priority discussion
# Date: 2010-06-09
# Time: 14:00 UTC (10:00 EDT, 15:00 CEST)
# Attendees: kparal, jskladan, wwoods, jlaska

Several folks working toward the Package Update Acceptance test plan met
and discussed re-prioritizing outstanding tasks.  Below are the notes
from that meeting.

== Agenda ==
Mindmap:
  http://kparal.fedorapeople.org/autoqa/tasks.png
  
== Conclusions ==
* Focus on infrastructure/architecture parts first
* testing autotest-server instance important, publicly available
instance not so important
* Current high priority tasks:
  * post-bodhi-hook
    * feature-complete, needs to be tested and merged into master
  * resultdb
  * quick version of virt support
  * getting public accessible machines
    * public autotest blocked on packaging gwt + deps (java booooo)
* Lower priority tasks
  * Package sanity tests 
  * Package update tests
  * Initscripts
  * message bus (aka "pony")
  * full virt support (destructive tests)
  * depcheck (permissive vs enforcing)
  * unit testing of koji/bodhi libraries
    * requires test data stored in koji & bodhi

== TODO ==
* [jlaska] find a machine where resultdb may run (it can be VM, publicly
accessible preferred)
* [jlaska] set up testing instance of autotest-server
* [kparal] implement *quick* virtualization support
* [jskladan, wwoods helping] bodhi hook needs to be tested
* [jskladan, kparal, wwoods] continue implementing and testing resultdb

== Dependencies ==

-> testing instance of autotest-server -> bodhi hook testing -> add
support for our tests

-> testing instance of autotest-server -> quick virtualization support

-> (publicly accessible) machine -> resultdb efforts

== Next Meeting ==
* 2010-06-25 - Check-in on autoqa-devel@ for status on action items

[James Laska]

On Wed, 2010-06-09 at 11:18 -0400, James Laska wrote:
>  == TODO ==
>  * [jlaska] find a machine where resultdb may run (it can be VM,
>  publicly
>  accessible preferred)
>  * [jlaska] set up testing instance of autotest-server 
The fedora infrastructure team rocks!  We now have our 6 bare metal
(virt-capable) systems deployed and just about ready for use.  In
addition, the existing QA1 virt guest is being renamed to autoqa.  

Long story short, the configuration is:
     1. http://autoqa.fedoraproject.org -> routes to
        autoqa.phx2.fedoraproject.org a EL5 virt guest 
     2. qa01.c.fedoraproject.org through qa06.c.fedoraproject.org are
        bare metal test systems intended to do the testing

Again, kudos to mmcgrath and smooge for setting this up for us.  Until
autoqa and autotest are packaged for Fedora, we will be responsible for
managing the software and configuration of these systems. 

We are waiting on a networking change to handle step#1 above.  I hope to
have more updates soon.

>  * [jskladan, wwoods helping] bodhi hook needs to be tested 
In case folks need to setup autoqa and autotest to try out the
post-bodhi-update hook ...

     1. I built an autoqa-0.3.5-pre1 package which is a merge of the
        wwoods and master git branches for testing
     2. I created yum repos to assist with installing/updating autoqa
        and autotest until it is available in Fedora
     3. I updated the installation+configuration instructions [1] [2]

Thanks,
James

[1] https://fedoraproject.org/wiki/Install_and_configure_autotest
[2] https://fedoraproject.org/wiki/Install_and_configure_AutoQA