OmniRPC User's Guide Version 1.2: http://www.omni.hpcc.jp/omnirpc/ <omnirpc@omni.hpcc.jp> | ||
|---|---|---|
| Prev | Next | |
So far, we've mentioned local environments which can use rsh, but rsh cannot be used in wide-area network environments. One of the solution for that is the Globus toolkit.
We explain the case of using Globus Toolkit, which is the de facto standard for constructing grid environments. If you use Globus Toolkit, on a remote host, creating the remote executable program, registering and programing is the same as previously stated. The only detail which is different is describing the hostfile. If you don't know much about the Globus Toolkit, please see Globus Alliance.
We assume an execution environment as follows.
Client host is alice.hpcs.is.tukuba.ac.jp .
Remote host is dennis.hpcc.jp. The Globus-gate-keeper must be running on the remote host.
On the remote host, a non special privilege port (the port number is more than 1024) may be opened.
| Warning |
Please refer to the Globus manual for the method to limit the range of Globus ports. |
In the explanation below, we assume an environment setting on which a job can be submitted from the client host to the remote host.