Re: [AutoQA] #244: Find the best way how to use fas.conf
#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 jlaska):
Replying to [ticket:244 kparal]:
1. fas.conf on every client - tedious and hard to maintain
Not terrible really, and we are doing this already with irb.conf. So it's
not perfect, but not that bad. And given the frequency that we provision
test clients, it's not so tedious. I think we just need to decide whether
the configuration information being recorded is test-specific ... or
generally useful for all/other tests. I think it's the later, which means
a per-test fas.conf is kind of silly. Since we now have /etc/autoqa/ I
think we can move this from the test into that system-wide configuration
directory.
2. fas.conf on some clients - we can use autotest labels to mark
only a
few clients as containing fas.conf; tests using fas.conf would then
require these clients; fas.conf checksum may be compared to decide whether
client's fas.conf is up-to-date
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.
3. 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.
4. ask some service to send a comment - it may run this on the
server,
but it's another layer, need to solve authentication and so on
This is probably a temporary hack until we have better solution based on
ResultDB, so some simple solution is preferred.
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.
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/244#comment:1>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project