Hide Forgot
Description of problem: From Erik: *) "orderly set of dependencies" --> "partially ordered set of dependencies" *) "DAGMan (DAG manager) performs workflow" --> "The Grid Dag Manager (DAGMan) performs workflow" *) "Tasks cannot loop" --> "Task dependencies cannot form cycles (i.e. cannot loop)" *) This sentence seems a little misleading: "DAGMan jobs are submitted to the condor_schedd in the same way as ordinary MRG Grid jobs." -- The individual jobs themselves are treated the same, but the submission of individual jobs is managed by the dagman, and the submission of the dag itself is via condor_submit_dag. *) I might remove this paragraph: "DAGMan submit description files act as pointers for the individual job submit description files, and instruct MRG Grid on the order to run the jobs. In the DAGMan submit description file, job dependencies are expressed as PARENT-CHILD relationships. The basic configuration for DAGMan jobs usually resembles a diamond." Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Change made in revision 1-31 Doc-stage: http://documentation-stage.bne.redhat.com/docs/en-US/Red_Hat_Enterprise_MRG/2/html-single/Grid_User_Guide/index.html#chap-Grid_User_Guide-DAGMan Code snippets/comments: <para> &GRID; allows jobs to be submitted and executed in parallel. However, some large-scale computing applications require individual jobs to be processed as a partially ordered set of dependencies. For example in some simulations of financial instrument models, or complex 3D modeling. </para> <para> The &GRID; <firstterm>DAG manager</firstterm> (DAGman) performs workflow management within &GRID;. Individual jobs are treated as tasks, each job may have zero or more dependencies. The DAGMan permits jobs to run when it determines that all dependencies have been completed successfully. The output of a job can be used as the input for the next job. </para> <para> DAGMan submit description files act as pointers for the individual job submit description files, and instruct &GRID; on the order to run the jobs. In the DAGMan submit description file, job dependencies are expressed as PARENT-CHILD relationships. The basic configuration for DAGMan jobs often resembles a diamond. </para>
Changes confirmed in Chapter 19. DAGMan. Revision 1-31 Tue Nov 29 2011 Alison Young BZ#754563 - minor updates >>> VERIFIED
This book is now available on redhat.com/docs. Please raise a new bug if you spot any issues. Thanks, LKB