Difference between revisions of "Installing updates: OS, CAs, Quattor, VL-e"

From PDP/Grid Wiki
Jump to navigationJump to search
Line 29: Line 29:
  
 
=== Compilation and Deployment ===
 
=== Compilation and Deployment ===
 +
 +
Perform a test compilation in your local environment and do not forget to refresh the repository templates:
 +
makexprof -u -f itb
 +
 +
If this succeeds, commit the changes to SVN and follow the deployment procedure to install the updates.
 +
 +
Note: if a kernel update is installed, schedule a reboot of the node(s) to ensure that the desired kernel is loaded as soon as possible, to prevent surprises at a later stage.

Revision as of 11:38, 17 December 2008

Installing OS updates comprises the following steps:

Synchronization of the local mirror

As user ndpfmgr at Quattor server stal, execute the script

mirror-centos

This will synchronize the local OS mirror at host stal with the OS mirror at spiegel.

At the moment, the following distributions are mirrored:

  • CentOS 3.9 i386
  • CentOS 4.7 i386
  • CentOS 4.7 x86_64
  • CentOS 5.2 i386
  • CentOS 5.2 x86_64

Generation of the OS update template for Quattor

At host stal using your personal account, run rpmUpdates.pl to generate an update template from the available OS updates:

$L/../bin/rpmUpdates.pl /project/mirror/centos/4.7/updates/i386/RPMS/ > /tmp/updates-centos47_i386.tpl

The generated template will contain only the last version of each package found in the update repository, except for the kernel packages, for which all versions are added. By convention, we want Quattor only to keep the installation of the currently running kernel and the desired new kernel version. The other modules should thus be removed by hand.

While editing the generated file, ensure that the template name is rpms/updates. Finally copy the edited file to $L/cfg/os/<distribution>/rpms/updates.tpl

Compilation and Deployment

Perform a test compilation in your local environment and do not forget to refresh the repository templates:

makexprof -u -f itb

If this succeeds, commit the changes to SVN and follow the deployment procedure to install the updates.

Note: if a kernel update is installed, schedule a reboot of the node(s) to ensure that the desired kernel is loaded as soon as possible, to prevent surprises at a later stage.