Integration with PBS PRO
If an external queuing system is used, the environment variable PSI_NODES_SORT should be set to "none", thus no sorting of any predefined node list will be done by ParaStation.
ParaStation includes its own queuing facility. For more details, refer to Section 5.4, “Using theParaStation5 queuing facility” and ParaStation5 User's Guide.
5.15.1. Integration with PBS PRO
Parallel jobs started by PBS PRO using the ParaStation mpirun command will be automatically recognized. Due to the environment variable PBS_NODEFILE, defined by PBS PRO, ParaStation will automatically setup the PSI_HOSTFILE to PBS_NODEFILE. The environment variable PSI_NODES_SORT is set to "none", thus no sorting of the predefined node list will occur. The tasks will be spawned in the given order on the predefined list of nodes.
Therefore, ParaStation will use the (unsorted) hostfile supplied by PBS PRO to startup the parallel task.
5.15.2. Integration with OpenPBS
Refer to previous Section 5.15.1, “Integration with PBS PRO”.
5.15.3. Integration with Torque
Refer to previous Section 5.15.1, “Integration with PBS PRO”.
5.15.4. Integration with LSF
Similar to Section 5.15.1, “Integration with PBS PRO”, ParaStation will also recognize the variable LSB_HOSTS, provided by LSF. This variable holds a list of nodes for the parallel task. It is copied to the ParaStation variable PSI_HOSTS, consequently it will be used for starting up the task. The environment variable PSI_NODES_SORT is set to "none", thus no sorting of the predefined node list will occur. The tasks will be spawned in the given order on the predefined list of nodes.
5.15.5. Integration with LoadLeveler
ParaStation recognizes the variable LOADL_PROCESSOR_LIST, provided by IBM LoadLeveler. This variable holds a list of nodes for the parallel task. It is copied to the ParaStation variable PSI_HOSTS, consequently it will be used for starting up the task. The environment variable PSI_NODES_SORT is set to "none", thus no sorting of the predefined node list will occur. The tasks will be spawned in the given order on the predefined list of nodes.
5.16. Multicasts
This version of ParaStation uses the ParaStation RDP protocol to exchange status information between the psid(8) daemons. Therefore, multicast functionality is no longer required. It is still possible to use multicasts, if requested.
To enable Multicast message exchange, edit parastation.conf and uncomment the
ParaStation5 Administrator's Guide | 25 |
