[Swift-devel] Condor-G test on UJ-OSG site
Zhao Zhang
zhaozhang at uchicago.edu
Mon May 11 13:07:39 CDT 2009
Hi, Mihael
Mihael Hategan wrote:
> On Mon, 2009-05-11 at 12:59 -0500, Zhao Zhang wrote:
>
>> Hi, Ben
>>
>>
>> Ben Clifford wrote:
>>
>>> On Fri, 8 May 2009, Zhao Zhang wrote:
>>>
>>>
>>>
>>>> So, for the remote job manger, I could use pbs, condor, fork or SGE which ever
>>>> is available on the remote site, right?
>>>>
>>>>
>>> Yes. You must use whichever is installed on the remote site. For OSG thats
>>> what swift-osg-ress-site-catalog tells you.
>>>
>>>
>> Yes, for most of the time, it is correct. Here is a case: FLTECH site.
>> In the site information web site, it says both condor and fork are
>> available,
>>
>
> Fork should always be available, but it's not something you run cluster
> jobs with.
>
What does "cluster jobs" mean?
>
>> http://vors.grid.iu.edu/cgi-bin/index.cgi?region=0&VO=24&grid=1&dtype=0&res=322#SITELISTING,
>> and swift-osg-ress-site-catalog chose condor as the default job manager.
>> But I couldn't run any job there with condor job manager,
>>
>
> Why is that?
>
Hmm, it is working now. But when I tried it on Friday, my swift client
was just hanging there. Is there any schedule policy difference between
those two job manager?
zhao
>
>> while if I use
>> fork, jobs were running. Again, I am
>> attaching the sites.xml file.
>>
>> zhao
>>
>> [zzhang at tp-grid1 condor-g]$ cat FLTECH.xml
>> <config>
>> <!-- FLTECH -->
>> <pool handle="FLTECH" >
>> <gridftp url="gsiftp://uscms1.fltech-grid3.fit.edu/" />
>> <execution provider="condor" />
>> <workdirectory >/mnt/nas0/OSG/DATA/osg/tmp/FLTECH</workdirectory>
>> <profile namespace="globus" key="jobType">grid</profile>
>> <profile namespace="globus" key="gridResource">gt2
>> uscms1.fltech-grid3.fit.edu/jobmanager-fork</profile>
>> </pool>
>> </config>
>>
>
>
>
More information about the Swift-devel
mailing list