A software upgrade to HP XC System Software Version 3.1 installs new versions of
Linux and HP XC RPMs on the current system. As part of the upgrade process,
the cluster_config utility re-creates the golden image
on the head node, and the head node represents the configuration from which
all other nodes are upgraded and reimaged.
This section addresses the following topics:
Upgrade Types |
 |
Table 5-1 lists
the two upgrade types that are available; the type of upgrade you perform
depends on the version of Enterprise Linux (EL) that is currently installed
on the system and the version of EL that is delivered in the new HP XC release.
Table 5-1 Upgrade Types
| Upgrade
Type | Description |
|---|
Major | You perform
a major upgrade on systems that are installed
with an HP XC release that is based on an older version of Enterprise
Linux (for example Enterprise Linux 3 [EL3]) and the new HP XC release
is based on the next Enterprise Linux release version (for example, EL4). |
Minor | You perform
a minor upgrade when the new HP XC release
is based on the same version of the Enterprise Linux (EL) operating system
that is currently installed on the system. For example,
a minor upgrade enables you to upgrade the HP XC system from an HP XC release
that is based on EL4 Update 3 to an HP XC release that is based on EL4 Update
4. |
Table 5-3 lists the
upgrade types associated with each supported upgrade path. To find out which
version of Enterprise Linux is currently installed on the system, enter the
following command:
# cat /etc/redhat-release
Red Hat Enterprise Linux AS release 3 (Taroon Update 4) |
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”, 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.
Upgrade Characteristics |
|
Before you begin an upgrade, become familiar with the
upgrade characteristics listed in Table 5-2.
Table 5-2 Upgrade Characteristics
| Characteristic | Description |
|---|
Affect on system availability | 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 HP XC licensing | The upgrade does not affect licensing. Your current HP XC license
is still valid, and you do not require a new HP XC license. |
Time to complete the upgrade | 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)
|
Affect on existing RPMs | The upgrade process attempts to upgrade all Linux and HP XC RPMs
currently installed on the system. |
Affect on configuration files | 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 nodes that are down | 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. |
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
| Version of HP XC System Software Currently Installed | Is An Upgrade to Version 3.1 Supported? | Upgrade Type |
|---|
Version 2.1 | Yes | Major |
Version 3.0 | Yes | Minor |
| Version 3.1 Accelerated Deployment
Kit (ADK)[1] | Yes | Minor |
|
| |
|
 | NOTE: Enter the following command if you are not sure what version of
the HP XC System Software is installed on the system: |
|
| |
|
Upgrade Commands |
|
Table 5-4 lists
the commands and utilities that are run as part of a software upgrade process.
Table 5-4 Commands Used During the Upgrade Process
| Command/Utility
Name | Description | Used During Major Upgrade? | Used During Minor Upgrade? |
|---|
preupgradesys | Prepares
the system for the upgrade. | Yes | Yes |
upgraderpms | For
minor upgrades only, this command upgrades the system with new versions of
Linux and XC RPMs. | No | Yes |
upgradesys | Backs
up the existing configuration and management database and migrates existing
data to the new release format. | Yes | Yes |
cluster_config [--migrate|--init] | Reconfigures the system after the upgrade. You have the option
to migrate the existing configuration or apply new default role assignments
to the existing configuration. | Yes | Yes |
Is Upgrading Right for Your System? |
|
An upgrade path from previous HP XC System Software releases to Version 3.1 is provided,
but HP recommends a new installation of Version 3.1. This recommendation
is consistent with other Linux vendors, who also recommend a new installation
rather than an upgrade because the Linux upgrade operation has a lower probability
of success and does not provide a consistent experience. In some cases, some
Linux RPMs might fail to operate properly after the upgrade.
An upgraded system is similar but not identical
to a freshly installed Version 3.1 HP XC system. Compatibility RPMs
are missing on upgraded systems (*.i386 versions), and
a portion of the RPMs from the previous release remain on an upgraded system.
Readiness Criteria
Use the requirements listed in Table 5-5 to determine whether or not an upgrade is appropriate
for the system. Your system must meet all requirements in order for an upgrade
to be successful.
Table 5-5 Upgrade Readiness Criteria
| Component | Requirement |
|---|
| Version of HP XC System Software currently installed on the
system | The existing HP XC system
must be running HP XC System Software Versions 2.1, 3.0, or 3.1ADK with all available patch
kits installed. |
| Firmware | The
firmware versions installed on all system components has been updated according
to the Version 3.1 master firmware revision list, which can be accessed from
the following Web site: http://www.docs.hp.com/en/highperfcomp.html |
| Distribution media | You
must have in your possession the HP XC System Software Version 3.1 DVD that is appropriate
for the cluster platform architecture |
Printable version
