#244: Find the best way how to use fas.conf --------------------+------------------------------------------------------- Reporter: kparal | Owner: kparal Type: task | Status: assigned Priority: major | Milestone: 0.4.4 Component: core | Resolution: Keywords: | --------------------+------------------------------------------------------- Comment (by kparal):
Replying to [comment:4 jlaska]:
Nice detective work! I can't think of any reasons why we might need
different config files on different client systems, can you?
Certainly not for fas.conf.
Meaning, maybe our F13 client systems have a slightly different config
from our F14 systems etc...
autoqa.conf is currently only configured on the server and transferred to client hosts by writing it out into test's control file. That means we don't really have any configuration changes for F13/F14/etc.
However, this approach is not really usable for autoqa.conf, because we modify autoqa.conf on the fly before writing it out into the control file. It is really meant as a quick workaround for transferring fas.conf (static and shared config file) into the test dir on the client. Because fas.conf should be temporary, this workaround should also be temporary.
With either solution, is the fas.conf available when viewing the test
results?
No, at least I couldn't find it in the results.
Or is the fas.conf only copied into the base directory for the test ...
not the results?
That should be exactly the case.
Assuming it's not visible when viewing test results from the web-ui, I
like your suggestion #2.
Do you mean the second solution in comment 3? I personally think the first solution from comment 3 is better, because it allows us to add/remove/rename symlinks to config files without deploying patched autoqa version on the production machine.
Should we extend that support further to add an additional method that
copies all autoqa config files from the autotest server to the test client before running a test? That would be a real nice improvement for the AutoQA sysadmin.
We don't have any more config files apart from fas.conf and autoqa.conf (that is transferred other way), or do we (necessary for the client)? I don't know about them :)
If we need to copy more such files and do it non-temporarily, I would rather ask autotest developers whether they could add such feature for us.
Btw, the patch for solution 1 from comment 3 is in autoqa-devel now:[[BR]] https://fedorahosted.org/pipermail/autoqa-devel/2010-November/001368.html