> It's like the whole discussion of getting CPU and Wall clock limit
requests from users - there is no reason it won't work right now [0]
(takes about 4 > lines of code to implement). After which we'd be able
to schedule things properly, and the site efficiencies would increase,
etc. But it takes a
> change on the WMS (which won't pass through options it's not been
told about), and in CREAM (to pass them to the batch system). So that's
never > going to happen...
Another thing dragged since EGEEII I remember when I was asked to test
the functionality of the WMS to pass batch requirements to the CE and
the piece of code wasn't there..... I did write a 10 liner to prove the
message could be passed but that wasn't the major problem. Major problem
was that developers refused to write anything claiming it was a "sys
admin task"; sys admin didn't think it was a good idea to develop each a
different script with inherently a different behaviour; the ball was
then passed to the WN working group to come up with a set of minimal
default parameters that should be configured; they probably produced a
document that was shown around and forgotten because the WMS back then
was unstable, the transition from the RB incomplete and there were
probably bigger problems to solve.
cheers
alessandra
|