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

From PDP/Grid Wiki
Jump to navigationJump to search
Line 37: Line 37:
 
=== Generation of the OS update template for Quattor ===
 
=== Generation of the OS update template for Quattor ===
 
(NOTE: These article has been updated with the steps followed to upgrade from Centos56 to Cento57)
 
(NOTE: These article has been updated with the steps followed to upgrade from Centos56 to Cento57)
 +
 +
If you're just installing a new kernel, go directly to the step "errata".
  
 
The current procedure for generating the OS updates is divided into two major steps:
 
The current procedure for generating the OS updates is divided into two major steps:

Revision as of 11:39, 25 January 2012

There are various kinds of packages that need to be updated frequently:

  • updates for the Operating System
  • updates for the gLite middleware
  • updates for the VL-e software
  • new versions of the CA packages
  • new Quattor releases

There is a lot of similarity in these updates. This article describes the procedures for the updates listed above, except for the gLite updates. Updating gLite packages is more complicated than the other updates; therefore, there is a dedicated article Updating Quattor-managed gLite servers.

Installing updates comprises the following steps:

  • Synchronization of the local mirror of the OS repository
  • Generation of Quattor update templates
  • Compilation and deployment

Synchronization of the local mirror

To synchronize the local mirror of the Operating System, execute the following script as user ndpfmgr at Quattor server stal:

mirror-centos

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

To synchronize the local mirror of the CA mirror in /project/quattor/www/html/mirror/CA/, execute the following script as user ndpfmgr at Quattor server stal:

mirror_cas

To synchronize the local mirror of the Quattor software under /project/quattor/www/html/quattor/, execute the following script as user ndpfmgr at Quattor server stal:

mirror-quattor

To synchronize the local mirror of the VL-e PoC R3 mirror under /project/quattor/www/html/mirror/VL-e//R3/, execute the following script as user ndpfmgr at Quattor server stal:

mirror-vle

At the moment, the following distributions are mirrored:

  • CentOS 4.9 i386
  • CentOS 4.9 x86_64
  • CentOS 5.7 x86_64

Generation of the OS update template for Quattor

(NOTE: These article has been updated with the steps followed to upgrade from Centos56 to Cento57)

If you're just installing a new kernel, go directly to the step "errata".

The current procedure for generating the OS updates is divided into two major steps:

But before going through any of these steps, a new branch needs to be created (By using your local copy):

  • cd $L/cfg/os
  • cp -a centos56_x85_64 centos57_x86_64

The copied branch still contains the directories that Subversion uses internally. They need to be removed:

  • find $L/cfg/os/centos57_x86_64 -type d -name .svn -exec rm -rf {} \;

The templates under the directory $L/cfg/os/centos57_x86_64/rpms can also be deleted, as new ones will be generated by buildOSTemplates. Now you can proceed with the actual first step:

buildOSTemplates

This is script is located under $L/bin and, as said, it will produce OS templates from a Red Hat style OS distribution. These are the relevant options to be used (For more information about other options, have a look at the script):

  • --compsdir : name of directory under Distrib_Root containing comps.xml or file name passed with --compsxml
  • --compsxml : name of xml file describing packages to be installed if different from comps.xml
  • --debug : enable (very) verbose option in called tools. Use several times to increase verbosity.
  • --rpmdir : name of directory under Distrib_Root containing RPMs
  • --scdbroot : path of SCDB top-level directory (must contain externals/). Default to current directory. As an alternative, define environment variable QUATTOR_SCDB_ROOT.
  • Distrib_Root : directory containing both a 'base' and a 'RPMS' directory.
  • Template_Dir : directory where to put the generated templates.

This is the generic script usage:

$L/bin/buildOSTemplates <OPTIONS> Distrib_Root Template_Dir

Example:

$L/bin/buildOSTemplates --compsdir os/x86_64/repodata --compsxml mycomps.xml --debug --rpmdir os/x86_64/CentOS --scdbroot $L /project/mirror/centos/5.7 $L/cfg/os/centos57_x86_64/rpms

errata

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

$L/../bin/rpmErrata.pl /project/mirror/centos/5.7/updates/x86_64/RPMS/ > \
                        $L/cfg/os/centos57_x86_64/rpms/errata/<DATE>.tpl

where <DATE> is (by convention) the date of generation, formatted as YYYYMMDD (e.g. 20120117).

The generated template contains only the last version of each package found in the update repository, except for the kernel packages. Only if the package was already installed before it will be updates. For kernel packages, a comment line for the last version is added. The kernel to be installed are selected somewhere else; see below for details.

The template sites/ndpf/site/os/errata-defaults.tpl defines the default errata versions to be deployed for a particular OS version:

variable OS_ERRATA_TEMPLATE ?= nlist(
  'centos57_x86_64',    'rpms/errata/20120117',
  'centos49_x86_64',    'rpms/errata/20110520',
  'centos49_i386',      'rpms/errata/20110520',
);

If needed, deviations from the defaults can be defined on a per-host basis in template sites/ndpf/site/os/version_db.tpl:

variable NODE_OS_ERRATA_TEMPLATE ?= nlist(
  escape('tbn13.nikhef.nl'),    'rpms/errata/20090101',
);

The definitions in NODE_OS_ERRATA_TEMPLATE take precedence over the defaults.

For each errata template, there must be a corresponding initialization template at location:

os/<OS_VERSION>/config/os/errata/20120117-init.tpl

This template defines the (default) kernel version for the corresponding erratum level:

$ cat os/centos57_x86_64/config/os/errata/20120117-init.tpl 
template config/os/errata/20120117-init;

variable OS_KERNEL_VERSION_ERRATA ?= nlist(
  'centos57',   '2.6.18-274.17.1.el5',
);

It is possible to override the kernel version via the variable KERNEL_VERSION_NUM. The selected kernel version is automatically added to the configuration for GRUB, so that it becomes the default for the next boot.

Generation of other templates

Update templates for VL-e software can be generated using rpmUpdates.pl. The software update template is located under $L/cfg/grid/vle/<PoC-release>/rpms/<OS-version>/updates.tpl

The easiest way to deal with a set of new CAs, is to download the template from the CA site: [http://groep.web.cern.ch/groep/cadist/] (you need to go down into the directory corresponding to the new release and get the file pro_software_meta_lcg_CA.tpl). This file needs to be customized: the template's name should read common/security/lcg-CA and should eventually be saved as $L/cfg/grid/common/security/lcg-CA.tpl

To change the Quattor software that is installed, the new versions should be added by hand to the templates, to be found under $L/cfg/os/<distribution>/rpms/quattor.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.



[1]