Marian Csontos wrote:
Hi Bill,
Is LC going to provide a synchronization among multiple tasks as RHTS
does?
it could, but I don't have any store (DB) in the lab controller right
now.
I would like to implement this as a kind of variables in Harness:
- variables could be either local (stored by harness) or server side
(managed by external entity, with the assistance of backends).
- local variables could be persistent - e.g. would survive a reboot.
- (task|recipe|recipe-set)-specific variables, by using id in its name.
- server side var's would be handled by backend - again, backend could
decide which variables it handles by simple pattern matching.
I would like it to be
done in the harness so that when multi-host tests
are run outside of the beaker scheduler they would work. The XML would
still have to say who is in what role.
<task avg_time="7200" id="233"
name="/distribution/kernelinstall"
result="None" role="SERVERS" status="Running">
<roles>
<role value="CLIENTS">
<system value="dell-pesc430-02.domain.com"/>
</role>
<role value="SERVERS">
<system value="hp-lp1.domain.com"/>
</role>
</roles>
How would the harness running on
dell-pesc430-02.rhts.eng.bos.redhat.com
know it needed to talk to the harness running on
hp-lp1.rhts.eng.bos.redhat.com?
Who is going to be the primary sync master? Whoever has the lowest ip
address?
Does seem easy if I just implement a store on the lab controller and let
them use it as the sync master..
Comments welcome,
-- Marian