[drmaa-wg] Mandatory support for drmaa_start_time

[Peter Troeger]

The attribute is not directly available at submission time. However,  
meanwhile the condor-users mailing list was able to provide an  
acceptable solution to my problem.
Condor supports a boolean ClassAd (periodic_release), which is  
checked every 60 seconds and frees a job from hold state if the  
expression evaluates to true. I can check the current time again a  
constant in this expression, so it is possible to support deferred  
startup.
The start_time attribute was missed so far in the implementation, so  
Nick had no chance to see this.

Sorry for the wrong alert ;-) The other mails are still open.

Regards,
Peter.


Am 17.10.2005 um 22:47 schrieb Rajic, Hrabri:

> Hi Peter,
>
> I believe we would need to live with this var as mandatory for the  
> time
> being - till ver 2 or so.
> Is the attribute simply missing or clashing with the Condor job
> submission philosophy.
> The best is to document this well in the experience doc and open a
> tracker.
>
> I am surprised that Nick hadn't alerted us about this problem - we  
> need
> to revisit his comments.  Regardless, it would be unfair to blame him.
>
> Regards
>
>         Hrabri
>
>
>
>> -----Original Message-----
>> From: owner-drmaa-wg at ggf.org [mailto:owner-drmaa-wg at ggf.org] On  
>> Behalf
>>
> Of
>
>> Peter Troeger
>> Sent: Monday, October 17, 2005 12:44 PM
>> To: DRMAA Working Group
>> Subject: [drmaa-wg] Mandatory support for drmaa_start_time
>>
>> Hi,
>>
>> the mandatory drmaa_start_time attribute for job templates could
>> become a problem for the Condor DRMAA implementation. There is no
>> direct support for such a concept in Condor, and the Condor guys
>> acknowledged this. I could end up with some strange workaround
>> (wrapper job for waiting, persistent DRMAA jobs with timed startup by
>> the library), but  we might also consider to make drmaa_start_time an
>> optional attribute. I need suggestions ...
>>
>> Regards,
>> Peter.
>>
>
>