[Swift-commit] r6500 - branches/release-0.94/docs/siteguide

[davidk at ci.uchicago.edu]

Author: davidk
Date: 2013-05-02 16:49:35 -0500 (Thu, 02 May 2013)
New Revision: 6500

Added:
   branches/release-0.94/docs/siteguide/midway
Modified:
   branches/release-0.94/docs/siteguide/siteguide.txt
Log:
Add midway to 0.94 siteguide


Added: branches/release-0.94/docs/siteguide/midway
===================================================================
--- branches/release-0.94/docs/siteguide/midway	                        (rev 0)
+++ branches/release-0.94/docs/siteguide/midway	2013-05-02 21:49:35 UTC (rev 6500)
@@ -0,0 +1,92 @@
+Midway (x86 cluster)
+--------------------
+Midway is a cluster maintained by the Research Computing Center
+at the University of Chicago. Midway uses Slurm to handle job
+scheduling. For more details about Midway, and to request
+an account, visit http://rcc.uchicago.edu.
+
+Connecting to a login node
+~~~~~~~~~~~~~~~~~~~~~~~~~~
+Once you have access to Midway, connect to 
+a Midway login node.
+
+-----
+$ ssh userid at midway.rcc.uchicago.edu
+-----
+
+Loading Swift
+~~~~~~~~~~~~~
+Swift is available on Midway as a module. To load the
+Swift, run:
+
+-----
+$ module load swift
+-----
+
+Example sites.xml
+~~~~~~~~~~~~~~~~~
+Below is an example that uses two of the queues available
+on Midway, sandyb and westmere. Be sure to adjust walltime,
+work directory, and other options as needed.
+
+-----
+<config>
+  <pool handle="midway-sandyb">
+    <execution provider="coaster" jobmanager="local:slurm"/>
+    <profile namespace="globus" key="jobsPerNode">16</profile>
+    <profile namespace="globus" key="maxWalltime">00:05:00</profile>
+    <profile namespace="globus" key="highOverAllocation">100</profile>
+    <profile namespace="globus" key="lowOverAllocation">100</profile>
+    <profile namespace="globus" key="queue">sandyb</profile>
+    <profile namespace="karajan" key="initialScore">10000</profile>
+    <filesystem provider="local"/>
+    <workdirectory>/scratch/midway/{env.USER}/work</workdirectory>
+  </pool>
+
+  <pool handle="midway-westmere">
+    <execution provider="coaster" jobmanager="local:slurm"/>
+    <profile namespace="globus" key="jobsPerNode">12</profile>
+    <profile namespace="globus" key="maxWalltime">00:05:00</profile>
+    <profile namespace="globus" key="highOverAllocation">100</profile>
+    <profile namespace="globus" key="lowOverAllocation">100</profile>
+    <profile namespace="globus" key="queue">westmere</profile>
+    <profile namespace="karajan" key="initialScore">10000</profile>
+    <filesystem provider="local"/>
+    <workdirectory>/scratch/midway/{env.USER}/work</workdirectory>
+  </pool>
+</config>
+-----
+
+Example sites.xml for use with MPI
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+Below is an example sites.xml that is suitable for running with MPI.
+Jobtype must be set to single. The value you set for ppn
+will determine the number of cores/slots your application uses per node. 
+The value of count will set the number of nodes to request. The example
+below requests 2 nodes with 12 slots per node.
+
+-----
+<config>
+  <pool handle="midway-westmere">
+    <execution provider="coaster" jobmanager="local:slurm"/>
+    <profile namespace="globus" key="jobsPerNode">1</profile>
+    <profile namespace="globus" key="ppn">12</profile>
+    <profile namespace="globus" key="maxWalltime">_WALLTIME_</profile>
+    <profile namespace="globus" key="highOverAllocation">100</profile>
+    <profile namespace="globus" key="lowOverAllocation">100</profile>
+    <profile namespace="globus" key="queue">westmere</profile>
+    <profile namespace="karajan" key="initialScore">10000</profile>
+    <profile namespace="globus" key="jobtype">single</profile>
+    <profile namespace="globus" key="count">2</profile>
+    <filesystem provider="local"/>
+    <workdirectory>/scratch/midway/{env.USER}/work</workdirectory>
+  </pool>
+</config>
+-----
+
+Various tips for running MPI jobs
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+* You'll need to load an MPI module. Run "module load openmpi" to add to your path.
+* The app that Swift runs should be a wrapper script that invokes your
+  MPI application by running "mpiexec /path/to/yourMPIApp"
+

Modified: branches/release-0.94/docs/siteguide/siteguide.txt
===================================================================
--- branches/release-0.94/docs/siteguide/siteguide.txt	2013-05-02 21:06:19 UTC (rev 6499)
+++ branches/release-0.94/docs/siteguide/siteguide.txt	2013-05-02 21:49:35 UTC (rev 6500)
@@ -22,6 +22,8 @@
 
 include::mcs[]
 
+include::midway[]
+
 include::stampede[]
 
 include::uc3[]