From: "Peter Troeger" To: "Andreas Haas" Cc: "Ruben Santiago Montero" , "Hrabri Rajic" , =?iso-8859-1?Q?Ignacio_Mart=EDn_Llorente?= , "Roger Brobst" , "Daniel Templeton" References: <200603211212.41381.rubensm@dacya.ucm.es> <44207279.4090500@hpi.uni-potsdam.de> <200603231153.39610.rubensm@dacya.ucm.es> Subject: Re: GridWay Experience Report Date: Thu, 23 Mar 2006 10:33:19 -0500 Message-ID: <4422BFBF.1000800@hpi.uni-potsdam.de> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_00B3_01C6564A.98565080" X-Mailer: Microsoft Office Outlook, Build 11.0.5510 Thread-Index: AcZOjxz4c6sJabBCTiSfFifkWcbX0w== In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Apparently-To: hrabri@sbcglobal.net via 68.142.199.172; Thu, 23 Mar 2006 07:33:20 -0800 X-Originating-IP: [141.89.225.123] X-Header-Overseas: Mail.from.Overseas.source.mail3.hpi.uni-potsdam.de x-fsavag4mse-ts: ce3a50e13d5a79e X-OriginalArrivalTime: 23 Mar 2006 15:33:19.0057 (UTC) FILETIME=[1C68FC10:01C64E8F] X-Accept-Language: de-DE, de, en-us, en X-Enigmail-Version: 0.93.0.0 This is a multi-part message in MIME format. ------=_NextPart_000_00B3_01C6564A.98565080 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit >>>- State of jobs after suspension: I loved to read this, since I had >>>exactly the same problem in the Condor DRMAA implementation. I ended up >>>with marking such jobs as "was suspended before", in order to give the >>>right active state afterwards. If we want to change the spec according >>>to this, we have a post 1.0 issue. >> >>Great!. I think I can just make the same thing in GridWay DRMAA. > > > Hm ... I doubt this is a good idea. Job suspension is different > from triggering job rescheduling. If implementing job suspension > is a severe problem for DRM vendors, I believe that should be rather > an argument for not making it mandatory rather than deviating > from the standard. Even though we are running out of time for spec changes, this should be a topic for the next DRMAA phone conference. Hrabri, could you put this on the agenda ? Regards, Peter. ------=_NextPart_000_00B3_01C6564A.98565080 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: GridWay Experience Report

>>>- State of jobs after suspension: I loved = to read this, since I had
>>>exactly the same problem in the Condor = DRMAA implementation. I ended up
>>>with marking such jobs as "was = suspended before", in order to give the
>>>right active state afterwards. If we want = to change the spec according
>>>to this, we have a post 1.0 issue.
>>
>>Great!. I think I can just make the same = thing in GridWay DRMAA.
>
>
> Hm ... I doubt this is a good idea. Job = suspension is different
> from triggering job rescheduling. If = implementing job suspension
> is a severe problem for DRM vendors, I believe = that should be rather
> an argument for not making it mandatory rather = than deviating
> from the standard.

Even though we are running out of time for spec = changes, this should be
a topic for the next DRMAA phone conference. Hrabri, = could you put this
on the agenda ?

Regards,
Peter.

------=_NextPart_000_00B3_01C6564A.98565080--