[kepler-dev] File Activity Simulation: Please suggest

subhav mital mital.subhav at gmail.com
Fri Sep 25 18:32:28 PDT 2009


Oh...That sounds interesting. I will try this out with the Directory Listing
Actor and looks like this should work out...
Thanks for creating this great suite of SSH actors!

However, I am still confused about this: Is there a way to execute a script
from the Client which causes the modification? The rest can be taken care by
a combination of the Directory listing actor to search for the file thereby
copying the selected/modified file using SCP.

Thanks!


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

> Subhav,
>
> All my workflows have to poll the remote file system currently to discover
> new files or modified files, so that
> they can work on them. See SSH Directory Listing actor.
>
> I do not understand your last question. If you transfer a file to a remote
> machine and then execute a command on that machine through the same SSH
> connection, then the process of the remote command has the access rights to
> do anything with that file. Unless that user account is configured somehow
> to have all files newly created to be read-only (never seen that).
>
> Norbert
>
> On 9/25/09 4:31 PM, "subhav mital" <mital.subhav at gmail.com> wrote:
>
> 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/ea06dfbd/attachment.html>


More information about the Kepler-dev mailing list