|
|
|
|
|
Grid(Lab) Resource Management
|
 |
GRMS Frequently Asked Questions
|
1. What is the GRMS?
|
|
2. What do I need to deploy the GRMS?
|
|
3. What else except Globus do I need on resources?
|
|
4. What is the funcionality of the GRMSv1.0.0?
|
|
1. What is the GRMS?
|
|
The GridLab Resource Management System (GRMS) is an open source meta-scheduling system,
developed under the GridLab IST-2001-32133 project, which allows developers to build
and deploy resource management systems for large scale distributed computing infrastructures.
The GRMS provides developers of user-level functionalities with a more abstract view of low level
and complex Grid technologies. Based on dynamic resource selection, mapping and advanced scheduling
methodology, combined with feedback control architecture, it deals with dynamic Grid environment
and resource management challenges, e.g. load-balancing among clusters, remote job control or file staging support.
Therefore, the main goal of the GRMS is to manage the whole process of remote job submission to various
batch queuing systems, clusters or resources. It has been designed as an independent core component
for resource management processes which can take advantage of various low-level Core Services
and existing technologies. Finally, the GRMS can be considered as a robust system which provides
abstraction of complex grid infrastructures as well as a toolbox which helps to form and adapts
to distributing computing environments.
|
|
2. What do I need to deploy the GRMS?
|
|
The first release of the GRMS is based on the Globus 2.X and uses Globus Core Services deployed on resources,
in particular GRAM, GridFTP and GRIS/GIIS services. Therefore, you need at least all these Core Services installed and configured correctly
on all resources and front ends you are going to manage using the GRMS
(see the Globus project page).
The GRMS is a persistent service within the Tomcat environment and it supports Grid Security Infrastructure by providing the GSI-enabled web service interfaces
for all clients, e.g. portals or applications, and thus can be integrated with any other middleware grid environment.
The GRMS has been developed entirely in Java and thus could be installed on various operating systems and resources.
One of the main assumptions for the GRMS is to perform remote jobs control and management
in the way that satisfies Users (Job Owners) and their applications requirements.
All users requirements are expressed within XML-based resource specification
documents and sent to the GRMS as SOAP requests/responses over GSI transport layer connections.
|
|
3. What else except Globus do I need on resources?
|
|
Nothing... Then you will be able to take advantage of basic GRMS functionality.
But if you need to establish more reliable and robust middleware infrastructure,
then you will have to install some additional GridLab Middleware Services
and software on resources.
|
|
4. What is the basic funcionality of the GRMSv1.8.0?
|
The first release of the GRMS provides the following functionalities:
-
to choose dynamically the best available resource or queuing system for the remote job execution according to provided Job Description, GRMS configuration and Administrator preferences,
-
to stage-in and stage-out files (input files, output files, stdin, stdout, stderr) required by jobs and users before and after executions according to provided Job Description,
-
to use Core Services (GridFTP/GASS/FTP) or GridLab Middleware Services (Replica Catalog Service and Data Movement Service) for staging files.
-
to setup environments before and after job execution according to provided Job Description,
-
to submit and control a job remotely,
-
to run single batch, MPI and Java jobs remotely,
-
to cancel a job remotely,
-
to check a job status remotely,
-
to check detailed information about a host on which a job is/has been executed,
-
to check a list of candidate resources for job and its Job Description,
-
to check a list of jobs submitted in the past by user,
-
to register callback information in the GRMS,
-
to migrate a GAT-enabled application to a resource according to provided Job Description.
|
 |
 |
GridLab: Grid Application Toolkit and Testbed
is co-funded by the European Commission under the Fifth Framework Programme
(IST-2001-32133).
Web admin: Petr Holub, web design: Radoslaw Strugalski
Last update on Tuesday, 05-Apr-2005 15:20:45 CEST.
|
| |
