Task 8: Configure the System and Propagate the Golden Image

Back up the existing configuration and management database and migrate existing data to the new release format:

# upgradesys

Command output is similar to the following:

The upgradesys utility performs all the necessary steps
to upgrade your cluster.  This script should be run immediately 
after you have upgraded the head node with the latest XC software 
and any third party vendor rpms.  

Do you wish to continue? [y/n] y
Backing up database to 
/opt/hptc/etc/sysconfig/upgrade/upgradesys.dbbackup-20050103145027.sql ...
Executing C02database gupdate
Starting MySQL:                                            [  OK  ]
Executing C20server_type gupdate
Executing C30device_names gupdate
Executing C33etc_hosts gupdate
Executing C35region gupdate
Executing C40role_migration gupdate
Executing C90systemimager gupdate
Removing XC MLIB RPMs

upgradesys output logged to /var/log/upgradesys/upgradesys.log

	CAUTION: Do not proceed to the next step in the upgrade process if the output from the upgradesys script indicates failures. If you cannot determine how to resolve these errors, contact the HP XC Support organization at the following e-mail address: <xc_support@hp.com>

Review the /opt/hptc/systemimager/etc/base_exclude_file to determine if you want to exclude files from the golden image beyond what is already excluded. You revise the base_exclude file file because it is the file that is read when the golden image is re-created as part of the upgrade process. The HP XC System Software Administration Guide describes how to add exclusions to this file.

Decide on the cluster_config option to use to configure the upgraded system. Table 5-8 describes two options to the cluster_config utility that you can use to reconfigure a system after a software upgrade. The option you choose depends upon how you want the upgrade to proceed.

Change directory to the configuration directory:

# cd /opt/hptc/config/sbin

Specify one of the following cluster_config options:

If you followed the instructions in “Task 9: Plan a Service Availability Strategy” to install an availability tool and position related scripts to set up improved availability of services, you are prompted to configure availability sets now. “Task 8: Configure Availability Sets” describes how to configure availability sets. Return to this section when you are done.

Do the following when the cluster_config utility displays the command-line options menu:

[L]ist Nodes, [M]odify Nodes, [A]nalyze, [H]elp, [P]roceed, [Q]uit:

1. If you specified the --init option, use the [M]odify Nodes option to reassign any role assignments you customized in the previous release. For example, if the system configuration had login roles on one or more nodes, you must assign a login role on any node on which you want users to be able to log in. In the default configuration, a login role is not assigned to any node.

2. If the head node was configured as a NIS slave server in HP XC Version 2.1, you must assign the nis_server role to the head node now, because this role was introduced after Version 2.1. Use the [M]odify option of the cluster_config utility to assign this role to the head node.

If you need more information about using the cluster_config command-line options menu to make or modify role assignments, see Appendix G.

When you have finished making role assignments, enter the letter p to proceed with the system configuration process:

[L]ist Nodes, [M]odify Nodes, [A]nalyze, [H]elp, [P]roceed, [Q]uit: p

Do you want to apply your changes to the cluster configuration? [y/n]  y
[S]ervices Config, [P]roceed, [Q]uit: p

Do you want to apply your changes to the service configuration? [y/n] y

The cluster_config utility prompts you to supply system configuration information. When prompted, provide the answers listed in Table 5-9.

Follow along on the system while the cluster_config utility configures the system.

	NOTE: To avoid duplicating command output here, cluster_config output is shown on .

Continue to the next step in this procedure when the cluster_config utility is complete.

Look at the backup copy of the slurm.conf file, which is located in the /hptc_cluster/slurm/etc/slurm.conf.bak file. If you had previously customized this file, you must merge those customizations into the new version of the /hptc_cluster/slurm/etc/slurm.conf file. Otherwise, bypass this step.

Re-enter the monitoring line card entries in the /etc/dhcpd.conf file if the system is using a Myrinet interconnect. See “Configure Myrinet Switch Monitoring Line Cards” for more information about adding entries to this file.

Bypass this step if the system is using an InfiniBand, QsNet^II , or Gigabit Ethernet interconnect.