#244: Find the best way how to use fas.conf --------------------+------------------------------------------------------- Reporter: kparal | Owner: Type: task | Status: new Priority: major | Milestone: 0.4.4 Component: core | Resolution: Keywords: | --------------------+------------------------------------------------------- Comment (by kparal):
Replying to [comment:1 jlaska]:
ad 2) I don't know the benefits of this are over the #1. My sense is this
adds extra complication to #1. But I might be missing some important details.
Well, the idea is that we don't have to maintain fas.conf on so many clients. Also if we add a new autotest client and forget to fill-in its fas.conf, some test requiring fas.conf may be scheduled on that client and then silently do nothing (not report anything). If we use autotest labels, this is more unlikely to happen.
- copy fas.conf from the server, but don't store it in the results
dir - ideal, if autotest server supports this, need some investigation
Hmm, I don't know.
Autotest server tarballs the whole test and then transfers it onto the client. So if we have a symlink in the test directory pointing at server's fas.conf, and if we manage autotest to archive the target file and not the symlink itself, it would work quite fine. But still, I looked at it very briefly.
I'd vote for #1 for simplicity. I have to play the role of "puppet"
already, so I don't mind including deploying an updated /etc/autoqa/fas.conf configuration to all test clients.
Originally I supposed we should do more complex solution, but as you say -- it's not really so much work after all, and it's just a temporary hack. If we don't find a better solution easily, I'd vote for #1 also.