On Sat, 27 Jun 2009 01:10:19 -0400 (EDT)
CAI Qian <qcai(a)redhat.com> wrote:
----- Bill Peck <bpeck(a)redhat.com> 写道:
>
> Just sending this to the list to get feedback. If you remember
> from previous emails a recipe = a single system. a RecipeSet
> contains mutliple recipes that need to be scheduled at the same
> time. Also, we only want multi-host jobs to be scheduled on the
> same lab controller.
>
Why? I can think of scenarios that to pick up machines from different
lab controllers are still valid,
- some systems are only in one lab controller like s390(x), but we
also can have a flexibility to pick up other machines in some other
labs.
Agreed. We've been bitten a couple of times when a special workflow
required X machines to run successfully, but the lab didn't have
enough. On the other hand, we needed to use the lab because it had
s390x.
So while attempting to schedule everything in one lab is a Good Thing,
I'd like to have the flexibility to override this for special cases.
/David
--
===================================================================
David Kovalsky, RHCE dkovalsk(a)redhat.com
Senior Quality Engineer - BaseOS QE Daemons Lead
Red Hat Czech s.r.o. Brno, Czech Republic
tel: +420 532 294 223
mobile: +420 777 707 369
IRC: #0day, #brno, #errata, #qa, #rhlp, #tps, #urt
===================================================================