----- Original Message -----
From: "Kamil Paral" <kparal(a)redhat.com>
To: "AutoQA development" <autoqa-devel(a)lists.fedorahosted.org>
Sent: Monday, December 19, 2011 5:16:08 PM
Subject: Re: production server environment
> Greetings,
>
> May I get some information about our production server, what system
> is it, RHEL or Fedora?
RHEL 6
> Which account is used to run all the tests, 'root', 'autotest' or
> sth
> else?
autotest
> what about the partition space, we should decide where should we
> put
> all the ISOs downloaded
My current idea is that the clients will download the ISO directly
from dl.fp.o. In devel environment we will have a caching proxy
deployed (I'll submit patch today) so only one download will be
required and the test (or other tests) can use that file countless
times. In production environment we will deploy proxy only if the
downloads create too much load at the Fedora servers.
So it that OK to store the ISO at /var/cache/autoqa/isos in production
environment?
> and
> the ISO build by compose_tree. Thanks.
That's currently unsolved, we have no mechanisms ATM to re-use
generated files. But I don't think we need that. The compose_tree
test can report whether the compose succeeded or failed. And the
rats_install test can use ISO images generated by releng (after F17
is branched).
previously the rats_install boot from pxeboot,I just changed rats_install to boot from
local vmlinuz and initrd.img.
the 'virt-install' with option '--boot' cannot accept local ksfile with
'--initrd-inject', so we need create virt disk
to store the ks file and pass by interacting with the terminal.
Will the releng build the pxeboot images for F17? If so, that will save a lot of time.
Hongqing