Bug 754563

Summary: Chapter 19 (dagman) Comments
Product: Red Hat Enterprise MRG Reporter: Robert Rati <rrati>
Component: Grid_User_GuideAssignee: Alison Young <alyoung>
Status: CLOSED CURRENTRELEASE QA Contact: Tomas Rusnak <trusnak>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 2.0CC: eerlands, lbrindle, matt, mkudlej, trusnak
Target Milestone: 2.1   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-01-26 19:22:13 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Robert Rati 2011-11-16 20:44:18 UTC 
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:
Comment 6 Alison Young 2011-11-29 01:03:50 UTC 
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>
Comment 7 Tomas Rusnak 2011-11-30 14:06:22 UTC 
Changes confirmed in Chapter 19. DAGMan.

Revision 1-31	Tue Nov 29 2011	Alison Young
BZ#754563 - minor updates

>>> VERIFIED
Comment 8 Lana Brindley 2012-01-26 19:22:13 UTC 
This book is now available on redhat.com/docs. Please raise a new bug if you spot any issues.

Thanks,
LKB