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 files).
That being said, if there's a core community member who has an itch to scratch (e.g., because said core community member runs into this case all the time :-) ), or if this is poised to become a more common user scenario, then I think patches would be gratefully accepted. :-) :-) :-) > On Apr 17, 2015, at 8:58 AM, Gilles Gouaillardet > <gilles.gouaillar...@gmail.com> wrote: > > 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 nice feature would be to have a suffix per arch, intel MPI is > doing this for mic : > mpirun --host cpu,mic a.out > a.out runs on the Xeon and a.out.mic runs on the Xeon phi > > for the time being, I use a very cheap hack : > replace orted with a shell scripts that exec the right binary, > and replace a.out with a wrapper that > 1. sets LD_LIBRARY_PATH according to the right arch > since open MPI sets this for the arch on which mpirun is invoked, which might > not be the expected one > 2. invoke the right binary for this arch > > an other really nice feature would be to have mpirun invoke this wrapper > "under the hood" : > > mpirun --wrapper wrapper.sh a.out > would invoke > wrapper.sh a.out > on all the nodes, and in this script, I can manually execs a.out from the > right path (e.g. one path per arch) > > an alternative to extending the machine file syntax would be to invoke an > other wrapper for orted : > mpirun --orted-wrapper ortedwrapper.sh --wrapper binwrapper.sh a.out > that would allow the end user to "implement" self discovery > > cheers, > > Gilles > > On Friday, April 17, 2015, Ralph Castain <r...@open-mpi.org> wrote: > 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, we would need > to know that prior to launching the daemons, so we can't self-discover it. > > > On Fri, Apr 17, 2015 at 2:32 AM, Gilles Gouaillardet <gil...@rist.or.jp> > wrote: > 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 > _______________________________________________ > devel mailing list > de...@open-mpi.org > Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel > Link to this post: > http://www.open-mpi.org/community/lists/devel/2015/04/17237.php > > _______________________________________________ > devel mailing list > de...@open-mpi.org > Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel > Link to this post: > http://www.open-mpi.org/community/lists/devel/2015/04/17242.php -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
