[Swift-commit] r4433 - www/cookbook
ketan at ci.uchicago.edu
ketan at ci.uchicago.edu
Wed Apr 27 23:34:03 CDT 2011
Author: ketan
Date: 2011-04-27 23:34:03 -0500 (Wed, 27 Apr 2011)
New Revision: 4433
Modified:
www/cookbook/cookbook-asciidoc.html
www/cookbook/cookbook-asciidoc.txt
Log:
Modified: www/cookbook/cookbook-asciidoc.html
===================================================================
--- www/cookbook/cookbook-asciidoc.html 2011-04-27 18:12:25 UTC (rev 4432)
+++ www/cookbook/cookbook-asciidoc.html 2011-04-28 04:34:03 UTC (rev 4433)
@@ -583,7 +583,8 @@
<div class="sectionbody">
<div class="paragraph"><p>This cookbook covers various recipes involving setting up and running Swift under diverse
configurations based on the application requirements and the underlying
-infrastructures. The Swift system comprises of SwiftScript language and the Swift runtime system. For
+infrastructures. The Swift system comprises of SwiftScript language and the
+Swift runtime system. For
introductory material, consult the Swift tutorial found
<a href="http://www.ci.uchicago.edu/swift/guides/tutorial.php">here</a>.</p></div>
<div class="paragraph"><p>Swift is a data-oriented coarse grained parallel scripting language that supports
@@ -608,7 +609,8 @@
<div class="sect3">
<h4 id="_prerequisites">2.1.1. Prerequisites</h4>
<div class="paragraph"><div class="title">Check your Java</div><p>Swift is a Java application. Make sure you are running Java version 5 or higher. You
-can make sure you have Java in your $PATH (or $HOME/.soft file depending upon your environment)</p></div>
+can make sure you have Java in your $PATH (or $HOME/.soft file depending upon
+your environment)</p></div>
<div class="paragraph"><p>Following are the possible ways to detect and run Java:</p></div>
<div class="listingblock">
<div class="content">
@@ -622,13 +624,15 @@
Java(TM) SE Runtime Environment (build 1.6.0_11-b03)
Java HotSpot(TM) 64-Bit Server VM (build 11.0-b16, mixed mode)</tt></pre>
</div></div>
-<div class="paragraph"><div class="title">Setting up to run Swift</div><p>This is simple. We will be using a pre-compiled version of Swift that can be downloaded from the following location:</p></div>
+<div class="paragraph"><div class="title">Setting up to run Swift</div><p>This is simple. We will be using a pre-compiled version of Swift that can be
+downloaded from the following location:</p></div>
<div class="listingblock">
<div class="content">
<pre><tt>http://www.ci.uchicago.edu/swift/packages/swift-0.92.1.tar.gz</tt></pre>
</div></div>
-<div class="paragraph"><p>The examples were tested with Java version 1.6. Make sure you do not already have Swift in your PATH. If you do, remove it,
-or remove any +swift or @swift lines from your $HOME/.soft or $HOME/.bash_profile file. Then do:</p></div>
+<div class="paragraph"><p>The examples were tested with Java version 1.6. Make sure you do not already
+have Swift in your PATH. If you do, remove it, or remove any +swift or @swift
+lines from your $HOME/.soft or $HOME/.bash_profile file. Then do:</p></div>
<div class="listingblock">
<div class="content">
<pre><tt>PATH=$PATH:/home/wilde/bigdata/swift/bin</tt></pre>
@@ -638,8 +642,8 @@
<td class="icon">
<div class="title">Warning</div>
</td>
-<td class="content">Do NOT set SWIFT_HOME or CLASSPATH in your environment unless you fully
-understand how these will affect Swift’s execution.</td>
+<td class="content">Do NOT set SWIFT_HOME or CLASSPATH in your environment unless you
+fully understand how these will affect Swift’s execution.</td>
</tr></table>
</div>
</div>
@@ -652,9 +656,9 @@
<td class="icon">
<div class="title">Note</div>
</td>
-<td class="content">The environment will be different when using Swift from prebuilt
-distribution and trunk. To execute your Swift script on a login host (or "localhost") use the
-following command:</td>
+<td class="content">The environment will be different when using Swift from prebuilt distribution
+and trunk. To execute your Swift script on a login host (or "localhost") use
+the following command:</td>
</tr></table>
</div>
<div class="listingblock">
@@ -1040,16 +1044,22 @@
</div>
<div class="sect2">
<h3 id="_osg">3.3. OSG</h3>
+<div class="paragraph"><p>This section describes how to get Swift running on the OSG Grid. We will use a
+manual coaster setup to get Swift running on OSG.</p></div>
+<div class="paragraph"><div class="title">Coaster setup on OSG</div><p>The following figure shows an abstract scheme for the manual coasters setup on
+OSG.</p></div>
<div class="imageblock">
<div class="content">
<img src="figures/coaster_setup.png" alt="Coaster setup" />
</div>
-<div class="title">Figure 1. Coaster setup on OSG</div>
</div>
+<div class="paragraph"><p>In the following steps, we will go through the process of manually setting</p></div>
</div>
<div class="sect2">
<h3 id="_bionimbus">3.4. Bionimbus</h3>
-<div class="paragraph"><p>This section explains a step by step procedure on getting Swift running on the Bionimbus cloud. We will use the <em>manual</em> <em>coasters</em> configuration on the Bionimbus cloud.</p></div>
+<div class="paragraph"><p>This section explains a step by step procedure on getting Swift running on the
+Bionimbus cloud. We will use the <em>manual</em> <em>coasters</em> configuration on the
+Bionimbus cloud.</p></div>
<div class="paragraph"><p><strong>step1.</strong> Connect to the gateway (ssh gatewayx.lac.uic.edu)</p></div>
<div class="paragraph"><p><strong>step2.</strong> Start a virtual machine (euca-run-instances -n 1 -t m1.small
emi-17EB1170)</p></div>
@@ -1182,11 +1192,11 @@
<div class="olist arabic"><ol class="arabic">
<li>
<p>
-One of the main reason that one would initially deviate from coaster defaults
-into more complex pool entries is to force jobs to fit into some site-imposed
-constraint. For instance a typical submission to the experimental queue requires a user to
-request upto 3 nodes for under 1 hour. This setup could be achieved with a
-careful tuning of coaters parameters.
+One of the main reason that one would initially deviate from coaster
+defaults into more complex pool entries is to force jobs to fit into some
+site-imposed constraint. For instance a typical submission to the experimental
+queue requires a user to request upto 3 nodes for under 1 hour. This setup
+could be achieved with a careful tuning of coaters parameters.
</p>
</li>
</ol></div>
@@ -1236,7 +1246,8 @@
<div class="sect1">
<h2 id="_log_processing">6. Log Processing</h2>
<div class="sectionbody">
-<div class="paragraph"><p>To properly generate log plots, you must enable VDL/Karajan logging. Make sure log4.properties contains:</p></div>
+<div class="paragraph"><p>To properly generate log plots, you must enable VDL/Karajan logging. Make sure
+log4.properties contains:</p></div>
<div class="listingblock">
<div class="content">
<pre><tt>log4j.logger.swift=DEBUG
@@ -1368,7 +1379,7 @@
<div id="footer">
<div id="footer-text">
Version 0.92<br />
-Last updated 2011-04-27 11:09:55 CDT
+Last updated 2011-04-27 23:33:37 CDT
</div>
</div>
</body>
Modified: www/cookbook/cookbook-asciidoc.txt
===================================================================
--- www/cookbook/cookbook-asciidoc.txt 2011-04-27 18:12:25 UTC (rev 4432)
+++ www/cookbook/cookbook-asciidoc.txt 2011-04-28 04:34:03 UTC (rev 4433)
@@ -10,7 +10,8 @@
--------
This cookbook covers various recipes involving setting up and running Swift under diverse
configurations based on the application requirements and the underlying
-infrastructures. The Swift system comprises of SwiftScript language and the Swift runtime system. For
+infrastructures. The Swift system comprises of SwiftScript language and the
+Swift runtime system. For
introductory material, consult the Swift tutorial found
link:http://www.ci.uchicago.edu/swift/guides/tutorial.php[here].
@@ -40,7 +41,8 @@
^^^^^^^^^^^^^^
.Check your Java
Swift is a Java application. Make sure you are running Java version 5 or higher. You
-can make sure you have Java in your $PATH (or $HOME/.soft file depending upon your environment)
+can make sure you have Java in your $PATH (or $HOME/.soft file depending upon
+your environment)
Following are the possible ways to detect and run Java:
@@ -57,29 +59,31 @@
----
.Setting up to run Swift
-This is simple. We will be using a pre-compiled version of Swift that can be downloaded from the following location:
+This is simple. We will be using a pre-compiled version of Swift that can be
+downloaded from the following location:
----
http://www.ci.uchicago.edu/swift/packages/swift-0.92.1.tar.gz
----
-The examples were tested with Java version 1.6. Make sure you do not already have Swift in your PATH. If you do, remove it,
-or remove any +swift or @swift lines from your $HOME/.soft or $HOME/.bash_profile file. Then do:
+The examples were tested with Java version 1.6. Make sure you do not already
+have Swift in your PATH. If you do, remove it, or remove any +swift or @swift
+lines from your $HOME/.soft or $HOME/.bash_profile file. Then do:
----
PATH=$PATH:/home/wilde/bigdata/swift/bin
----
-WARNING: Do NOT set SWIFT_HOME or CLASSPATH in your environment unless you fully
-understand how these will affect Swift's execution.
+WARNING: Do NOT set SWIFT_HOME or CLASSPATH in your environment unless you
+fully understand how these will affect Swift's execution.
Environment Setup
~~~~~~~~~~~~~~~~~
Setting up the environment
[NOTE]
-The environment will be different when using Swift from prebuilt
-distribution and trunk. To execute your Swift script on a login host (or "localhost") use the
-following command:
+The environment will be different when using Swift from prebuilt distribution
+and trunk. To execute your Swift script on a login host (or "localhost") use
+the following command:
----
swift -tc.file tc somescript.swift
@@ -446,15 +450,27 @@
</config>
source~~~~
+
OSG
~~~
+This section describes how to get Swift running on the OSG Grid. We will use a
+manual coaster setup to get Swift running on OSG.
+
.Coaster setup on OSG
+The following figure shows an abstract scheme for the manual coasters setup on
+OSG.
+
image::figures/coaster_setup.png[Coaster setup]
+
+In the following steps, we will go through the process of manually setting
//Swift on OSG
//
+
Bionimbus
~~~~~~~~~
-This section explains a step by step procedure on getting Swift running on the Bionimbus cloud. We will use the _manual_ _coasters_ configuration on the Bionimbus cloud.
+This section explains a step by step procedure on getting Swift running on the
+Bionimbus cloud. We will use the _manual_ _coasters_ configuration on the
+Bionimbus cloud.
**step1.** Connect to the gateway (ssh gatewayx.lac.uic.edu)
@@ -624,11 +640,11 @@
//Coasters for advanced users. Getting your hands dirty.
-. One of the main reason that one would initially deviate from coaster defaults
-into more complex pool entries is to force jobs to fit into some site-imposed
-constraint. For instance a typical submission to the experimental queue requires a user to
-request upto 3 nodes for under 1 hour. This setup could be achieved with a
-careful tuning of coaters parameters.
+. One of the main reason that one would initially deviate from coaster
+defaults into more complex pool entries is to force jobs to fit into some
+site-imposed constraint. For instance a typical submission to the experimental
+queue requires a user to request upto 3 nodes for under 1 hour. This setup
+could be achieved with a careful tuning of coaters parameters.
//How to run Swift under different Coasters configurations
//~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -674,7 +690,8 @@
Log Processing
---------------
-To properly generate log plots, you must enable VDL/Karajan logging. Make sure log4.properties contains:
+To properly generate log plots, you must enable VDL/Karajan logging. Make sure
+log4.properties contains:
----
log4j.logger.swift=DEBUG
log4j.logger.org.globus.cog.abstraction.coaster.service.job.manager.Cpu=DEBUG
More information about the Swift-commit
mailing list