Research Article

What makes workflows work in an opportunistic environment?

  1. Ewa Deelman1,*,
  2. Tevfik Kosar2,
  3. Carl Kesselman1,
  4. Miron Livny2

Article first published online: 13 DEC 2005

DOI: 10.1002/cpe.1001

Issue

Concurrency and Computation: Practice and Experience

Concurrency and Computation: Practice and Experience

Special Issue: Workflow in Grid Systems

Volume 18, Issue 10, pages 1187–1199, 25 August 2006

Additional Information

How to Cite

Deelman, E., Kosar, T., Kesselman, C. and Livny, M. (2006), What makes workflows work in an opportunistic environment?. Concurrency Computat.: Pract. Exper., 18: 1187–1199. doi: 10.1002/cpe.1001

Author Information

  1. 1

    USC Information Science Institute, 4676 Admiralty Way, Suite 1001, Marina Del Rey, CA 90292, U.S.A.

  2. 2

    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.

Publication History

  1. Issue published online: 19 JUL 2006
  2. Article first published online: 13 DEC 2005
  3. Manuscript Accepted: 27 APR 2005
  4. Manuscript Revised: 15 MAR 2005
  5. Manuscript Received: 1 JUN 2004

SEARCH

SEARCH BY CITATION

ARTICLE TOOLS

Get PDF (384K)

Keywords:

  • Grid;
  • workflow management;
  • workflow mapping;
  • advanced planning;
  • deferred planning;
  • just-in-time planning;
  • workflow delegation;
  • data placement;
  • scheduling;
  • Pegasus;
  • Chimera;
  • DAGMan;
  • Condor;
  • Stork

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.

Get PDF (384K)