[Swift-commit] r6692 - SwiftTutorials/uc3

[davidk at ci.uchicago.edu]

Author: davidk
Date: 2013-07-30 13:53:17 -0500 (Tue, 30 Jul 2013)
New Revision: 6692

Modified:
   SwiftTutorials/uc3/README
Log:
Part 10 doc, note about re-running setup.sh on reconnecting


Modified: SwiftTutorials/uc3/README
===================================================================
--- SwiftTutorials/uc3/README	2013-07-30 18:38:04 UTC (rev 6691)
+++ SwiftTutorials/uc3/README	2013-07-30 18:53:17 UTC (rev 6692)
@@ -27,6 +27,8 @@
 $ swift -version    # verify that Swift 0.94 is in your $PATH and functional
 -----
 
+NOTE: If you disconnect from the machine, you will need to re-run source setup.sh.
+
 Overview of the applications
 ----------------------------
 There are two shell scripts included that act as a mock science application: 
@@ -437,3 +439,34 @@
 $ cd part09
 $ swift p9.swift
 ----
+
+part10
+~~~~~~
+p10.swift is exactly the same as p9.swift. Instead of the swift script,
+take a look at the sites.xml configuration file.
+The sites.xml file determines where swift runs its job at. Here the
+line with the condor requirement to select nodes from the UC3 seeder
+cluster is left un-commented to select that site.
+
+-----
+<profile namespace="globus" key="condor.Requirements">regexp("uc3-c*", Machine)</profile>
+-----
+
+The condor requirements for selecting nodes from UC3 seeder, ITS
+Virtualization lab, Open Science Grid and Atlas Midwest Tier 2 (at UC,
+IU, UIUC) are present in the sites.xml file.
+To choose any of these sites, simply uncomment the requirement line
+for the target system and run the swift script as:
+
+To run:
+----
+$ cd part10
+$ swift p10.swift
+----
+
+Once the script completes, run the script find_host.sh to find where
+the jobs were run.
+
+-----
+./find_host.sh
+-----