A solution looking for lots of problems: generic portals for science infrastructure

Authors:
Thomas D. Uram;Michael E. Papka;Mark Hereld;Michael Wilde
Affiliations:
Argonne National Laboratory, Argonne, IL;Argonne National Laboratory, Argonne, IL;Argonne National Laboratory, Argonne, IL;Argonne National Laboratory, Argonne, IL
Venue:
Proceedings of the 2011 TeraGrid Conference: Extreme Digital Discovery
Year:
2011

Citing 7
Cited 0

Virtual Network Computing

IEEE Internet Computing
The MyProxy online credential repository: Research Articles

Software—Practice & Experience - Grid Security
TeraGrid Science Gateways and Their Impact on Science

Computer
SimpleGrid toolkit: Enabling geosciences gateways to cyberinfrastructure

Computers & Geosciences
Parallel Scripting for Applications at the Petascale and Beyond

Computer
HUBzero: A Platform for Dissemination and Collaboration in Computational Science and Engineering

IEEE Design & Test
Accelerating science gateway development with Web 2.0 and Swift

Proceedings of the 2010 TeraGrid Conference

Quantified Score

Hi-index	0.00

Visualization

Abstract

Science gateways have dramatically simplified the work required by science communities to run their codes on TeraGrid resources. Gateway development typically spans the duration of a particular grant, with the first production runs occurring some months after the award and concluding near the end of the project. Scientists use gateways as a means to interface with large resources. Our gateway infrastructure facilitates this by hiding away the various details of the underlying resources and presents an intuitive way to interact with the resource. In this paper, we present our work on GPSI, a general-purpose science gateway infrastructure that can be easily customized to meet the needs of an application. This reduces the time to deployment and improves scientific productivity. Our contribution in this paper is two-fold: to elaborate our vision for a user-driven gateway infrastructure that includes components required by multiple science domains, thus aiding the speedy development of gateways, and presenting our experience in moving from our initial portal implementations to the current effort based on Python [15] and Django [16].