HP XC System Software Installation Guide Version 3.1

5.1.2 Differences Between Major and Minor Upgrades
The tasks you perform for a major and minor upgrade are essentially the same. The primary difference
occurs in “Task 4: Upgrade Linux and HP XC RPMs” (page 100), where you use the upgraderpms command
if you are performing a minor upgrade. The documentation clearly states where differences occur.
For major software upgrades, the HP XC software upgrade process begins on the head node and is based
on the Anaconda Kickstart automated installation process; all tasks are performed by the root user on the
head node. The HP XC DVD software distribution contains a bootable image and an embedded
ks_upgrade.cfg Kickstart upgrade file, which is accessed on the DVD when you start the upgrade.
For minor software upgrades, the software upgrade process begins on the head node, but the underlying
update mechanism is the Yellow Dog Updater, Modified (YUM). YUM determines RPM dependencies
and updates, installs, and removes RPMs from the system accordingly.
5.1.3 Upgrade Characteristics
Before you begin an upgrade, become familiar with the upgrade characteristics listed in Table 5-2.
Table 5-2 Upgrade Characteristics
DescriptionCharacteristic
A period of system down time occurs because all nodes have to be shut down
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.
Affect on system availability
The upgrade does not affect licensing. Your current HP XC license is still
valid, and you do not require a new HP XC license.
Affect on HP XC licensing
A major upgrade takes approximately 30 minutes to upgrade the head node.
A minor upgrade takes approximately 10 minutes to upgrade the head node.
The following elements also influence the time it takes to complete the entire
upgrade process:
• cluster_config processing and the time it takes to re-create the golden
image
• The number of nodes to be reimaged
• Reinstalling or upgrading the additional software that may have been
installed on the HP XC system (such as other HP products, third-party
applications, and open source software)
Time to complete the upgrade
The upgrade process attempts to upgrade all Linux and HP XC RPMs
currently installed on the system.
Affect on existing RPMs
The RPM upgrade process saves user customizations to existing HP XC
configuration files by renaming them with a .rpmsave or .rpmsave file
extension.
If you want to retain your customizations to these files or to any
customizations you made to standard Linux configuration files, you must
perform a manual merge of the customizations into the newly delivered
version of the file (which may have changed).
Affect on configuration files
If a node or nodes is in the DOWN state during the upgrade, you must reimage
those nodes as soon as they are returned to operation.
Affect on nodes that are down
5.1.4 Supported Upgrade Paths
Table 5-3 lists the supported upgrade paths to HP XC System Software Version 3.1.
Table 5-3 Supported Upgrade Paths
Upgrade Type
Is An Upgrade to Version
3.1 Supported?Version of HP XC System Software Currently Installed
MajorYesVersion 2.1
MinorYesVersion 3.0
MinorYesVersion 3.1 Accelerated Deployment Kit (ADK)
1
1 An ADK is also sometimes known as an advanced developer's kit.
96 Upgrading an HP XC System