Re: [Condor-users] Chirp/Parrot for Job Submission (R software)

["Natarajan, Senthil" <senthil@xxxxxxxx>]

Hi Doug,
I have a quick question.
How to specify the port no, so that the node will use the same port no
to communicate to the chirp server running on 9094.

Now what's happening is the node sends the message from dynamic port no
to chirp server.

Since our server has the firewall, it is difficult to setup the firewall
rule, because each time the source port no is changing.

Hope you understand what I am asking. Do I need to do something in the
condor (I already have HIGHPORT, LOWPORT for firewall) Please let me
know.



Thanks,
Senthil


-----Original Message-----
From: Douglas L Thain [mailto:dthain@xxxxxxxxxx] 
Sent: Tuesday, November 14, 2006 9:25 PM
To: Natarajan, Senthil
Cc: dan@xxxxxxxxxxxx; condor-admin@xxxxxxxxxxx; Condor-Users Mail List
Subject: Re: Chirp/Parrot for Job Submission (R software)


Hello Senthil -

Yes, you can use Parrot and Chirp to simulate a distributed filesystem.
I can't tell if your submit scripts are perfect,
but you have the right  idea.

Here are some similar examples that may help:
	http://www.cse.nd.edu/~ccl/software/howto/remotelink.shtml
	http://www.cse.nd.edu/~ccl/software/howto/secure.shtml
	http://www.escience.cam.ac.uk/projects/camgrid/parrot.html

Cheers -
Doug

On Tue, 14 Nov 2006, Natarajan, Senthil wrote:

> Hi Dan/Douglas,
>
> I am trying to submit R software (Statistical Software) Job to condor.
>
> The problem is I don't have shared file system and hence the job fails
> while executing on the remote node (which doesn't have R installed,
and
> also we don't know the path etc). So I was wondering if I installed R
> software on Chirp Server, which also running in the same machine as
> condor central manager (job submitting node), the job running on the
> remote node can use R software through Parrot on the Chirp server. Is
it
> possible? Please let me know if you have any better suggestion for
this
> problem.
>
> Please let me know.
>
>
>
> So the job submission will look something like this.
>
>
>
> Original Job Specification
>
> *****************************
>
> Executable = /usr/lib/R/bin/R
>
> arguments = --vanilla
>
> universe = vanilla
>
> Log = Ra0.log
>
> notification = error
>
> input = a0
>
> output = a0.Rout
>
> error =Ra0.err
>
> should_transfer_files = YES
>
> when_to_transfer_output = ON_EXIT
>
> Queue
>
>
>
> Job Specification with Chirp and Parrot
>
> *********************************************
>
> Executable = parrot
>
> arguments = -H R --vanilla
>
> universe = vanilla
>
> Log = Ra0.log
>
> environment = LD_LIBRARY_PATH=/chirp/servername/library
>
> notification = error
>
> input = a0
>
> output = a0.Rout
>
> error =Ra0.err
>
> should_transfer_files = YES
>
> when_to_transfer_output = ON_EXIT
>
> Queue
>
>
>
> Thanks,
>
> Senthil
>
>
>
>