#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 jlaska):
Replying to [comment:5 kparal]:
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.
Oh that's right we do modify autoqa.conf and send it to the client. Thanks.
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.
I'm just not sure whether the '-h' tar option was omitted intentionally by upstream autotest, that'd be my only hesitation with changing that core autotest behavior.
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 :)
repoinfo.conf, and irb.conf could benefit from this (although irb is kind of an unmaintained feature).
From an rpm packaging standpoint, I (and rpmlint) hate having config files live outside /etc. Additionally, I wonder if your second solution might be more future-proof since you're not replacing/duplicating the existing autotest tar() method, but simply calling it. Of course, either approach will do nicely ... and we'll adjust as needed.