[Swift-commit] r6217 - trunk/docs/userguide

[ketan at ci.uchicago.edu]

Author: ketan
Date: 2013-02-02 19:33:40 -0600 (Sat, 02 Feb 2013)
New Revision: 6217

Modified:
   trunk/docs/userguide/coasters
Log:
starting to fix coasters desc

Modified: trunk/docs/userguide/coasters
===================================================================
--- trunk/docs/userguide/coasters	2013-02-03 01:20:52 UTC (rev 6216)
+++ trunk/docs/userguide/coasters	2013-02-03 01:33:40 UTC (rev 6217)
@@ -7,17 +7,17 @@
 order of a few kilobytes) for which other grid protocols such as GRAM
 and GridFTP are poorly suited.
 
-The coaster mechanism submits a head job using some other execution
+The coaster mechanism submits a pilot job using some other execution
 mechanism such as GRAM, and for each worker node that will be used in a
 remote cluster, it submits a worker job, again using some other
 execution mechanism such as GRAM. Details on the design of the coaster
 mechanism can be found here. <http://wiki.cogkit.org/wiki/Coasters>
 
-The head job manages file transfers and the dispatch of execution jobs
+The pilot job manages file transfers and the dispatch of execution jobs
 to workers. Much of the overhead associated with other grid protocols
 (such as authentication and authorization, and allocation of worker
 nodes by the site's local resource manager) is reduced, because that
-overhead is associated with the allocation of a coaster head or coaster
+overhead is associated with the allocation of a coaster pilot or coaster
 worker, rather than with every Swift-level procedure invocation;
 potentially hundreds or thousands of Swift-level procedure invocations
 can be run through a single worker.