To add to what Reuti said, if you enable PBS support in Open MPI, when users "mpirun ..." in a PBS job, Open MPI will automatically use the PBS native launching mechanism, which won't let you run outside of the servers allocated to that job.
Concrete example: if you qsub a job and are allocated node A, B, and C, but then try to run with "mpirun --host D,E,F ...", you'll get an error.
That being said -- keep in mind what Reuti said: if users are allowed to ssh between nodes that are not allocated to them, then they can always bypass this behavior and use just Open MPI's ssh support to launch on nodes D, E, F (etc.).
On Feb 5, 2013, at 2:46 AM, Reuti <reuti_at_[hidden]> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> Am 05.02.2013 um 11:24 schrieb Duke Nguyen:
>> Please advise me how to force our users to use pbs instead of "mpirun
>> --hostfile"? Or how do I control mpirun so that any user using "mpirun
>> --hostfile" will not overload the cluster? We have OpenMPI installed
>> with Torque/Maui and we can control users's limits (total number of
>> procs, total nodes, total memories etc) with Torque/Maui, but if a user
>> knows the cluster, and creates himself a hostfile with all the available
>> nodes then he can use them all.
> Can the users use a plain ssh between the nodes? If they are forced to use the TM of Torque instead, it should be impossible to start a job on a non-granted machine.
> - -- Reuti
>> users mailing list
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG/MacGPG2 v2.0.18 (Darwin)
> Comment: GPGTools - http://gpgtools.org
> -----END PGP SIGNATURE-----
> users mailing list
For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/