[Saga-devel] ssh file adaptor
Andre Merzky
andre at merzky.net
Tue Jan 6 15:06:14 CST 2009
So, I committed a ssh file adaptor just today.
Basically, that adaptor mounts the remote FS into the local
name space, and then uses the local file adaptor to perform
all operations (README attached). The adaptor then simply
translates URLs back and forth between the name spaces...
It seems to work nicely with ec2 hosts, and standard ssh
host like qb or gumbo or whatever. I'll send some
performance numbers as soon as I have them, but don't expect
that to be great...
The ssh job adaptor is not yet working - but that code lives
in the aws job adaptor at the moment - just need to copy it
over. Stay tuned :-)
The nice thing is that this is making the cloud adaptors
much simplier - they basically are reduced to managing the
virtual machine instances in the Cloud, and to translate the
cloud security into ssh certificates - everything else can
be done via the ssh adaptors.
Cheers, Andre.
--
Nothing is ever easy.
-------------- next part --------------
This ssh file adaptor relies on sshfs/fuse. It mounts a remote file system, and
then translates all URLs into local URLs, in that mounted name space, and
operates via the local adaptor.
MacOS:
FUSE: http://code.google.com/p/macfuse/
SSHFS: http://code.google.com/p/macfuse/wiki/MACFUSE_FS_SSHFS
Linux:
FUSE: http://fuse.sourceforge.net/
SSHFS: http://fuse.sourceforge.net/sshfs.html
The adaptor mounts the remote file systems into
~/.saga/adaptors/ssh/ssh_file/mnt/<unique_id>
Latency for mounting a fs is a <10 seconds (usually about 1). The
mounts are refcounted, so the last object using the mount is doing the
umount. (The 'sshfs_keepalive' option determines if the filesystem is
umounted when the respective SAGA object gets destroyed.)
More information about the saga-devel
mailing list