Hi
the requirement is lost between gatekeeper and PBS.
CREAM has provisions for passing the requirements on from the
gatekeeper to the LRMS. So next week in Istanbul, make sure to let
the developers know how anxiously you are looking forward to CREAM ...
JT
On Sep 16, 2008, at 19:51 , Christos Triantafyllidis wrote:
> Hi all,
>
> On Sep 16, 2008, at 4:23 PM, Murri Riccardo wrote:
>
>> The downside is that this is "too much" effective: since all jobs
>> come
>> from the WMS/RB with no time requirements, they inherit the default
>> setting of the queue. With 72-hour queues as in YAIM default,
>> if you schedule a downtime for Monday morning, no new jobs will be
>> started since Friday... (We have a separate queue for "ops" with
>> a 1-hour time limit, which ensures SAM jobs can run until
>> the start of the downtime.)
>>
>
> I think this is what most (not all?) sites do but in my point of
> view the problem is that actually no information comes from WMS (i
> don't think there is any reason to talk about RBs) for time
> requirements.
> Even if users say in their requirements that they need a CPU for 2
> hours, MAUI and PBS will do calculations as if it was needed for the
> default setting of the queue (probably 72hours). I think that we
> could achieve better services (allowing quick jobs to run with
> priority etc) if the time requirement from user's JDL was passed to
> torque's requirements.
>
> The 72-hours can be the default requirement at each UI in order to
> keep the same environment for users that don't use this requirement.
>
> Actually i'm not sure if this requirement is lost between WMS and
> gatekeeper or between gatekeeper and PBS....
>
>
> Regards,
> Christos
>
|