----- "James Laska" <jlaska(a)redhat.com> wrote:
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
Wow, great! This is going to be the testing instance or the stable instance?
2.
qa01.c.fedoraproject.org through
qa06.c.fedoraproject.org
are
bare metal test systems intended to do the testing
Just perfect.
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
Thanks, that will surely help. You might be also interested that autotest
0.12.0 is already out.