On 06/13/2013 03:43 PM, Raymond Mancy wrote:
> 1. If the recipe is dirty, add the first candidate system that
isn't
> already in the "off limits" set to the "off limits" set.
We would need to keep counters on the 'off limits' systems, as they
could be 'off limits'.
> 2. If the recipe is clean, schedule it on the first candidate system
> that isn't already in the "off limits" set
If the recipe is clean we would also need to check if it had previously
put any systems, in the 'off limits' set. If it did, it would reduce the
counter by 1, if the counter was zero it could be removed from the 'off limits'
set.
The "off limits" set would start empty on every scheduling pass, so no
need for any counters - if a system ends up in the off limits set, it's
effectively "tentatively scheduled" for the first dirty recipe that was
waiting for it.
Cheers,
Nick.
--
Nick Coghlan
Red Hat Infrastructure Engineering & Development, Brisbane
Testing Solutions Team Lead
Beaker Development Lead (
http://beaker-project.org/)