What makes workflows work in an opportunistic environment?: Research Articles

Authors:
Ewa Deelman;Tevfik Kosar;Carl Kesselman;Miron Livny
Affiliations:
USC Information Science Institute, 4676 Admiralty Way, Suite 1001, Marina Del Rey, CA 90292, U.S.A.;Computer Sciences Department, University of Wisconsin–Madison, 1210 West Dayton Street, Madison, WI 53719, U.S.A.;USC Information Science Institute, 4676 Admiralty Way, Suite 1001, Marina Del Rey, CA 90292, U.S.A.;Computer Sciences Department, University of Wisconsin–Madison, 1210 West Dayton Street, Madison, WI 53719, U.S.A.
Venue:
Concurrency and Computation: Practice & Experience - Workflow in Grid Systems
Year:
2006

Citing 0
Cited 5

Dynamic service selection in workflows using performance data

Scientific Programming - Dynamic Computational Workflows: Discovery, Optimization and Scheduling
Data placement for scientific applications in distributed environments

GRID '07 Proceedings of the 8th IEEE/ACM International Conference on Grid Computing
Evolving toward the perfect schedule: co-scheduling job assignments and data replication in wide-area systems using a genetic algorithm

JSSPP'05 Proceedings of the 11th international conference on Job Scheduling Strategies for Parallel Processing
Turbine: a distributed-memory dataflow engine for extreme-scale many-task applications

Proceedings of the 1st ACM SIGMOD Workshop on Scalable Workflow Execution Engines and Technologies
Turbine: A Distributed-memory Dataflow Engine for High Performance Many-task Applications

Fundamenta Informaticae - Scalable Workflow Enactment Engines and Technology

Quantified Score

Hi-index	0.00

Visualization

Abstract

In this paper, we examine the issues of workflow mapping and execution in opportunistic environments such as the Grid. As applications become ever more complex, the process of choosing the appropriate resources and successfully executing the application components becomes ever more difficult. This may include extension or reduction of the initial workflow mapping as necessary for the actual execution. In this paper, we focus on the interplay between a workflow-mapping component that plans the high-level resource assignments and the workflow executor that oversees the component execution. We concentrate particularly on issues of data management and we draw from the experiences with mapping and execution systems: Pegasus, DAGMan and Stork. Copyright © 2005 John Wiley & Sons, Ltd.