[kepler-dev] ssh: Kepler and remote things

Norbert Podhorszki pnorbert at cs.ucdavis.edu
Wed Apr 26 08:50:25 PDT 2006


Hi,

I would like to note that recently I have developed a tiny ssh package 
(not actors) with the singleton design pattern in order to use an ssh 
connection to a remote machine to be able to do nasty things, several 
times, in different actors of the workflow, still typing password (secure 
One-Time-Password) only once.

You may know from Bertram that I am hired to do plumbing... so all 
workflows coming out my hands are just nasty, 
what-to-avoid-in-Kepler-tutorialable creatures.

But I have created my job management package and actors and some others 
just silently use the ssh package if it is about using a remote target 
instead of the local machine. A remote machine is for me now just a string 
'user at host', fed to the actors as a parameter. And I do not need to care 
about it more (since my actors do).

I do not know what challenges the Resurgence project faces, but I have to 
execute supercomputer jobs, move files between machines, execute external 
programs and watch remote directories for intermediate results. In my 
dreams I run Kepler still on my local machine, while heavy things happen 
remotely.

I am not planning to put anything into the cvs before the first release, 
but of course all that code is intended to become part of Kepler sometime. 
Maybe others need also develop such actors that can work both locally and 
remotely. For instance, my FileList actor can read a directory content 
either locally using Java's File or a remote (Unix) one with ssh and 'ls'.
And the output is always just the list of files that had been created 
after the previous check.
Anyone interested, just contact me.

Norbert

On Wed, 26 Apr 2006, Wibke Sudholt wrote:
> ...
> work without problems. It would considerably ease my (and probably also
> other people's) work when it would also be realistically possible to run
> Kepler remotely via ssh, since at least for the Resurgence project several
> external codes need to be installed (Nimrod, GAMESS etc.) that you often
> only want to have installed on a server and not on user machines. Also, it

-- 

      Norbert Podhorszki
    ------------------------------------
      University of California, Davis
      Department of Computer Science
      1 Shields Ave, 2236 Kemper Hall
      Davis, CA 95616
      (530) 754-8188
      pnorbert at cs.ucdavis.edu
      ----------------------------------


More information about the Kepler-dev mailing list