Had to go back into the deep, dark archives and look at the source code to
address this. :-)
Your understanding is correct - ompi should see those envars and automatically
use xgrid.
I don't see anything in the source code beyond those variables described in the
reference you provided. You
To be more specific.
I have a working xgrid with the envirnment variables set. In
particular I can run xgrid commands from the shell prompt like this:
xgrid -job submit /bin/hostname
and it runs because the enviroment variables are set.
my understanding is that openMPI will look for those
If you want, you can upgrade to the last release in the 1.2 series from the
www.open-mpi.org web site. Anything in 1.2 will work - just not beyond.
On Jun 21, 2010, at 1:40 PM, Barrett, Brian W wrote:
> You have to set two environment variables (XGRID_CONTROLLER_HOSTNAME and
>
You have to set two environment variables (XGRID_CONTROLLER_HOSTNAME and
XGRID_CONTROLLER_PASSWORD) with the correct information in order for the XGrid
starter to work. Due to the way XGrid works, the nolocal option will not work
properly when launching with XGrid.
Brian
On Jun 21, 2010, at
Perhaps I was mistaken about 1.5rc1.As for the installed openMPI
on mac osx, my 10.5 OSX has v1.2.3 when I try to run it, it works
fine locally but it never finds the xgrid.
any mpi job I run, will run on the localhost not the xgrid agents. If
try to force the issue by specifying
Where did you see that 1.5 works with xgrid? That support has been broken since
the 1.2 series, unfortunately, so it would help to ensure we don't have stale
docs out there to the contrary.
As for the 1.2 results, you are aware (I imagine) that OSX ships with the last
1.2 release already
