[DRMAA-WG] Meeting Minutes - Conference call - Apr 27th - 19:00 UTC

Mariusz Mamoński mamonski at man.poznan.pl
Fri Apr 29 07:39:20 CDT 2011


2011/4/29 Daniel Gruber <dgruber at univa.com>:
>
> Am 29.04.2011 um 14:14 schrieb Peter Tröger:
>
> There are currently two problems from Grid Engine:
> - There seems no way for getting the desired NOW behavior (at least in this
> section the *optional* NOW keyword is not defined)
>   for an GE specific enhancement, without breaking compatibility
> -  In GE there is no currently no sliding windows support for the
> SET/SET/SET in case of duration is shorter than endTime-startTime
>    (GE DRMAA implementation have then a similar problem then the other DRM
> which do not support NOW as startTime)
> Following suggestions for this section (5.6.2):
> - Add the *optional* "NOW" constant -> if an implementation does not
>   support it, it is treated like UNSET (InvalidAttributeException)
>
> My understanding of the agreed result was a little but more radical. NOW is
> not supported by all DRM systems, and it is not as crucial as slots ;-), so
> we can just leave it out. Applications then will start to build their own
> "NOW" workarounds (current local time plus ...  hmmm .... 10s), which is
> completely fine in this specific case.
>
> We should really take an optional NOW constant really into account.
> Application could do their own workaround but
> *if* a DRM has build-in support for this, it is really hard to offer this
> functionality. It just prevents that this can be optionally
> implemented. What do we loose with an new optional "NOW" constant??

for me it is ok, as far as we can introspect if NOW is supported by
the given DRM system.
>
> - If startTime, endTime and duration is set and duration is shorter than
> endTime-startTime, the
>   sliding windows approach (take "the earliest point in time") could made
> optional.
>   That means: take startTime and duration or *optionally* search the
> earliest point in
>    time.
>
> I don't understand this. What is the alternative for searching the earliest
> feasible startTime ? Ignoring the duration value ? Or ignoring end time ?
>
> One of them, for me it really does not matter which is going to be ignored,
> it should just be defined.
> Maybe the best solution would be ignore "end time" when start "time +
> duration" <= "end time".
> Cheers,
> Daniel

the same problem. In my initial proposal:

http://fury.man.poznan.pl/~mmamonski/wiki/index.php/DRMAAv2/Advance_Reservation

"duration
Reservation duration. If reservation duration is shorter than endTime
- startTime the earliest reservation (matching the requirements, e.g.:
slotsCount) will be created. If this attribute is omitted then the
duration is assumed to be equal to endTime - startTime. Optional
attribute."


i wanted the "duration" to be optional. Now i remember why ;-) This
was an easy way to determine if the DRM system support searching
earliest feasible reservation in the given time window. I.E. if the
system support the Duration attribute it means that it also offer the
aforementioned functionality.

>
> Best regards,
> Peter.
>
>
>
>
> I know we discussed it more than once, but having these options would make
> it
> much easier to get a compatible implementation.
> Cheers,
> Daniel
>
>
> Am 27.04.2011 um 23:46 schrieb Peter Tröger:
>
> Line 751 - Reservation without time frame
> - Makes no sense, since it might be way too short for the user
> -> raise invalid argument exception on UNSET/UNSET/UNSET
> - add rationale why startTime=UNSET is not equal to startTime=NOW
>   - handy concept supported by some, but not all DRM systems
>   - Emulation in the DRMAA library is not a valid option, since this
> would lead to situations were the reservation already arrives 'too late'
> in the DRM system
>
> Best regards,
> Peter.
>
>
> Am 27.04.11 00:57, schrieb Peter Tröger:
>
> Dear all,
>
> the next DRMAA conf call is scheduled for Apr 27th, 19:00 UTC. We meet
>
> on Skype, please find me under my user name "potsdam_pit".
>
> Preliminary meeting agenda:
>
> 1. Meeting secretary for this meeting?
>
> 2. Solving remaining issues in DRMAAv2 Draft 3 (see attachment, starting
>
> from page 18)
>
> Sorry, I didn't had the time to prepare a new draft.
>
> Best regards,
>
> Peter.
>
>
>
>
> --
>
>   drmaa-wg mailing list
>
>   drmaa-wg at ogf.org
>
>   http://www.ogf.org/mailman/listinfo/drmaa-wg
>
> --
>  drmaa-wg mailing list
>  drmaa-wg at ogf.org
>  http://www.ogf.org/mailman/listinfo/drmaa-wg
>
>
> ---------------------------------------------------------------------
>
> Notice from Univa Postmaster:
> This email message is for the sole use of the intended recipient(s) and may
> contain confidential and privileged information. Any unauthorized review,
> use, disclosure or distribution is prohibited. If you are not the intended
> recipient, please contact the sender by reply email and destroy all copies
> of the original message. This message has been content scanned by the Univa
> Mail system.
>
> ---------------------------------------------------------------------
>
>
>
> ---------------------------------------------------------------------
>
> Notice from Univa Postmaster:
> This email message is for the sole use of the intended recipient(s) and may
> contain confidential and privileged information. Any unauthorized review,
> use, disclosure or distribution is prohibited. If you are not the intended
> recipient, please contact the sender by reply email and destroy all copies
> of the original message. This message has been content scanned by the Univa
> Mail system.
>
> ---------------------------------------------------------------------
>
> --
>  drmaa-wg mailing list
>  drmaa-wg at ogf.org
>  http://www.ogf.org/mailman/listinfo/drmaa-wg
>



-- 
Mariusz


More information about the drmaa-wg mailing list