[kepler-dev] File Activity Simulation: Please suggest

subhav mital mital.subhav at gmail.com
Fri Sep 25 13:31:26 PDT 2009


Hi Norbert,
This is just a case of Collaborative Sharing. Either some application, or
for eg: A Shell Script modifies the contents of the file.

So once the Script executes something and changes are made to the file, then
the copy back to the Client needs to be triggered.

I am not clear how will this be automated, but maybe a poll on the remote
server to check if the file is received, and to check when updating is done,
to copy it back.

Can you think of something similar?

Also, another questions I had. Can the execute, cause some changes to the
copied file on the remote server?

Thanks a lot!!





On Fri, Sep 25, 2009 at 3:06 PM, Podhorszki, Norbert <pnorbert at ornl.gov>wrote:

> Subhav,
>
> It is not clear from your description, what is "causing the file change"
> and if there is any problem for your workflow to discover in 3) "when done".
> If it's the workflow that executes the program on the remote machine, than
> this is a simple three step pipeline of
> copy - execute - copy. What more needs to be automated?
>
> Norbert
>
>
> On 9/25/09 2:34 PM, "subhav mital" <mital.subhav at gmail.com> wrote:
>
> Hi,
>
> I am trying to simulate the following scenario. Would be glad if someone
> could please throw some light on implementation possibilities in Kepler.
>
> Suppose there is a file copied onto a Remote Server. Now a program on the
> server causes the file to change its contents. Once these contents have been
> modified, the modified file must return back to the Client.
>
> 1) Copy file A from Client to Remote Server 2) Make changes to that file 3)
> When done, copy the file back to the Client.
>
> Moreover, is there any way to automate this procedure?
>
> Please suggest..
>
> Thanks...
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mercury.nceas.ucsb.edu/kepler/pipermail/kepler-dev/attachments/20090925/1047aa67/attachment.html>


More information about the Kepler-dev mailing list