== Project Sponsor ==
'''Name''': James Laska
'''Fedora Account Name''': jlaska
'''Group''': Fedora QA Admin Group
'''Infrastructure Sponsor''': Mike McGrath and Jesse Keating
== Secondary Contact info ==
'''Name''': Will Woods
'''Fedora Account Name''': wwoods
== Project Info ==
'''Project Name''': AutoQA
'''Target Audience''': Consumers of Fedora rawhide interested in automated daily test result presentation
'''Expiration/Delivery Date (required)''': 2009-09-10
'''Description/Summary''': Test hardware for AutoQA project
'''Project plan (Detailed)''': See https://fedorahosted.org/autoqa/milestone/israwhidebroken.com
'''Goals''': The first major milestone is to provide public review of daily rawhide test results intended to satisfy the question: ''Is rawhide broken?'' To satisfy this, we are using an autotest server along with bare metal test client systems.
== Specific resources needed ==
autotest, autoqa, Django
Clients - Bare metal hardware intended to run tests scheduled by autotest Server.
== Additional Info (Optional) ==
qa1 (the server portion of this) is now up and running. You can get to it by sshing to bastion.fedoraproject.org then sshing to "qa1"
the recommended (optional) ssh config would be:
ProxyCommand ssh -A bastion.fedoraproject.org nc qa1 22
mmcgrath: is there a recommended procedure for re-provisioning qa1 to a RHEL5 system?
I'd recommend the IBM x3550. We have a bunch already is all so it'd be easy to manage.
1) rail kit
2) remote management (with the IBM's it'd be an RSA-II card)
3) 24x7 on site warranty for at least 3 years if you plan on using them for 3 years :)
1) dual power supply
I think this is all done. Feel free to re-open if there's further things to do...
to comment on this ticket.