OmniRPC User's Guide Version 1.2: http://www.omni.hpcc.jp/omnirpc/ <omnirpc@omni.hpcc.jp> | ||
---|---|---|
Prev | Appendix A. Description of hostfile | Next |
We show an example below.
<?xml version="1.0" ?> <OmniRpcConfig> <Host name="jones.is.tsukuba.ac.jp"> <Host name="alice.hpcc.jp" user="foo" arch="i386" os="linux"> <Agent invoker="globus" mxio="on" path="/usr/local/omrpc"/> <JobScheduler type="rr" maxjob="6" /> <Registry path="/home/foo/app/stubs" /> <WorkingPath path="/home/foo/tmp" /> <Description> This is a sample host description. </Description> </Host> <TimeOut second="20"> </OmniRpcConfig>
We specify 2 hosts(jones.is.tsukuba.ac.jp and alice.hpcc.jp). In jones.is.tsukuba.ac.jp, the defaults setting is used, so the invocation method of the agent is "rsh" and a remote executable program is allocated. Because alice.hpcc.jp is a remote server node, Globus Toolkit's GRAM is used as a agent invocation method. Registry is at "/home/foo/app/stubs", not the default setting. Remote executable programs are executed by the round-robin scheduler, which is the built-in scheduler in the OmniRPC agent. 6 remote executable programs are invoked. Also, the account in alice.hpcc.jp is "foo and worker programs use "/home/foo/tmp" directory to store temporary files, not the default setting (default directory is "/tmp"