Siva --
To be able to spawn tasks, you should have lam daemons running on the
nodes on which you want to spawn. So effectively this means you should
have lambooted with those nodes in a single scope.
As I see, you can do this under two scenarios --
* If your clusters are rsh based, that is it possible to access individual
nodes across clusters via rsh/ssh, then you can include all the hostnames
in the host file for lamboot (these hostnames may be across clusters)
* If you are using the "globus" environment, then these clusters
effectively form grid machines for you and should be able to use the LAM
globus boot module for this purpose (check the globus boot section in the
user doc for LAM -- http://www.lam-mpi.org/using/docs/ -- be sure to
provide the proper contact strings with the certificates and hostnames in
the host file for lamboot)
For other boot modules, like PBS and BProc, LAM currently does not support
lambooting acrosss clusters; or if you have clusters with different
scheduling mechanisms (like PBS on one and BProc on other), you cannot
currently lamboot across such clusters.
Hope this helps --
-Vishal
On Sun, 29 Feb 2004 sbandham_at_[hidden] wrote:
# Hi,
# I am using a LAM?MPI based cluster.
# Is it possible to spawn tasks on a different cluster from a process within this
# cluster. If so, can someone please give sample code.
#
# thanks
# Siva
#
# _______________________________________________
# This list is archived at http://www.lam-mpi.org/MailArchives/lam/
#
|
