Return to GAP

GARUDA Access Portal User Manual version 2.1

1. Introduction

2. Login

3. Job Management

3.1 . Basic Submission

3.2 . Resubmission of Job

3.3 . Sequential/MPICH Job Submission

3.4 . XML Job Submission

3.5 . Job Info

4. Resources

5. File Manager

5.1 . File Management

5.2 . GSRM File Upload

5.3 . GSRM File Download

5.4 . GSRM Reservation cum File Upload

6. Accounting

7. CompilerService

8. Mobile job Submission and Status

9. Partner Site

10. Notices

11. Faqs

12. Browsers and Versions that support Grid Portal

13. Types of MPI supported

1. Introduction

Grid portal is for submitting sequential, parallel and heterogeneous jobs to the grid. A grid is a cluster of heterogeneous workstations located at geographically distant locations, and with the ultimate aim of sharing computing resources. This portal provides a web interface for viewing the resources and submitting and monitoring jobs.

2.Login

This interface is allowing the user to login into the Portal by entering Valid Username and Password at the respective fields..Portal is initializing the proxy for the user based on selected VO Name.The User must accept the GARUDA User Policy by selecting the check box button. if not the user will be getting "You have to agree terms and conditions" alert message.

user needs to select the check box with label "I am first time user of portal/change of VO " if user is logging into the portal for the first time or wants to change VO Name.On selection of this check box combo box with VO names will enable on top of it.user needs to choose the suitable VO as allocated by VO Grid Admin.With out VO name portal will not allow user to login into portal.

After entering the required fields, by clicking on Login button,user will logged into GAP2 job submission page and the Proxy credentials will be initialized for the selected VO for the period of 7 days.After login user can access the grid services like job Management,Resources info,File Management,accounting.. etc

List of common error messages while login into the portal.

1)You are not a member of this VO.Please select VO Name you belongs to.

If user provided the wrong or invalid VO Name

2)No credential for given user exist on myproxy server.Please upload your p12 certificate.
If user credential is not available in myproxy server, web page will be automatically redirected to upload p12 certificate.

3)Credentail exist on the server but it has been expired.please upload your p12 certificate

If user credential is available but expired in myproxy server,web page will be automatically redirect to upload new p12 certificate.

4)Please select VO name if you are first time user.

If user is accessing portal for the first time without selecting check box "I am a First Time User of this page / Change of VO" .

On successful uploading of p12 certificate into myproxy server ,your proxy will initialize and able to login into the portal

Top

3. Job Management

User can submit their job, monitor the status and view output files using the Job Management interfaces. There are three simple tabs in this interface. The first tab provides interface for Basic Job Submission, the second for Sequential/MPICH Job Submission, the third for XML Job Submission and the fourth for obtaining Job Information.

3.1 Basic Submission

This is the preferred option. Users are generally discouraged from using the Sequential/MPICH or XML Submission options, since Basic Submission makes better use of the available resources.

This interface can be used to submit sequential as well as parallel jobs. The user should select the Operating System to suit their Job and the type of job they want to execute. Then the user has to provide the corresponding executable. User should also provide the input file if the job requires it. The executable ,the input file and STDIN file can either be uploaded from the local machine or can be selected from the Remote File List, if it is available in the Submit Node or can be selected from the GSRM(Garuda Storage Resource Manager) server.On selecting GSRM server will list the files which you stored in GSRM server.If you want to upload any files into GSRM server please go to FileManagement portlet and click on GSRM File Upload.

Total number of processes required for the job, should also be provided by the user. This parameter is only for the parallel applications that requires more than one cpu.If the job requires any Command Line arguments or Environment Variables, then the user should also furnish it, before submitting.

All those fields marked with * are mandatory fields and should be filled before submitting a job.


STDIN option is required when the user wants to provide any inputs to the application during the runtime.

Walltime option is newly added. Wall time is "Maximum amount of real time during which the job can be in the running state". By default wall time in Portal is set as 6 days. If user want more than that, it could be modified according to the application requirements.

User Specific Output files option is required if the user application generates any output/error files other than standard output/error files and its entries should be separated by comma's or single empty space in case of multiple files.

User can provide a suitable Job Name to their job in the text box provided for it. But it is optional. The user can optionally provide Execution Time. Here the Execution Time is the anticipated job completion time.

After clicking the submit button the portal submits the job to GridWay Meta Scheduler, it then schedules the job for execution returning the Job Id. This Job Id is displayed in the Basic Submission interface. The jobid has to be noted for future reference to this job.

In the event of unsuccessful submission, the corresponding error message is displayed.

We strongly suggest that you check out the "Notices" link to know about any issues in job submission to any cluster, before doing the actual job submission, since the known issues will be mentioned in 'Notices'.

3.2 Resubmission of Job

