Hi, In recent times I don't have time anymore to carry on the development of drmaa-python, the drmaa Python implementation I wrote some time ago. For this reason, I'm looking for a new maintainer taking the project ownership, please drop me a note if interested. Best Regards, Enrico
<div><div dir="ltr">Hi,<div><br></div> <div>I'm an external collaborator (and former PostDoc) of the Computer Architecture and Operating Systems Department at the Universitat Autonoma de Barcelona. </div> <div><br></div> <div>Some time ago, we have developed a Simulation Management Tool using DRMAA to interact with our computer clusters in the department. Now, we're planning to upload and release the project in Google Code (under construction web <a href="http://code.google.com/p/sim-mgmt-tool/">http://code.google.com/p/sim-mgmt-tool/</a>) under the GNU GPL v2.</div> <div><br></div> <div>Is there any correct or standard procedure for citing/mentioning DRMAA in this situation? Should we include some reference to the DRMAA project/website somewhere in the source code?</div> <div> <br> </div> <div>Thank you!</div> <div><br></div> <div>Best regards,</div> <div>Gonzalo Zarza</div> </div></div>
Dear DRMAA friends, first, a late happy 2013 for all of you. I hope that you make good progress in your DRMAAv2 implementation projects. Daniel Gruber raised a critical issue for the published C binding spec: https://redmine.ogf.org/issues/57 My proposal would be to follow Daniel's suggestion and fix the reference implementation header file: https://github.com/troeger/drmaav2-mock/blob/master/drmaa2.h We point the people to this code base anyway, so it is the easiest solution for making sure everybody uses the same work-around. The issue tracker archives the modification until we have enough complete implementations for an errata document. Any opinions ? Best regards, Peter. P.S.: https://redmine.ogf.org/issues/59 might be also worthwhile a look.
Dear DRMAA friends, first, a late happy 2013 for all of you. I hope that you make good progress in your DRMAAv2 implementation projects. Daniel Gruber raised a critical issue for the published C binding spec: https://redmine.ogf.org/issues/57 My proposal would be to follow Daniel's suggestion and fix the reference implementation header file: https://github.com/troeger/drmaav2-mock/blob/master/drmaa2.h We point the people to this code base anyway, so it is the easiest solution for making sure everybody uses the same work-around. The issue tracker archives the modification until we have enough complete implementations for an errata document. Any opinions ? Best regards, Peter. P.S.: https://redmine.ogf.org/issues/59 might be also worthwhile a look.
Hi Antonio, > I'm a researcher at the Brazilian National Laboratory for Scientific > Computing (LNCC -- http://www.lncc.br), and also the executive > secretary of the Brazilian National System for High-Performance > Computing (SINAPAD -- http://www.lncc.br/sinapad). Very briefly, we > use DRMAA specs in SINAPAD for providing APIs to scientific portals > and we'd be quite interested in the OCCI-DRMAA initiative. I found > some pointers to a draft specification, but I'm not allowed to get to > them, even being registered in GridForge. As the Redmine project page says, you can clone the repository with the specification document sources: git clone http://redmine.ogf.org/git/standards/applications-area/drmaa-wg/drmaav2-occi-binding.git Please note that this is a document under work. Furthermore, the OCCI-DRMAA standardization is currently suspended, since the OCCI guys need to improve at some points first. One example is the currently missing pagination support in OCCI. You find according comments in the TEX file. > Where can I get such draft so to evaluate its ideas' applicability in > the SINAPAD context? Read the current document, take nothing for granted, and come back with your ideas :) Beside that, what about DRMAAv2 support in your projects ? Any language bindings you need to have beside C and OCCI ? Best regards, Peter. > > Thank you in advance for your attention. > > Best regards, > -- > Antonio Tadeu Azevedo Gomes, DSc. > http://www.lncc.br/~atagomes > http://www.lncc.br/sinapad > http://martin.lncc.br
No, it's not a typo, it is "v1"I started this project over 3 years ago when I needed an interactive DRMAA shell, but I had to set it aside in 2010 when I started a new job that didn't leave me any spare time. It was almost finished then. I have now managed to tie up the loose ends, it even passes the tests in the test suite, and upload it to Github. The sources are here: https://github.com/fredyouhanaie/drmaatcl There is a PDF document, generated from the source code, in the downloads area: https://github.com/downloads/fredyouhanaie/drmaatcl/drmaatcl-main-14124b9.pdf See the PDF for examples of use, or the "Examples/" directory in the source tree. Now, where did I leave that DRMAAv2 spec? :) Cheers Fred Youhanaie
Dear all, I am happy to inform you that the C binding specification for DRMAAv2 was finally approved. It is now OGF standard GFD-R-P.198. It is now the time to focus on adoption. The reference implementation is more or less finished, feel free to fork your own version for a quick start: https://github.com/troeger/drmaav2-mock New language bindings (Java, Python, ...) only make sense if we have some DRMAAv2 implementations for real systems in place. Best regards, Peter. Anfang der weitergeleiteten Nachricht: > Von: redmine@... > Betreff: [Editor - document #37] Distributed Resource Management Application API Version 2 (DRMAA) - C Language Binding > Datum: 9. November 2012 20:51:04 MEZ > An: undisclosed-recipients:; > > > Issue #37 has been updated by Greg Newby. > > > This has been approved for publication by the standards council. It will now be published as GFD-R-P.198. Thanks to authors/editors for their efforts! > ---------------------------------------- > document #37: Distributed Resource Management Application API Version 2 (DRMAA) - C Language Binding > https://redmine.ogf.org/issues/37#change-55 > > Author: Peter Tröger > Status: final review > Priority: Normal > Assignee: Greg Newby > Category: > Target version: > > > In continuation of https://forge.ogf.org/sf/go/artf6556 , this is the final version of the document after public comment period. > > The meeting minutes for the discussion of all public comments are here: > > http://www.ogf.org/pipermail/drmaa-wg/2012-August/001491.html > > > > > -- > You have received this notification because you have either subscribed to it, or are involved in its topic. > To change your notification preferences, please click here: http://redmine.ogf.org/my/account
Dear all, I am happy to inform you that the C binding specification for DRMAAv2 was finally approved. It is now OGF standard GFD-R-P.198. It is now the time to focus on adoption. The reference implementation is more or less finished, feel free to fork your own version for a quick start: https://github.com/troeger/drmaav2-mock New language bindings (Java, Python, ...) only make sense if we have some DRMAAv2 implementations for real systems in place. Best regards, Peter. Anfang der weitergeleiteten Nachricht: > Von: redmine@... > Betreff: [Editor - document #37] Distributed Resource Management Application API Version 2 (DRMAA) - C Language Binding > Datum: 9. November 2012 20:51:04 MEZ > An: undisclosed-recipients:; > > > Issue #37 has been updated by Greg Newby. > > > This has been approved for publication by the standards council. It will now be published as GFD-R-P.198. Thanks to authors/editors for their efforts! > ---------------------------------------- > document #37: Distributed Resource Management Application API Version 2 (DRMAA) - C Language Binding > https://redmine.ogf.org/issues/37#change-55 > > Author: Peter Tröger > Status: final review > Priority: Normal > Assignee: Greg Newby > Category: > Target version: > > > In continuation of https://forge.ogf.org/sf/go/artf6556 , this is the final version of the document after public comment period. > > The meeting minutes for the discussion of all public comments are here: > > http://www.ogf.org/pipermail/drmaa-wg/2012-August/001491.html > > > > > -- > You have received this notification because you have either subscribed to it, or are involved in its topic. > To change your notification preferences, please click here: http://redmine.ogf.org/my/account
Dear all, this is a unique opportunity to summarize our latest DRMAAv2 work in a scientific publication. We can discuss our abstraction approaches that finally lead to the standardized API design. Who is interested to join me in the paper writing ? It would be also nice to have some early adopter talking about prototype work and the resulting performance numbers. Best regards, Peter. Anfang der weitergeleiteten Nachricht: > Von: "Sill, Alan" <alan.sill@...> > Betreff: [wg-all] JOGC Special Issue - Cloud Interoperability, Federation, Frameworks and APIs > Datum: 17. September 2012 09:40:07 MESZ > An: OGF Work Groups <wg-all@...> > > Call For Papers: > > Journal of Grid Computing Special Issue: > Interoperability, Federation, Frameworks and Application Programming Interfaces for IaaS Clouds > > The Special Issue on Interoperability, Federation, Frameworks and Application Programming Interfaces for Infrastructure-as-a-Service (IaaS) Clouds will highlight foundational standards and application programmer interfaces (APIs) useful for large-scale, scalable distributed computing. > > This issue will provide the community with dedicated forum for presenting new research, development, and deployment efforts in running interoperable, federated IaaS cloud systems. Priority will be given to submissions that focus on presenting solutions to challenges faced by current and future infrastructure cloud toolkits and APIs, and on frameworks that allow their use across a broad range of platforms and user communities.Accepted papers will be published in the prestigious Springer Journal of Grid Computing (JOGC), which has impact factor 1,31. > > Link: > http://cac.hpcc.ttu.edu/jogc/cloud-interop-2012/ > > Special Issue Guest Editors: > * Alan Sill (alan.sill@...), Texas Tech University & Open Grid Forum > * Gabor Kecskemeti (kecskemeti.gabor@...), MTA SZTAKI, Hungary > > Editors-in-Chief: > * Peter Kacsuk, Hungarian Academy of Sciences & University of Westminster > * Ian Foster, University of Chicago & Argonne National Laboratory > > For further information, see the attached flyer or visit the special issue web site at the link above. > > -- > The wg-all mailing list is an umbrella list for all > OGF mailing lists. If you are subscribed to any OGF > mailing list, you will receive mails to wg-all. > > You can unsubscribe from this list on > > http://www.ogf.org/cgi-bin/perl/unsubscribe-wg-all.pl > > wg-all mailing list > wg-all@... > https://www.ogf.org/mailman/listinfo/wg-all
Dear all, this is a unique opportunity to summarize our latest DRMAAv2 work in a scientific publication. We can discuss our abstraction approaches that finally lead to the standardized API design. Who is interested to join me in the paper writing ? It would be also nice to have some early adopter talking about prototype work and the resulting performance numbers. Best regards, Peter. Anfang der weitergeleiteten Nachricht: > Von: "Sill, Alan" <alan.sill@...> > Betreff: [wg-all] JOGC Special Issue - Cloud Interoperability, Federation, Frameworks and APIs > Datum: 17. September 2012 09:40:07 MESZ > An: OGF Work Groups <wg-all@...> > > Call For Papers: > > Journal of Grid Computing Special Issue: > Interoperability, Federation, Frameworks and Application Programming Interfaces for IaaS Clouds > > The Special Issue on Interoperability, Federation, Frameworks and Application Programming Interfaces for Infrastructure-as-a-Service (IaaS) Clouds will highlight foundational standards and application programmer interfaces (APIs) useful for large-scale, scalable distributed computing. > > This issue will provide the community with dedicated forum for presenting new research, development, and deployment efforts in running interoperable, federated IaaS cloud systems. Priority will be given to submissions that focus on presenting solutions to challenges faced by current and future infrastructure cloud toolkits and APIs, and on frameworks that allow their use across a broad range of platforms and user communities.Accepted papers will be published in the prestigious Springer Journal of Grid Computing (JOGC), which has impact factor 1,31. > > Link: > http://cac.hpcc.ttu.edu/jogc/cloud-interop-2012/ > > Special Issue Guest Editors: > * Alan Sill (alan.sill@...), Texas Tech University & Open Grid Forum > * Gabor Kecskemeti (kecskemeti.gabor@...), MTA SZTAKI, Hungary > > Editors-in-Chief: > * Peter Kacsuk, Hungarian Academy of Sciences & University of Westminster > * Ian Foster, University of Chicago & Argonne National Laboratory > > For further information, see the attached flyer or visit the special issue web site at the link above. > > -- > The wg-all mailing list is an umbrella list for all > OGF mailing lists. If you are subscribed to any OGF > mailing list, you will receive mails to wg-all. > > You can unsubscribe from this list on > > http://www.ogf.org/cgi-bin/perl/unsubscribe-wg-all.pl > > wg-all mailing list > wg-all@... > https://www.ogf.org/mailman/listinfo/wg-all
Dear all, as decided at OGF35, here is the errata for DRMAAv2 that brings the root spec back in sync with the final C binding you got yesterday. Please check if your favorite flaw is covered in this document. I will send it to the OGF editors in 24h. Best regards, Peter.
Dear all, since the public comment period for DRMAAv2 C-binding is over, we need to discuss our reaction on the comments. The next DRMAA conf call is therefore scheduled for Wednesday, August 22, 19:00 UTC - 20:00 UTC. We meet on Skype, please find me under the nickname "potsdam_pit". Preliminary meeting agenda: 1. Meeting secretary for this meeting? 2. Status report by the participants 3. Public comments on DRMAAv2 C-binding (http://ogf.org/gf/docs/comment.php?id=388) - pointer NULLing by the library ? What it means for the interface ? - Problems with OStype and CPUtype enumerations - Semantics of DRMAA2_DATA_SEG_SIZE - Additional free functions needed - Return type for wait functions - _j_ vs. _job_ - Small issues Best regards, Peter.
Dear all, since the public comment period for DRMAAv2 C-binding is over, we need to discuss our reaction on the comments. The next DRMAA conf call is therefore scheduled for Wednesday, August 22, 19:00 UTC - 20:00 UTC. We meet on Skype, please find me under the nickname "potsdam_pit". Preliminary meeting agenda: 1. Meeting secretary for this meeting? 2. Status report by the participants 3. Public comments on DRMAAv2 C-binding (http://ogf.org/gf/docs/comment.php?id=388) - pointer NULLing by the library ? What it means for the interface ? - Problems with OStype and CPUtype enumerations - Semantics of DRMAA2_DATA_SEG_SIZE - Additional free functions needed - Return type for wait functions - _j_ vs. _job_ - Small issues Best regards, Peter.
All, The getExitStatus() of the JobInfo object, returned by a call to Session.wait(Session.JOB_IDS_SESSION_ANY, Session.TIMEOUT_WAIT_FOREVER), is returning an exit status of 0. This is incorrect since I know my job is returning an exit status of 3: submitting my job using "qsub -sync y" yields an exist status of 3. I'm using: drmaa-gridengine-6.2u5.jar drmaa-common-1.0.jar and libdrmaa.so.1.0 from ge2011.11 Does anyone know why I get different values of exit status? Any pointers, potential bug fixes or potential threading issues with the implementation of org.ggf.drmaa.Session? If you need more information please do not hesitate to ask. -- Kind regards, Ian Johnson Software Engineer ian.johnson@... Applied Language Solutions High quality language solutions delivered on time...with a smile! www.appliedlanguage.com Tel (UK): +44 (0)845 367 7000 Tel (US): +1 (800) 579-5010 Riverside Court, Huddersfield Road, Delph, Oldham, OL3 5FZ. UK Registered in the UK 5122429 Pride in everything we do | Respect everyone like a friend Think of the environment; please don't print this e-mail unless you really need to.
Dear all, we had a small but productive meeting at OGF35. Beside the further discussion about OCCI-DRMAA, we analyzed the DRMAAv2 C binding comments collected so far: - We support the proposal by Daniel to introduce an overall drmaa2_string type, instead of using the native char* in the binding. The intended semantic is to use drmaa2_string whenever the application is supposed to clean up such variable. This can be done by calling drmaa2_string_free() or the free function of the surrounding structure (e.g. with job templates), depending on the context. This freeing demand must be documented in the spec. It should further be clarified that drmaa2_string_list will return drmaa2_string items in the get() operation. - The pointer-nullification-on-free issue, which would lead to a complete shift to double-indirected pointer parameters, has to be decided in a voting. - We agree to the proposal of Stephan Klauck for introducing additional interface handle free functions. This leads to a rejection of the "_h" suffix proposal. - There was no clear consensus about the MACOSX issue raised by Rayson Ho, so this must be decided in the voting procedure. We obviousely agreed to the TRU64 issue also raised by him. Both things will change the root spec. - We agree to the 64bit processor architecture issue raised by Rayson. The current proposal is to add 64Bit variations for all identified ISAs. A voting is needed on the latter idea. This will again change the root spec. - We support the proposal by Stephan Klauck to have an UNSET definition for JobInfo instance. - We support the idea of Rayson Ho to rename DATA_SEG_SIZE to DATA_SIZE. This will change the root spec. - We agree to the comment from Stephan Klauck that the Job::wait... functions should return void. This will change the root spec. The list of resulting open root spec issues (there are more) was approved by the participating group members. We further agreed on submitting the root specification errata and the finalized C binding spec together after the end of the public comment period. Meanwhile, please check the root specification issues here: http://redmine.ogf.org/projects/drmaav2-root-spec/issues Best regards, Peter. P.S.: If you want to know details about the OCCI-DRMAA progress, just let me know.
 |
|
|
|
|
|
|
| Mon | Tue | Wed | Thu | Fri | Sat | Sun |
|---|---|---|---|---|---|---|
| 1 | 2 | 3 | 4 | 5 | ||
| 6 | 7 | 8 | 9 | 10 | 11 | 12 |
| 13 | 14 | 15 | 16 | 17 | 18 | 19 |
| 20 | 21 | 22 | 23 | 24 | 25 | 26 |
| 27 | 28 | 29 | 30 | 31 |
RSS Feed4 | |
|---|---|
2 | |
4 | |
3 | |
6 | |
3 | |
3 | |
27 | |
5 | |
7 | |
5 | |
7 | |
3 | |
6 | |
3 | |
4 | |
35 | |
20 | |
27 | |
7 | |
10 | |
5 | |
18 | |
6 | |
3 | |
15 | |
28 | |
15 | |
4 | |
7 | |
81 | |
16 | |
10 | |
6 | |
6 | |
16 | |
11 | |
12 | |
10 | |
8 | |
12 | |
5 | |
13 | |
7 |