<div dir="ltr"><div>I agree, I don't think the names give a good idea of what they're about. I also feel like it's difficult to explain some of these without diagrams.<br><br></div>- Tim<br></div><div class="gmail_extra">
<br><br><div class="gmail_quote">On Mon, Aug 11, 2014 at 3:34 PM, Yadu Nand <span dir="ltr"><<a href="mailto:yadudoc1729@gmail.com" target="_blank">yadudoc1729@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">Hi Everyone,</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">
In the current conventions for staging, we are calling what used to be proxy staging method as local, which I think is counter-intuitive, when local staging is actually staging to remote sites.</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">
<br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">Staging method "swift" does not give any idea about what it actually does either. </div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">
<br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">I'm pasting the staging methods table from the documentation below.</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">
<br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><table rules="all" frame="border" style="border:3px solid rgb(82,123,189);color:rgb(0,0,0);font-family:Georgia,serif;font-size:medium" cellpadding="4" cellspacing="0" width="100%">
<thead style="font-family:Arial,Helvetica,sans-serif;font-weight:bold;color:rgb(82,123,189)"><tr><th align="left" valign="top">Staging Method</th><th align="left" valign="top">Description</th></tr></thead><tbody><tr><td align="left" valign="top">
<p style="margin-top:0px;margin-bottom:0.5em"><tt style="font-size:inherit;color:navy">swift</tt></p></td><td align="left" valign="top"><p style="margin-top:0px;margin-bottom:0.5em">This method instructs Swift to use a filesystem provider to direct all necessary staging operations from the Swift client-side to the cluster head node. If this method is used, the <tt style="font-size:inherit;color:navy">workDirectory</tt> must point to a head node path that is on a shared file system accessible by the compute nodes.</p>
</td></tr><tr><td align="left" valign="top"><p style="margin-top:0px;margin-bottom:0.5em"><tt style="font-size:inherit;color:navy">wrapper</tt></p></td><td align="left" valign="top"><p style="margin-top:0px;margin-bottom:0.5em">
File staging is done by the Swift application wrapper</p></td></tr><tr><td align="left" valign="top"><p style="margin-top:0px;margin-bottom:0.5em"><tt style="font-size:inherit;color:navy">local</tt></p></td><td align="left" valign="top">
<p style="margin-top:0px;margin-bottom:0.5em">Used to indicate that files should be staged in/out from/to the site on which Swift is running. In the case of Swift Coasters, the system proxies the tranfers between client side and compute nodes through the Coaster Service.</p>
</td></tr><tr><td align="left" valign="top"><p style="margin-top:0px;margin-bottom:0.5em"><tt style="font-size:inherit;color:navy">service-local</tt></p></td><td align="left" valign="top"><p style="margin-top:0px;margin-bottom:0.5em">
This method instructs the execution mechanism provider to stage input and output files from the remote site where the execution service is located. For example, if a Coaster Service is started on the login node of a cluster, the Coaster Service will perform the staging from a file system on the login node to the compute node and back.</p>
</td></tr><tr><td align="left" valign="top"><p style="margin-top:0px;margin-bottom:0.5em"><tt style="font-size:inherit;color:navy">shared-fs</tt></p></td><td align="left" valign="top"><p style="margin-top:0px;margin-bottom:0.5em">
This method is used by Coasters to implement a simple staging mechanism in which files are accessed using a shared filesystem that is accessible by compute nodes</p></td></tr></tbody></table></div><div><br></div><div><br>
</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">Thanks,</div><div dir="ltr">Yadu Nand B<div><br></div></div>
</div>
<br>_______________________________________________<br>
Swift-devel mailing list<br>
<a href="mailto:Swift-devel@ci.uchicago.edu">Swift-devel@ci.uchicago.edu</a><br>
<a href="https://lists.ci.uchicago.edu/cgi-bin/mailman/listinfo/swift-devel" target="_blank">https://lists.ci.uchicago.edu/cgi-bin/mailman/listinfo/swift-devel</a><br>
<br></blockquote></div><br></div>