Allows the user to view the selected Job Id details and Resubmit the jobs with/without updating the relevent fields. "Resubmission of Job" is a newly introduced facility in basic job submission page, is useful for the users who want to submit the same job repeatedly with small modifications.By selecting job Id and clicking on "View job details", the details of the job id which is already submitted in respective fields are shown .User can submit the job once again by modifying or updating the i/p files,user specific output,error files and other options like wall time,environment variables,command line arguments etc..

3.3 Sequential/MPICH Job Submission

We encourage the users to use the Basic Submission option rather than the Sequential/MPICH or XML Submission options, since Basic Submission makes better use of the available resources.

This interface is also provided for the user to submit Sequential and Parallel Jobs. The only difference with this submission is, it is using GT4 Web Services components for submitting jobs to the Grid instead of Gridway as scheduler.

However this version does not support Heterogeneous kind of job submission into the Grid. The user has to select the OS and provide corresponding executable. The executable and the input file can either be uploaded from the local machine or can be selected from the Remote File List, if it is available in the Submit Node.

For submitting Parallel jobs, the user needs to select the No. of Process is more than one from the combo box. The meaning of No. of Process is the total number of tasks or processes required to run the application and not in the hardware context of the cpus available in the system. Also the No. of Nodes selection helps the user to achieve the optimal performance of the application and it allows the job scheduler to divide the number of tasks across the nodes. For example if the user selects the number of node is 2 and the number of process is 4, the job scheduler spawns two process in one node and another two process in remaining node, so here the total number of tasks are 4 which will be allocated to the application. In case of any invalid selection like No. of Nodes is 8 and the No. of Process is 4, the job scheduler simply ignores the value of the No. of Nodes.

After the all the required entries are added the user can submit the job by clicking the submit button. After submission the Grid Portal creates the XML file, which is required for submitting job to globus. After submission the jobid appears at the bottom of this interface.

In the event of unsuccessful submission, the corresponding error message will appear at the bottom of this interface.

3.4 XML Job Submission

Using this interface, the user can provide their-own XML file as the executable provided the required files are available in the submit node. Except the XML file as Executable parameter, the remaining parameters and its functionalities are same as Sequential/MPICH Job Submission module. This job submission option is recommended only for advanced users.

We strongly suggest that you check out the "Notices" link to know about any issues in job submission to any cluster, before doing the actual job submission, since the known issues will be mentioned in 'Notices'.

3.5 Job Info

The information about the jobs that are submitted through this portal can be obtained from this interface. Here the user could view the status of the job and the output file of the job by specifying their Job Id. The output file, error file can be downloaded by clicking the Download button.

The user can cancel Job by selecting the job id and clicking the Cancel Job button. After the job is canceled the acknowledgment is provided as a simple message. The user can cancel only those jobs, which are in queue. Trying to cancel a job, which has been removed from the Job queue will throw an error and this message will also be displayed to the user.

After confirming the completion of a particular Job its output, error file can be viewed by selecting the corresponding file option and clicking the view button. If the output file is in the form of text then it will be displayed in the Text Area. The error file content if any will also be displayed in the Text Area. The output, error file can be downloaded by selecting the corresponding file option and clicking the Download button.

4. Resources

Using this interface user can view the resources information provided by the GridWay scheduler. The information about Node Name, Head Node, OS, ARCH, Load Average, Status, Configured Process and Available Process are displayed in Table format. Users can use this information to select a suitable cluster to submit their job.

5. File Manager

5.1 File Management(GRID Head Node)

GHN-Grid Head Node (gridfs)

This interface provides the standard file management functionalities such as

1.Copy
2.Move
3.Remove
4.Create Directory

This module allows the users to carry out the basic file management functionalities of Grid Head Node (GHN) such as Copy, Create Directory, Move and Remove which are listing in combo box. These functionalities are similar to UNIX file operations.

By default the 'Copy' option is getting listed, when the user clicks on the FM interface, by clicking on the 'Grid Head Node' from the Source, the portal home directory of the user will get listed from the Pop up window, from this user can select any file from the portal home directory or its sub directories as a Source for copying the file.

Similarly clicking on the 'Grid Head Node' from the Destination, the portal home directory will get listed and by clicking on 'OK', the destination will get selected and also having the option to create the new directory in the respective place as a destination path.

After selecting the Source and Destination by clicking on 'Submit' button the file will get copied into the destination path. Similarly, the user has to follow the above steps for other functionalities Move and Create directory also.

The 'Local' option allows the user to upload the file into the GHN from their local desktop i.e where the Grid Portal is launched.

By selecting 'Remove' option from combo box and clicking on 'Submit' button, it will pop up a File Browser of GHN of the logged user. From this user can browse their entire directory structure and also by selection of check box (es) and clicking on remove the respective files will get removed from the GHN. However the removal of directory is not allowed.

5.2 GSRM File Upload

