Pegasus development and improvement platform

Project Information

Discipline
Computer Science (401) 
Subdiscipline
11.04 Information Sciences and Systems 
Orientation
Research 
Abstract

This project is to give all members of the Pegasus team unified access to FutureGrid resources under one project umbrella. We believe that FutureGrid can be a valuable pool of resources to help us run automatic tests of our Pegasus software build process, and by virtue of being a cloud hosting VM, contribute to a wide variety of OS flavors to build binary bundles for. This is a repetitive operation likely over the lifetime of FutureGrid.

Intellectual Merit

a) Pegasus is a workflow system that can be used as part of the FG experiment management. We are developing a framework that will allow repeatable experiments b) Pegasus can run workflows on Grids

Broader Impacts

By using FG-provided resources, we expect to improve the Pegasus software stack, because it enables us to explore more difficult to test for problems.

Project Contact

Project Lead
Mats Rynge (rynge) 
Project Manager
Mats Rynge (rynge) 
Project Members
Karan Vahi, Weiwei Chen, Gideon Juve, Gaurang Mehta  

Resource Requirements

Hardware Systems
  • alamo (Dell optiplex at TACC)
  • foxtrot (IBM iDataPlex at UF)
  • hotel (IBM iDataPlex at U Chicago)
  • india (IBM iDataPlex at IU)
  • sierra (IBM iDataPlex at SDSC)
  • xray (Cray XM5 at IU)
  • bravo (large memory machine at IU)
 
Use of FutureGrid

I can see three essential use-cases: [1] bringing up a couple of small resource uniform VM for build-integrated testing. [2] bringing up a couple of medium-size development heterogeneous VMs for cross-flavor packaging. [3] bringing up a large number of uniform VM for domain science experiment runs. However, these will explore the computer-science, i.e. workflow, side of the experiments, disregarding any domain science results.

Scale of Use

About a dozen of resources for a short duration. Some burstiness possible for occasional experiments, though we prefer to point our users to FutureGrid and have them apply for their own projects. However, if problems during such experiments occur, it is simpler for us to have access to our own project, and thus FutureGrid resources, in order to debug problems or test use-cases. We might be able to help FutureGrid with scalability testing.

Project Timeline

Submitted
02/09/2012 - 18:05 
»