Appendix C. Upgrading ParaStation4 to ParaStation5
This appendix explains how to upgrade an existing ParaStation4 installation to the current ParaStation5 version.
C.1. Building and installing ParaStation5 packages
Just recompile the packages:
#rpmbuild
#rpm
#rpmbuild
#rpm
#rpm
#rpmbuild
#rpm
Before installing the new packages, stop the ParaStation psid daemon on each node. This will terminate all currently running jobs!
Install the psmgmt, pscom and psmpi2 packages on all nodes using the rpm command. Install the psdoc package holding the documantation on the login node(s) and frontend servers.
The existing ParaStation4 configuation file /opt/parastation/config/parastation.conf is just fine for ParaStation5. If new features like process pinning should be used, adjust the existing configuration file. Look for pinProcs, CPUmap, bindMem, supplGrps and RLimit Core entries in the new template file parastation.conf.tmpl, copy them to the current configuration file and adjust them to your needs.
The configuration file of ParaStation5 located in /etc is no longer a symbolic link to /opt/parastation/config/parastation.conf, therefore we recommend to copy this file to /etc.
Restart the ParaStation daemons:
# psiadmin -s
This will startup the psid on all nodes of the cluster. Check with psiadmin command if all nodes and interconnects are available.
C.2. Changes to the runtime environment
When running applications with ParaStation5, some differences to ParaStation4 must be observed.
First of all, jobs must be started using the new mpiexec command. Refer to mpiexec(8) for options and details.
The former mpirun command is no longer supported! If it is still available, due to an ParaStation4 mpich- ps4 package still installed, this command will not run executables compiled and linked with ParaStation5!
In addition, jobs may no longer be started by running the executable, like
$ ./myprog …
ParaStation5 Administrator's Guide | 89 |
