1 / 9

Integrated Genomics Applications Pipeline (iGAP) on the GRID

Integrated Genomics Applications Pipeline (iGAP) on the GRID. iGAP – Current Architecture. iGAP – Current Architecture. Input Sequences are Spilt at the Client Catered for a Cluster Environment with a Local Scheduler Assumes Database and Input Sequences to be Shared among all Nodes (NFS)

noah
Download Presentation

Integrated Genomics Applications Pipeline (iGAP) on the GRID

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Integrated Genomics Applications Pipeline (iGAP) on the GRID

  2. iGAP – Current Architecture

  3. iGAP – Current Architecture • Input Sequences are Spilt at the Client • Catered for a Cluster Environment with a Local Scheduler • Assumes Database and Input Sequences to be Shared among all Nodes (NFS) • Job Monitoring not Implemented

  4. Porting iGAP to the Grid – Tasks Involved • Security and Access to Computing Resources • A Method of Publishing Available Grid Nodes • Sending Input Sequences to the Nodes • Scheduling Jobs Among Nodes • Location of Binary and Databases • Retrieving Output Files • Monitoring Job Status

  5. iGAP – The Grid Architecture

  6. iGAP – Job Submission • Authentication – Managed through Globus • Resources – Available grid nodes and their resources are published in a text file. • Scheduling – Weighted Round Robin • Input – Input files are copied to nodes using globus-url-copy • Execution – RSL Generated on client and submitted to Globus. • Log – Database updated with job information

  7. iGAP – Job Monitoring • Retrieval – Search table for active jobs for the user • Status – Check status of these jobs with Globus • If job is complete, retrieve output files • Update status of the job in the database • Back to Step 1

  8. Shortcomings • Current resource discovery mechanism inadequate • Shared file-systems within clusters in the Grid required • Globus job status reporting inadequate • Prior knowledge of location of database and binary

  9. Future Implementation • Integration with the data-grid using SRB • Publishing database and binary location in the MDS • Automated re-submission of “failed” jobs • User notification on job completion

More Related