(Click to open topic with navigation)
This topic provides instructions to upgrade Moab Workload Manager to the latest release version using the RPM upgrade method. It includes instructions for migrating your database schema to a new version if necessary.
Because many system-level files and directories are accessed during the installation, the instructions in this guide should be executed with root privileges.
You will see that the instructions execute commands as the root user. Please note that the same commands will work for a non-root user with the sudo command.
3.19.1 Upgrade Steps
Do the following:
You must complete all the previous upgrade steps in this topic before upgrading Moab Server. See the list of steps at the beginning of this topic.
The Moab RPM automatically creates a backup of all relevant files. These backups are stored in /var/tmp/backup-<rpmName>-<timestamp>.tar.gz.
If changes are detected between any existing configuration files and new configuration files, a version of the new configuration file will be saved under <configurationFileLocation>/<fileName>.rpmnew.
On the Moab Server Host, do the following:
[root]# service moab stop
[root]# yum update moab-workload-manager*
You will need to decide whether to start with the old configuration file and add newer configuration options (or vice versa). Typically it depends on the amount of customization you previously made in earlier versions. In instances where you have modified very little, you should consider using the newer configuration and merging site-specific settings from the old file into the new one. The following steps highlight important changes between the 7.2.x default configuration and the 9.0.2 default configuration. Also note that new configuration files may have auto-generated content for secret keys and default passwords—be careful to ensure that secret keys shared between components are configured correctly.
The recommended layout for the /opt/moab/etc/ directory appears as follows:
[root]# ls -l /opt/moab/etc total 29 -rw-r--r--. 1 root moab 2323 Nov 13 13:41 config.moab.pl -rw-r--r--. 1 root moab 989 Nov 13 13:41 config.sql.pl lrwxrwxrwx. 1 root root 14 Nov 13 15:46 moab.cfg -> moab.hpc.cfg -rw-r--r--. 1 root moab 23500 Nov 13 15:43 moab.hpc.cfg drwxr-xr-x. 2 root moab 4096 Nov 13 15:41 moab.d -rw-r--r--. 1 root moab 391 Nov 13 13:41 moab.dat -r--r--r--. 1 root root 493 Nov 6 16:14 moab.lic -rw-------. 1 root moab 288 Nov 13 15:39 moab-private.cfg lrwxrwxrwx. 1 root root 14 Nov 13 15:46 nami.cfg -> nami.hpc.cfg -rw-r--r--. 1 root moab 563 Nov 13 15:43 nami.hpc.cfg
CLIENTCFG[RM:mws] USERNAME=moab-admin PASSWORD=changeme!
The default MWS credentials in 7.2.x were admin:adminpw. For releases after 7.2.x, the default credentials were changed to moab-admin:changeme!. Use whatever credentials you have configured in /opt/mws/etc/mws-config.groovy.
If you are upgrading from a version prior to 9.0, the Torque RPMs will have moved the Torque binaries from /usr to /usr/local. Make sure that your RMCFG[] SUBMITCMD parameter is set to the correct path for qsub.
[root]# vi /opt/moab/etc/moab.cfg RMCFG[pbs] TYPE=PBS SUBMITCMD=/usr/local/bin/qsub
[root]# cp /opt/moab/etc/moab.cfg /opt/moab/etc/moab.cfg.bak
[root]# ln -s /opt/moab/etc/moab.hpc.cfg /opt/moab/etc/moab.cfg
[root]# service moab start