[Swift-devel] swift on ranger

[Michael Wilde]

With 0.92.1 I am able to run coasters local:sge on Ranger:

login3$ swift -config cf -tc.file tc -sites.file sites06.xml catsn.swift -n=1
Swift svn swift-r4371 cog-r3096

RunID: 20110630-2250-pn3dfi67
Progress:
Progress:  Submitted:1
Progress:  Submitted:1
Progress:  Submitted:1
Progress:  Submitted:1
Progress:  Submitted:1
Progress:  Active:1
Final status:  Finished successfully:1
Canceling job 2013431
login3$ cat sites06.xml
<config>
 <pool handle="localhost">
   <execution provider="coaster" url="none" jobManager="local:sge"/>
     <profile namespace="globus" key="slots">1</profile>
     <profile namespace="globus" key="nodeGranularity">16</profile>
     <profile namespace="globus" key="maxNodes">16</profile>
     <profile namespace="globus" key="workersPerNode">16</profile>
     <profile namespace="globus" key="pe">16way</profile>
     <profile namespace="globus" key="maxtime">1800</profile>
     <profile namespace="globus" key="maxwalltime">00:15:00</profile>
     <profile namespace="globus" key="project">TG-CHE110004</profile>    
     <profile namespace="globus" key="queue">development</profile>
     <profile namespace="karajan" key="initialScore">10000</profile>
     <profile namespace="karajan" key="jobThrottle">.15</profile>
   <filesystem provider="local" />
     <workdirectory>/share/home/00306/tg455797/swiftwork</workdirectory>   
 </pool>
</config>
login3$ cat cf
wrapperlog.always.transfer=true
sitedir.keep=true
execution.retries=0
lazy.errors=false
status.mode=provider
use.provider.staging=false
provider.staging.pin.swiftfiles=false
login3$ cat tc
localhost sh /bin/sh null null null
localhost cat /bin/cat null null null
pbs cat /bin/cat null null null
mcs cat /bin/cat null null null
localhost catnap /home/wilde/swift/lab/catnap.sh null null GLOBUS::maxwalltime="00:01:00"

login3$ ls ~/.globus/scripts
OLD                       SGE14622.submit.exitcode  SGE32272.submit.exitcode  SGE982.submit.exitcode.0   SGE982.submit.exitcode.4
SGE13929.submit.exitcode  SGE14622.submit.stderr    SGE32272.submit.stderr    SGE982.submit.exitcode.1   SGE982.submit.exitcode.5
SGE13929.submit.stderr    SGE14622.submit.stdout    SGE32272.submit.stdout    SGE982.submit.exitcode.10  SGE982.submit.exitcode.6
SGE13929.submit.stdout    SGE15887.submit           SGE32273.submit.exitcode  SGE982.submit.exitcode.11  SGE982.submit.exitcode.7
SGE13930.submit.exitcode  SGE233.submit.stderr      SGE32273.submit.stderr    SGE982.submit.exitcode.12  SGE982.submit.exitcode.8
SGE13930.submit.stderr    SGE233.submit.stdout      SGE32273.submit.stdout    SGE982.submit.exitcode.13  SGE982.submit.exitcode.9
SGE13930.submit.stdout    SGE234.submit.exitcode    SGE45187.submit           SGE982.submit.exitcode.14  SGE982.submit.stderr
SGE14621.submit.exitcode  SGE234.submit.stderr      SGE60909.submit.exitcode  SGE982.submit.exitcode.15  SGE982.submit.stdout
SGE14621.submit.stderr    SGE234.submit.stdout      SGE60909.submit.stderr    SGE982.submit.exitcode.2
SGE14621.submit.stdout    SGE26260.submit           SGE60909.submit.stdout    SGE982.submit.exitcode.3
login3$ cd ~/.globus/scripts
login3$ ls -lt
total 172
-rw-r--r--  1 tg455797 G-80243 2540 Jun 30 22:52 SGE982.submit.stdout
-rw-r--r--  1 tg455797 G-80243   96 Jun 30 22:52 SGE982.submit.stderr
-rw-r--r--  1 tg455797 G-80243    2 Jun 30 22:52 SGE982.submit.exitcode.0




----- Original Message -----
> On Thu, 2011-06-30 at 22:34 -0500, Michael Wilde wrote:
> > Does debug=true in etc/provider-sge work, in the same manner it
> > works for provider-pbs?
> 
> What I see in the trunk code is that logger.isDebugEnabled() is used
> as
> a test that decides whether the script is deleted at the end or not.
> 
> This is in the abstract classes that are subclassed by both the pbs
> and
> sge providers, so it should apply to both.

-- 
Michael Wilde
Computation Institute, University of Chicago
Mathematics and Computer Science Division
Argonne National Laboratory