Dear colleagues,
please let us know what other kinds of job execution requirements for the
batch system should be expressible in the JDL and subsequently forwarded
to the batch system.
---------- Forwarded message ----------
Date: Thu, 8 Sep 2005 11:16:41 +0200 (CEST)
From: Massimo Sgaravatto - INFN Padova <[log in to unmask]>
To: Maarten LITMAATH <[log in to unmask]>,
David Smith <[log in to unmask]>,
"Charles (Cal) Loomis" <[log in to unmask]>
Cc: Francesco Prelz <[log in to unmask]>,
Giuseppe Fiorentino <[log in to unmask]>
Subject: Forward requirements to local batch system
Dear all
I have just been given the task to try to better undestand the
requirement:
"Forward requirements to local batch system"
set in the JRA1 workplan (looks like there were some misunderstandings
concerning who had to take care about that).
As far as I am told, the issue was raised in particular by Cal. I think
that also David and Maarten are the right candidates to start the
discussion with.
So, could you please elaborate such requirement ?
Do you mean that the various constraints expressed in the "JDL
requirement" expression should be translated in the proper batch system
directive and used when submitting the job, or were you thinking about
something different ?
How about different batch systems supporting a different set of
attributes ?
Should all the supported (by the used batch system) attributes be
translated, or only a minimum common (supported by all the supported
batch system) set of attributes should be considered ?
How about translating requirement expressions specified on multiple CE
attributes, as the following example (taken from a real atlas production
job):
Requirements = other.GlueCEPolicyMaxCPUTime >= ( 14000000 / 60 ) /
other.GlueHostBenchmarkSI00 )
?
Let's start the discussion :-)
Cheers, Massimo
|