This module allows the user to upload file into the GSRM data grid. For this, the user needs to select the files from 'Grid Head Node' or from the desktop using 'Local' option, as Source and required to select the suitable directory name as the Destination by Clicking the 'SRM Files' button. And there is option for the user to select the Reservation ID by clicking on the field 'Use Disk Space Reservation', this will make sure that user will be getting the Disk space as per the reservation id. The user can also obtain a details of the corresponiding Reservation ID by clicking on 'Get Status' button

After selecting the Source and Destination info, by clicking on 'Upload Submit' button the corresponding file will get uploaded into GSRM datagrid and suitable message will be updated with the page based on the status of the Upload.

5.3 GSRM File Download

This module allows the user to download the file from GSRM datagrid into the Grid Head Node. For this, the user needs to select the file from 'SRM Files' button as Source and required to select the suitable directory name as Destination by clicking the 'Grid Head Node' button.

After selecting the Source and Destination information, by clicking on 'Download Submit' button the corresponding file will get downloaded into GHN from GSRM datagrid and suitable message will be updated with the page based on the status of the download.

5.4 GSRM Reservation cum File Upload

The SRM Reservation portlet is allows the user reserve the disk space from GSRM for the specified period of time. The user needs to enter the 'Disk Space' value interms of MB and provide the 'Time Duration' value interms of Number of Days and by clicking on 'Submit' button, the specified disk space will get for the user and suitable message will be updated withe page on the statu of reservation. This portlet also have the option to reserve the disk space with File upload feature.The user needs to select the option for using this facility and steps for same as the Upload module.

Top

6. Accounting

This module provides Accounting information of all the jobs that are submitted through the Grid Portal.

Archive Data

On clicking this Accounting Button, by default userwise radio button is enabled to view the last one month(30 days) data of the total no. of jobs and accounting info of various system parameters such as Memory usage, Virtual memory,wall time,cpu time; similarly clusterwise can be obtained by clicking on clusterwise button.

The user has the various options to get the userwise and clusterwise info for the specific period in terms of days by clicking on submit button using the combo boxes Name of the User,Name of the cluster,Start date and End date.

7. Compiler Service

click here

8) Mobile job Submission and Status

    SMS to Mobile : 09844461835

    1. Re-submit job using SMS

    SUBMIT 'GridFS username' 'GridFS password' 'jobID'

    Example: SUBMIT raju121 test123 20165

    2. Checking Job status using SMS

    STATUS 'GridFS username' 'GridFS password' 'jobID'

    Example: STATUS raju121 test123 20166

    Important Notes!!

1. The username and password are case sensitive.
2. The job ID shall not be alphanumeric or contain any special characters or decimal values.
3. The job ID will be purely numeric with 5 digits

9. Partner Site

This interface provides the facility for GARUDA Partners to create and update their web pages. Currently we have provided this facility only for a few Partners and remaining Partners need to send a request to grid-help@cdac.in by mail for editing/updating their respective pages in the Partner site web page. To get more Help information about the Partner site, please browse the following links,

a. Creating/editing contents
b. Viewing the website

Alternatively you can browse through the Help -> Guided Tour Menu and then navigate to the above pages, by clicking on User -> My Space -> Edit Website from the left-side navigation menu.

10. Notices

This interface provides information about current updates available in the Garuda Grid. For eg., if any cluster has any issues, we will mention it here. This will be updated regularly.

We strongly suggest that you check out the "Notices" link to know about any issues in job submission to any cluster, before doing the actual job submission, since the known issues will be mentioned in 'Notices'.

11. FAQs

This interface provides information about Frequently Asked Questions for the user.

12. Browsers and Versions that support Grid Portal

Linux Platform

1. Mozilla ver. 1.6 and above.
2. Firefox ver. 1.0.4 and above.

Windows Platform

1. Internet Explorer ver. 7.0 and above.
2. Firefox ver. 1.5.0.1 and above.

Solaris Platform

1. Netscape ver. 6.2.3 and above.

13. Types of MPI supported

1. Bangalore Linux Cluster(gg-blr)

MPI type : MPICH2 Version 1.0.6
MPI path : /opt/mpich2/gnu/

2. Bangalore AIX Cluster(tf73)

MPI type : IBM MPI
MPI path : /usr/bin/poe

3. Chennai Linux Cluster(gg-che)

MPI type : MPICH2 Version 1.0.6
MPI path : /opt/mpich2/gnu/

4. Hyderabad Linux Cluster(gg-hyd)

MPI type : MPICH2 Version 1.0.6
MPI path : /opt/mpich2/gnu/

5. IIT Delhi Linux Cluster(iitd)

MPI type : MPICH2 Version 1.0.3
MPI path : /usr/local/bin/

6. JNU Delhi Linux Cluster(gg-blr)

MPI type : ---
MPI path : ---

7. IIT Guwahati Linux Cluster(iitg)

MPI type : MPICH Version 1.2.6
MPI path : /usr/local/mpich-1.2.6/

Top