#254: Transfer autoqa library to autotest clients
-------------------------+--------------------------------------------------
Reporter: kparal | Owner: kparal
Type: enhancement | Status: assigned
Priority: minor | Milestone: 0.7.0
Component: autotest | Resolution:
Keywords: |
-------------------------+--------------------------------------------------
Comment (by kparal):
Replying to [comment:12 tflink]:
The only question I have is why go through the conf file creation
process instead of running 'yum deplist autoqa' on the client in order
to
determine dependencies? Yeah, it would find a few things that aren't
really needed (httpd, mod_wsgi etc.) but we wouldn't have an extra
configuration file and wouldn't need to be doing such hacking in the
makefile.
You would have to first add correct yum repositories to the client (until
AutoQA is in Fedora). The client wouldn't be as maintenance-free (one more
step needed).
Also, I use this approach for installing openssh-clients and rsync, the
dependencies of autotest. Autotest currently supposes you do that manually
when creating the client. Using my approach we have even less work.
Currently it really boils down just to setting up the ssh pubkey
server->client authentication.
I can abolish populating client-deps.conf file in the Makefile. But
instead I'll have to move most of the code into site_autotest.py (add
correct yum repos on the client, find out dependencies, filter them out,
install them, also install autotest dependencies). I think it's more or
less the same, the benefit of client-deps.conf is that it's not as deep
buried as with site_autotest.py. Note: we don't have to filter out the
dependencies for httpd etc, it's just a minor optional optimization until
we split AutoQA into several packages.
I'm also not a huge fan of running unattended 'yum -y' commands but I
can't think of another way to make this work while staying within autotest
unless we just errored out in the case of missing dependencies. In theory,
the system should have those deps installed so it shouldn't be Either
way, I don't have a better idea so it's a moot point.
We do that (yum -y) for all our tests initialization. I'd like to see a
better approach, but I don't have it.
--
Ticket URL: <
https://fedorahosted.org/autoqa/ticket/254#comment:13>
AutoQA <
http://autoqa.fedorahosted.org>
Automated QA project