Dear all, the next DRMAA phone conference is scheduled on May 26th, at 19:00 UTC. The phone conference line is sponsored by Oracle: Phone number (toll-free from US): +001-866-545-5227 Access code: 5988285 In case the phone conference facility is not working, we meet in the following video chat at TokBox: http://www.tokbox.com/conf/cowkc0i1275vyezg You need a Flash-enabled browser, a web cam and a headset for the live talk. We might also use only the text chat - in the case, you Flash is enough. Preliminary meeting agenda: 1. Meeting secretary for this meeting? 2. Support for core file fetching 3. Support for marking re-queueable jobs 4. JobTemplate structuring proposals 5. Other open issues Best regards, Peter. -- drmaa-wg mailing list drmaa-wg@ogf.org http://www.ogf.org/mailman/listinfo/drmaa-wg
Looks like Oracle killed my old Sun conference call number. I guess I'll have to get a new one. For now I guess we just use TokBox. Daniel On 05/26/10 10:23, Peter Tröger wrote:
Dear all,
the next DRMAA phone conference is scheduled on May 26th, at 19:00 UTC.
The phone conference line is sponsored by Oracle:
Phone number (toll-free from US): +001-866-545-5227 Access code: 5988285
In case the phone conference facility is not working, we meet in the following video chat at TokBox:
http://www.tokbox.com/conf/cowkc0i1275vyezg
You need a Flash-enabled browser, a web cam and a headset for the live talk. We might also use only the text chat - in the case, you Flash is enough.
Preliminary meeting agenda:
1. Meeting secretary for this meeting? 2. Support for core file fetching 3. Support for marking re-queueable jobs 4. JobTemplate structuring proposals 5. Other open issues
Best regards, Peter. -- drmaa-wg mailing list drmaa-wg@ogf.org http://www.ogf.org/mailman/listinfo/drmaa-wg
-- drmaa-wg mailing list drmaa-wg@ogf.org http://www.ogf.org/mailman/listinfo/drmaa-wg
In two weeks the dial-in we'll use is: http://www.intercall.com/oracle/access_numbers.htm The conference code is 6513037. The security code is DRMAA (37622). I would suggest that Peter set up another Tokbox session for anyone who wants video. In any case, the phone conference will provide the audio. Daniel On 05/26/10 10:23, Peter Tröger wrote:
Dear all,
the next DRMAA phone conference is scheduled on May 26th, at 19:00 UTC.
The phone conference line is sponsored by Oracle:
Phone number (toll-free from US): +001-866-545-5227 Access code: 5988285
In case the phone conference facility is not working, we meet in the following video chat at TokBox:
http://www.tokbox.com/conf/cowkc0i1275vyezg
You need a Flash-enabled browser, a web cam and a headset for the live talk. We might also use only the text chat - in the case, you Flash is enough.
Preliminary meeting agenda:
1. Meeting secretary for this meeting? 2. Support for core file fetching 3. Support for marking re-queueable jobs 4. JobTemplate structuring proposals 5. Other open issues
Best regards, Peter. -- drmaa-wg mailing list drmaa-wg@ogf.org http://www.ogf.org/mailman/listinfo/drmaa-wg
-- drmaa-wg mailing list drmaa-wg@ogf.org http://www.ogf.org/mailman/listinfo/drmaa-wg
Participants: Dan T, Dan G., Roger, Mariusz, Peter
In case the phone conference facility is not working, we meet in the following video chat at TokBox:
Dan already provided an updated phone number or the next meeting, we will additionally use the TokBox video facility for interested participants.
4. JobTemplate structuring proposals
Discussion of Mariusz proposals: http://fury.man.poznan.pl/~mmamonski/wiki/index.php/DRMAAv2/JobTemplate_-_Bi... - General agreement that we want a job template (JT) struct type in DRMAA-C for 2.0 - Decision that applications should be able to interface multiple DRMAA libraries from one source code - Known examples from DRMAA 1.0 world - meta schedulers - Using implementation-specific JT attributes should not lead to compilation errors then - Option II by Mariusz is out - Option III is a good candidate - one standardized JT attribute which contains all impl.-specific attribute values as dictionary - Leads to the question how this is different from native specification - Majority decision that this makes nativeSpecification attribute obsolete - DRMAA implementors are then enforced to model all their native features in according impl.-specific attributes of the JT - Frees implementation from parsing and analyzing the native specification - Seems to be reasonable for SGE (list of qsub options), Condor (universe specification) and PBS / LSF (maps nativeSpecification anyway to parameter dictionary)
5. Other open issues
- ISC starts in Hamburg this Saturday, Dan is there and would be able to do some DRMAA F2F work - Plan for big final F2F meeting in Potsdam, organized by Peter, somewhere around July / August
participants (2)
-
Daniel Templeton -
Peter Tröger