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



gLite 3.2

glite-BDII - Update to version 3.2.1-0

Date 29.06.2009
Priority Normal


Introduction of the BDII
This update introduces the glite-BDII node type for SL5 x86_64.

Please also have a look at the list of known issues.

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

Fixed bugs

Number Description
 #49319 BDII: Update process should tollarate random spaces in DNs.
 #49796 [ glite-yaim-bdii ] 'GlueTop' not allowed

Updated rpms

Name Version Full RPM name Description
bdii 5.0.0-22 bdii-5.0.0-22.noarch.rpm bdii
glite-BDII 3.2.1-0 glite-BDII-3.2.1-0.x86_64.rpm Metapackage for the glite-BDII
glite-info-generic 2.0.2-3 glite-info-generic-2.0.2-3.noarch.rpm glite-info-generic
glite-info-plugin-fcr 2.0.0-2 glite-info-plugin-fcr-2.0.0-2.noarch.rpm glite-info-plugin-fcr
glite-info-provider-ldap 1.2.2-2 glite-info-provider-ldap-1.2.2-2.noarch.rpm glite-info-provider-ldap
glite-info-provider-service 1.0.3-2 glite-info-provider-service-1.0.3-0.noarch.rpm glite-info-provider-service
glite-info-templates 1.0.0-8 glite-info-templates-1.0.0-8.noarch.rpm glite-info-templates
glite-info-update-endpoints 1.0.0-5 glite-info-update-endpoints-1.0.0-5.noarch.rpm glite-info-update-endpoints
glite-version 3.2.0-0.slc4 glite-version-3.2.0-0.sl5.x86_64.rpm glite-version
glite-yaim-bdii 4.0.4-9 glite-yaim-bdii-4.0.4-9.noarch.rpm glite-yaim-bdii module configures 3.1 top level BDII and site BDII.
glite-yaim-core 4.0.7-10 glite-yaim-core-4.0.7-10.noarch.rpm glite-yaim-core
glue-schema 1.3.0-5 glue-schema-1.3.0-5.noarch.rpm glue-schema

The RPMs can be updated using yum:

Service reconfiguration after update

Since this is the first BDII release in SL5, the BDII needs to be configured after the installation.

Service restart after update

Since this is the first BDII release in SL5, it will be started automatically after being configured. If YAIM is not used, then start it manually.

How to apply the fix

  1. Install the RPMs (see above)
  2. Run the configuration
  3. Start the service manually, if YAIM is not used