GridSAM provides a job submission interface for submitting computational jobs to many commonly used distributed resource management systems (Condor, PBS, SGE, etc.).
The latest version of GridSAM can be downloaded from SourceForge.
GridSAM endpoints are available on the NGS for registered NGS users. See the NGS website for further information.
GridSAM will run on most versions of Linux, Windows and Mac OS X. GridSAM can be used within the container provided by the Development Kit. If you wish to use GridSAM as a standalone Software Component, it will require a servlet container in which to operate.
- SourceForge Homepage
- Help and FAQ Forum
- Draft Roadmap for public comment
- Supported platforms
- Licence: BSD
- Mailing List
- Follow GridSAM on Twitter
- DOAP record: gridsam-doap.xml
The GridSAM tutorial was developed by OMII-UK's GridSAM expert, Justin Bradley. It shows how to run a command-line-based client: from generating results locally, through to running the same command line in a controlled manner on GridSAM. The tutorial is aimed at researchers who would like to learn more about deploying a custom GridSAM application in a grid environment. Systems administrators and technical managers would also benefit from the tutorial.
What can it do?
GridSAM offers a simple open-standards-based Web Service for job submission. It handles submission of jobs to distributed compute environments, status monitoring, and data staging in and out of the compute environment.
GridSAM can submit jobs to a range of back-end distributed compute environments: Condor, PBS, Globus Toolkit 2, Sun Grid Engine and DRMAA interfaces. For data staging purposes, GridSAM can use HTTP, HTTPS, WebDAV, SCP, FTP, and GSIFTP. It can be extended to use any Apache Commons VFS plugin.
GridSAM offers a Java API for job submission and monitoring directly from code, plus a set of command-line tools. Jobs for submission are described using standard JSDL. An OGSA-BES submission interface is available, in addition to the native GridSAM submission service.
How does it work?
The GridSAM server runs within a standard Java servlet container, such as that provided with the OMII-UK Development Kit. It presents, using Web Services, both a "native" GridSAM submission interface and an OGSA-BES interface. Each GridSAM server can be configured to submit jobs to a given distributed resource manager (DRM) environment. A job-submission document is submitted to the server and used by it to arrange the staging-in of files for each job, the execution of that job on suitable resources via the DRM, and the staging-out of the final data. While the job is running, the GridSAM interface can be used to inspect the current status of the running job, e.g. to see if the job has completed. GridSAM can monitor the status of many concurrently running jobs on the back-end DRM.
Job-submission documents (written in JSDL) can be sent to the GridSAM service through either of the two web interfaces, or through a simple set of command-line-interface tools. In each case, the main component of the job submission is the JSDL document describing the data staging and job parameters.
For advanced developers producing their own systems, the GridSAM core can be removed from its Web Services container, and embedded directly into other products to act as an API, providing a common interface to the supported DRMs and to provide completely asynchronous job-monitoring functions.