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 your local HP support center.

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. The base_exclude file file 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.

If you are using the InfiniBand interconnect, verify that the appropriate configuration files were successfully changed so that the XC system is using the same type of InfiniBand software stack as the HP SFS system. The sfsconfig should have changed the following files:

Verify that the newly created HP XC Golden Image is a reasonable size (typically 2 to 3 GB) otherwise the imaging process might fail.

# du –sk /var/lib/systemimager/images/base_image

Decide on the cluster_config option to use to configure the upgraded system. Table 5-6 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 here when you are done.

View the role assignments 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: l

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-7.

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

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

Continue to the next step in this procedure when the cluster_config processing 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 previously customized this file, you must merge those customizations into the new version of the /hptc_cluster/slurm/etc/slurm.conf file. Otherwise, omit this step.

Compare the final LSF configuration with the saved version to ensure that only the appropriate changes relevant to the upgrade have occurred. Also ensure (or restore, if required) the elim scripts.

HP recommends that you use another terminal window to install the elim scripts at the point when the cluster_config utility displays the following prompt:

All user specified configuration is complete.
  The Golden Image will be created next.
  [P]roceed, [Q]uit: 

Thus, changes to the /opt/hptc/lsf/top/6.2/ directory will be included in the golden image. This is the directory where elim scripts reside.

Any changes to the LSF configuration files in the /hptc_cluster/lsf/conf/ directory can occur after cluster_config has finished because this directory is not part of the golden image.

If the LSF version has changed, binary paths (including the $LSF_SERVERDIR directory, where elim scripts reside) have also changed.

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.

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