Abstracts for online demonstrations must provide a summary of the demo content. Places for demos are limited and this summary will be used as part of the selection procedure. Please include the visual impact of the demo and highlight any specific requirements (e.g. network connection). In general, a successful demo is expected to have some supporting material (poster) and be capable of running on a single screen or projector.
After a short introduction (supported by some slides) is given, a live demo of the chosen interface will be performed. For this demo, a grid infrastructure will be set up, involving a GridWay instance located at UCM giving access to some resources from EGEE (and possibly from TeraGrid and OSG), a GridGateWay wrapping that GridWay instance, a SGE cluster with a transfer queue to GridWay configured, an Excel spreadsheet submitting tasks to GridWay and some DRMAA applications using both GridWay and SGE depending on the DRMAA library they are dynamically linked. This infrastructure will accessed using SSH, therefore a wired network connection would be appreciated.
Describe the added value of the Grid for the scientific/technical activity you (plan to) do on the Grid. This should include the scale of the activity and of the potential user community and the relevance for other scientific or business applications
GridWay interfaces for on-demand access to grid infrastructures allow end-users to obtain computing power where needed. For instance, computing resources can be used on-demand by overloaded LRMS (like SGE), ISV applications using DRMAA (like gridMathematica), Excel spreadsheets (e.g. to immediately visualize results) or tools using standard Globus CLIs and APIs (like a workflow engine or a computing portal).
Moreover, since GridWay is able to simultaneously harness resources from the most important grid infrastructures (EGEE, TeraGrid, OSG…), both directly and through GridGateWays, end-users don’t need to worry about the underlying resources and middleware their jobs are using.
Describe the scientific/technical community and the scientific/technical activity using (planning to use) the EGEE infrastructure. A high-level description is needed (neither a detailed specialist report nor a list of references).
The GridWay Metascheduler is a Globus project that performs job execution management and resource brokering, allowing unattended, reliable, and efficient execution of jobs, job arrays, and workflows on heterogeneous and dynamic Grids. GridWay is completely functional on EGEE, being able to interface with its computing, file transfer and information services. The demonstration will mainly show the interfaces provided by GridWay allowing on-demand access to EGEE resources.
Report on the experience (or the proposed activity). It would be very important to mention key services which are essential for the success of your activity on the EGEE infrastructure.
Currently, there are four interfaces in GridWay that allow on-demand access to grid resources:
- "GridGateWay" encapsulates a grid behind standard Globus services, mainly GridFTP, MDS and GRAM (the latter two, both WS and pre-WS), enabling any application using Globus services to access a whole grid infrastructure as if it were a single Globus resource.
- "SGE Transfer Queue to Globus and GridWay" allows the forwarding of jobs from SGE to Globus and GridWay in a transparent way under some load conditions.
- "Excel plug-in for GridWay" allows Excel spreadsheets to divert compute-demanding tasks to grid resources managed by GridWay.
- "C and Java DRMAA bindings for GridWay" enable developers and ISVs to write portable applications using DRM systems.
The above interfaces are deployed on the client side, not needing the deployment of central services. Moreover, GridWay can be currently deployed on an EGEE UI.