[Swift-commit] r3210 - trunk/etc

noreply at svn.ci.uchicago.edu noreply at svn.ci.uchicago.edu
Sun Jan 24 17:56:14 CST 2010


Author: hategan
Date: 2010-01-24 17:56:13 -0600 (Sun, 24 Jan 2010)
New Revision: 3210

Modified:
   trunk/etc/swift.properties
Log:
added more explanation on provider staging

Modified: trunk/etc/swift.properties
===================================================================
--- trunk/etc/swift.properties	2010-01-24 23:55:28 UTC (rev 3209)
+++ trunk/etc/swift.properties	2010-01-24 23:56:13 UTC (rev 3210)
@@ -330,8 +330,23 @@
 # Controls whether file staging is done by swift or by the execution 
 # provider. If set to false, the standard swift staging mechanism is
 # used. If set to true, swift does not stage files. Instead, the 
-# execution provider is instructed to stage files in and out. 
-# Provider staging is experimental and only working with a limited 
-# number of providers (local and coaster).
+# execution provider is instructed to stage files in and out.
+# 
+# Provider staging is experimental.
+#
+# When enabled, and when coasters are used as an execution provider,
+# a staging mechanism can be selected for each site
+# using the swift:stagingMethod site profile in sites.xml. The
+# following is a list of accepted mechanisms:
+#
+# * file:  Staging is done from a filesystem accessible to the 
+#          coaster service (typically running on the head node) 
+# * proxy: Staging is done from a filesystem accessible to the
+#          client machine that swift is running on, and is proxied
+#          through the coaster service
+# * sfs:   (short for "shared filesystem") Staging is done by
+#          copying files to and from a filesystem accessible
+#          by the compute node (such as an NFS or GPFS mount).   
+ 
 
 use.provider.staging=false
\ No newline at end of file




More information about the Swift-commit mailing list