<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi Mike,<br>
<br>
The schema is here swift-k/resources/swift.conf.schema, and I do see
this wrapperStagingLocalServer<br>
defined in the schema.<br>
<br>
Here's a github link to the schema :
<a class="moz-txt-link-freetext" href="https://github.com/swift-lang/swift-k/blob/master/resources/swift.conf.schema">https://github.com/swift-lang/swift-k/blob/master/resources/swift.conf.schema</a><br>
<br>
-Yadu<br>
<br>
<br>
<br>
<div class="moz-cite-prefix">On 11/08/2014 04:37 PM, Michael Wilde
wrote:<br>
</div>
<blockquote cite="mid:545E9B2A.1020309@anl.gov" type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
I get this error:<br>
<br>
org.griphyn.vdl.util.SwiftConfigException: swift.conf:4 unexpected
property 'site.local.wrapperStagingLocalServer'<br>
at
org.griphyn.vdl.util.SwiftConfigSchema.validate(SwiftConfigSchema.java:214)<br>
<br>
Ive tried spelling this property both as in your sample .conf and
as in your text:<br>
<br>
wrapperStagingLocalServer and wrapperStageingLocalServer<br>
<br>
Neither is accepted. Did a schema change not get committed?<br>
<br>
For general info: where is the json schema file that a user can
check to find all valid conf parameters?<br>
<br>
Thanks,<br>
<br>
- Mike<br>
<br>
<br>
<br>
<div class="moz-cite-prefix">On 11/8/14 4:13 PM, Mihael Hategan
wrote:<br>
</div>
<blockquote cite="mid:1415484807.975.10.camel@echo" type="cite">
<pre wrap="">type file;
app (file c) cat(file a, file b) {
cat filename(a) filename(b) stdout=filename(c);
}
file c <"c.txt">;
file a <"a.txt">;
file b <<a moz-do-not-send="true" class="moz-txt-link-rfc2396E" href="http://mirror.internode.on.net/pub/test/1meg.test">"http://mirror.internode.on.net/pub/test/1meg.test"</a>>;
c = cat(a, b);
--------------------------------------------------------
You would need a proper swift.conf. Here's an example of that:
--------------------------------------------------------
site.local {
staging: "wrapper"
scratch: "/some/scratch/dir"
# *see email comments for details on the following option
# wrapperStagingLocalServer: <a moz-do-not-send="true" class="moz-txt-link-rfc2396E" href="file://">"file://"</a>
}
--------------------------------------------------------
With a proper scratch dir there, this <b class="moz-txt-star"><span class="moz-txt-tag">*</span>should<span class="moz-txt-tag">*</span></b> work for you without any
additional tweaking.
Check _swiftwrap.wrapperstaging's stagein() and stageout() functions.
That's where you would add additional protocols.
The wrapperStagingLocalServer sets the default staging location for
things that do not have an explicit scheme. In the case above, "c.txt"
and "a.txt" are staged in and out using <a moz-do-not-send="true" class="moz-txt-link-rfc2396E" href="file://">"file://"</a>. If you wanted the
default to be some gridftp server, you would say something like
'wrapperStageingLocalServer: "gsiftp://gridftp.server.org/"'. Of course,
_swiftwrap.wrapperstaging would need to know how to handle gsiftp URLs,
which it doesn't at the moment.
Mihael</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Michael Wilde
Mathematics and Computer Science Computation Institute
Argonne National Laboratory The University of Chicago
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Swift-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Swift-devel@ci.uchicago.edu">Swift-devel@ci.uchicago.edu</a>
<a class="moz-txt-link-freetext" href="https://lists.ci.uchicago.edu/cgi-bin/mailman/listinfo/swift-devel">https://lists.ci.uchicago.edu/cgi-bin/mailman/listinfo/swift-devel</a>
</pre>
</blockquote>
<br>
</body>
</html>