LHC Computer Grid - Rollout
> [mailto:[log in to unmask]] On Behalf Of Charles Loomis
said:
> > 1) Keep the current syntax, allow matching against multiple
> subclusters,
> > and pass the subcluster name to the batch system.
>
> This is not a solution to the problem.
It's a solution to part of the problem, i.e. that currently jobs may
avoid sites even if only 1 WN out of 500 doesn't match the requirement,
because you have to publish the most restrictive limit.
> I would instead opt for a hybrid approach of 2) and 3).
> Allow people to
> define parameters like in 3) and have whatever processes the
> final JDL
> combine those with any explicit requirements to arrive at the full
> expression. Only those limits given separately would be
> passed to the local batch system.
Yes, that doesn't sound too bad - but in itself it wouldn't solve the
above problem, so you might still want to think about doing subclusters
properly, or else changing the glue schema to go back to max/min values.
Stephen
|