gLite > gLite 3.2 > glite-MPI_utils > Update to glite-MPI_utils 3.2.1-0  
 
 

 

 

gLite 3.2

glite-MPI_utils - Update to version 3.2.1-0


Date 08.02.2010
Priority Normal

Description



glite-MPI_utils

This patch introduces the glite-MPI_utils metapackage for gLite 3.2

This release of the glite-MPI_utils fixes a long known dependency issue with an incompatible torque library provided by the torque RPM.

There have been several updates to glite-yaim-mpi:

  • The YAIM configuration will now look in the YAIM "services" configuration directory for configuration details.
  • There have been minor changes to the YAIM MPI configuration scripts which fix some observed problems relating to variable assignment.

The default MPI installation is now OPENMPI, which is provided by the Scientific Linux distribution. Support for MPICH1 and MPICH2 has been discontinued on SL4. MPICH2 is available for SL5.

The supplied OPENMPI packages are compiled with support for Infiniband. If your site does not support infiniband, openmpi will output warnings. To fix this problem at your site, please see: http://xmipp.cnb.csic.es/twiki/bin/view/Xmipp/RemoveOpenMPIWarnings

The affected files are:

SL4: /usr/lib/openmpi/1.2.8-gcc/etc/openmpi-mca-params.conf

SL5: /usr/lib64/openmpi/1.2.7-gcc/etc/openmpi-mca-params.conf

glite-ARGUS, glite-BDII, glite-CREAM, glite-LFC_mysql, glite-LFC_oracle, glite-MPI_utils, glite-SCAS, glite-SE_dpm_disk, glite-SE_dpm_mysql, glite-TORQUE_client, glite-TORQUE_server, glite-TORQUE_utils, glite-UI, glite-VOBOX, glite-WN

New release of yaim core

New release of yaim core containing a set of bug fixes and new features:

  • New SAGA adapters. There's a new function called config_glite_saga that configures the SAGA gLite adapters.
  • grid environment cleaning mechanism to be able to install different WN tarball versions in the same machine.
  • Variables that were wrongly implemented in previous yaim releases are now fixed: CONFIG_GRIDMAPDIR and USER_HOME_PREFIX.
  • YAIM doesn't fail when gLite version package is not installed. This is useful for non gLite software using YAIM.
  • siteinfo packaging is now fixed (-p option).

New release of glite-version and glue-schema

The new glite-SE_dpm_disk metapackage introduces a new version of:

  • glite-version: new version of glite-version introducing a set of new options to print information about the versions of the installed gLite nodetypes, their architecture and their update number. It still prints information about the gLite release (i.e. 3.2.0).
  • glue-schema: minor update to change GLUE2PolicyUserDomainForeignKey from being mandatory to optional.

These two packages are also part of other services which are also updated to the new versions with this update,as it can be seen in the service detail pages.

This update fixes various bugs. For the full list of bugs, please see list below.

Fixed bugs

Number Description
 #53462 [ yaim-core ] GROUPS_CONF/group.d mechanism seem to fail in config_sw_dir
 #53745 [ yaim-core ] yaim fails if glite-version is not installed
 #53864 [ yaim-core ] Add SAGA & gLite adapters

Updated rpms

Name Version Full RPM name Description
environment-modules 3.2.6-4.el5 environment-modules-3.2.6-4.el5.x86_64.rpm Provides dynamic modification of a user's environment
glite-MPI_utils 3.2.1-0 glite-MPI_utils-3.2.1-0.x86_64.rpm gLite metapackage (glite-MPI_utils)
glite-yaim-core 4.0.11-2 glite-yaim-core-4.0.11-2.noarch.rpm YAIM core package
glite-yaim-mpi 1.1.5-1 glite-yaim-mpi-1.1.5-1.noarch.rpm yaim module for MPI configuration
i2g-mpi-start 0.0.59-1 i2g-mpi-start-0.0.59-1.noarch.rpm A generic startup mechanism for different MPI installation in a cluster/grid.
mpich2 1.1.1-1.el5 mpich2-1.1.1-1.el5.x86_64.rpm A high-performance implementation of MPI
mpich2-devel 1.1.1-1.el5 mpich2-devel-1.1.1-1.el5.x86_64.rpm Development files for mpich2
mpiexec 0.83-2.el5 mpiexec-0.83-2.el5.x86_64.rpm MPI job launcher that uses the PBS task interface directly
torque 2.3.6-2cri.el5 torque-2.3.6-2cri.el5.x86_64.rpm Tera-scale Open-source Resource and QUEue manager

The RPMs can be updated using yum via

Service reconfiguration after update

Service must be reconfigured.

Service restart after update

Service must be restarted.

How to apply the fix

  1. Update the RPMs (see above)
  2. Update configuration (see above)
  3. Restart the service if necessary (see above)