Effect on system availability | There is a period of system down time because all nodes have to be shut down in order to upgrade to the next release. Therefore, to minimize user interruption, schedule the upgrade for a time when system use and user activity is low. For your site, this might be over the weekend or perhaps after work hours or late in the evening. |
Effect on HP XC licensing | The upgrade does not affect XC licensing. Your current XC license is still valid, and you do not require a new XC license. However, you must contact your HP representative to upgrade your license file if your previous HP XC system was configured with LSF-HPC with SLURM and you want to switch to the standard LSF option in Version 3.0. |
Time to complete the upgrade | It takes approximately 30 minutes to upgrade the head node. The number of nodes to be reimaged influences the amount of time it takes to complete the entire upgrade process. You must also allow some time to upgrade your third-party applications as well. |
Effect on existing RPMs | The upgrade process attempts to upgrade all Linux and HP XC RPMs currently installed on your system. |
Effect on configuration files | The upgrade process preserves existing configuration files by renaming them with a .rpmsave file extension. You must perform amanual merge for any standard Linux or HP XC configuration files that contain previous user customizations. |
Effect on nodes that are down | You must reimage any nodes that are in a DOWN state during the upgrade when they are returned to operation. |
Printable version
