Job scheduler extension

This package is an extension package to BASE that adds support for interacting with Open Grid Scheduler and Slurm clusters. This package is of no use on it's own. It has been designed to let other extensions submit and monitor jobs on Open Grid and Slurm clusters. This package provides:

• Simple configuration for accessing one or more clusters.
• An API for programmatic submission of jobs to the clusters.
• A service that monitor the status and progress of submitted jobs.
• BASE jobs are used as proxies and can provide full progress reporting (with some help from the job scripts).
• Asynchronous callback methods are used to notify the extension when submitted jobs have been completed.

Documentation

• BASE 3.16 and Java 11 or higher is required.
• README​
• Installation and configuration instructions
• How to use the Job scheduler package API
• Javadoc API documentation

License

• ​GNU Affero General Public License version 3.

Download

Version	Revision	Date	Binary (tar.gz)	BASE Version	Special notes
1.4	-	-	not yet released	3.16 or later	Added support for Slurm	changelog
1.3	5565	August 14, 2019	opengrid-1.3.tar.gz​ (1.0MB)	3.15 or later	Java 11	changelog
1.2	4935	August 23, 2018	opengrid-1.2.tar.gz​ (632kB)	3.13 or later	-	changelog
1.1	4502	May 10, 2017	opengrid-1.1.tar.gz​ (4.0MB)	3.11 or later	-	changelog
1.0	4327	February 1, 2017	opengrid-1.0.tar.gz​ (3.9MB)	3.10 or later	-	changelog

Source code can be downloaded from the subversion repository. Use the following command to get source code for the 1.3 version:

svn co http://baseplugins.thep.lu.se/svn/extensions/net.sf.basedb.opengrid/tags/1.3 opengrid-1.3

The latest development (maybe unstable; do not use on a production server) revision can be checked out from the repository using the following command:

svn co http://baseplugins.thep.lu.se/svn/extensions/net.sf.basedb.opengrid/trunk opengrid-dev

Contribute

After making modifications to the source code, compose a clear and concise log message to describe those changes and the reasons for them. Then, send an email to the developers list containing your log message and the output of svn diff (from the top of your subversion working copy). If the community members consider your changes acceptable, someone who has commit privileges will add your changes to the public source code tree. Recall that permission to directly commit changes to the repository is granted on merit - if you demonstrate comprehension of subversion, programming competency, and a team spirit, you will likely be awarded that permission.

Todo

No results