Will these kinds of things work in all launchers, or just ssh?
I'm a little uncomfortable with going to extraordinary measures for a fairly
uncommon scenario, especially when there are mechanisms that already exist that
are designed for this kind of use case (i.e., logic in shell login/startup
Ralph,
right now, I am using ssh
one way to go is to extend the machine file syntax
instead of
user@host
we could have
user@host:port//prefix
an other way would be to do this on the command line :
mpirun --host host1 --prefix prefix1 a.out : -- host host2 --prefix prefix2
b.out
an other really
Back in the days when I worked on heterogeneous machines like this, I had logic
in my shell startup files to set paths properly. E.g. (pseudocode):
-
arch=`config.guess`
switch $arch:
case *x86_64-linux*)
prefix_path=$HOME/x86_64-linux-stuff/bin
prefix_ldpath=$HOME/x86_64-linux-stuff/lib
Hi Gilles
What launch environment? We don't currently have a simple way of doing this
outside of ensuring the paths on those nodes point to the correct default
place (i.e., you can't use prefix). However, it might be possible to add
such support if we knew which nodes were what type. Unfortunately
Folks,
i am trying to run heterogeneous Open MPI.
all my nodes use NFS everything is shared, so i need to manually specify
x86_64 nodes must use /.../ompi-x86_64 and sparcv9 nodes must use
/.../ompi-sparcv9
is there a simple way to achieve this ?
Cheers,
Gilles
