Page updated: 06/09/2004
About the website

                        Valid XHTML 1.0!

 
gLite 3.0

glite-VOBOX - Update to version 3.0.26-2

Date 27.06.07
Priority High

Description

New BDII with indexing -- High Priority

New version of the BDII which uses indexes. This should significantly reduce the amount of load on a top-level BDII. For example when deployed on lcg-bdii.cern.ch the load dropped by a factor 3.

The bdii-update script has been made more efficient, reading LDIF files directly from disk, not through a pipe. In addition, a configuration parameter has been added to allow a BDII to cache (a subset of) the contents of another BDII.

LFC/DPM -- High Priority

The new version of LFC/DPM (1.6.5-1) fixes various bugs and has among others the following improvements:
  • Remove expired spaces.
  • Avoid crash in dpm_errmsg/Cns_errmsg when supplied buffer is too small (GGUS ticket #21767).
  • Correct processing of rfio_access on DPM TURLs (Atlas).
  • Return DPM version in otherInfo field of srmPing response.
  • dpm-shutdown: take "server" into account.
  • Add methods ping and getifcevers in LFC/DPM.
  • Add ACLs on disk pools (bug #25830).
  • dpm-qryconf: add option --group to display groupnames instead of gids.
  • dpm-qryconf: add option --proto to display supported protocols.
  • dpm-qryconf: add option --si to display sizes in power of 10 (bug #25810).
  • Implement recursive srmLs and srmRmdir.
glite-yaim

The new version of glite-yaim (3.0.1-22) fixes various bugs and has several new features.
  • For MDS, the config_gip function has been updated to correctly configure ldap schema for new openldap versions.
  • New variable (DPNS_BASEDIR) introduced. 
    # Space separated list of email addresses which will be written into /root/.forward"
# ROOT_EMAIL_FORWARD="gridadmin@mysite.mydomain security@mysite.mydomain"
# The DPNS server's entry point in this domain (home)
# i.e. this server will serve the /dpm/${MY_DOMAIN}/${DPNS_BASEDIR} name space
# It is to ensure that if 2 or more DPM server is installed under the same domain
# their name space should be (strongly suggested to be) separated, i.e. all the DPM
# server in the world can be joined to a uniform name-space later on.
# Use for example DPNS_BASEDIR=home2 or DPNS_BASEDIR=data for your second or third server.
# Correct syntax is without '/' !
#DPNS_BASEDIR=
  • Fix for fetch-crl problem (bug #26033).
  • A cron job is copied to /etc/cron.monthly during the install of a DPM node (and classicSE), which creates the 'generated' directories in advance. It has to be run manually for the first time, then it runs automatically every month.
  • Changes in dCache configuration:
    1. Changed GlueServiceVersion, and GlueServiceType to be LHC compliant in values.
    2. Changed Default replica location service from PNFS to companion database as its now stable.
    3. Added a cron job to run at 22:12 daily to generate the directory for LCG tools and delete all empty generated directories which are older than 2 days. This code is based upon production code created by Patrick Furman and now maintained as part of YAIM.
    These changes do not require steps from the site admins.
    NOTE: these changes were not tested during certification.
  • Removal of MDS configuration on DPM (GGUS ticket #21675).
  • No pool accounts are created on LFC.
  • The last modification time of the site-info.def during configuration is saved in the log file.
  • The config_mkgridmap function has been modified to allow the (non recommended) old sgm/prd user mapping schema, i.e. several sgm/prds are mapped to a single user.

    YAIM will auto-detect the situation and warn about dubious users.conf content, e.g. when only a single pool account has been defined for a VO (like in the example users.conf).

    Correct syntax for the LHCb sgm and production user's certificate FQANs are inserted in example groups.conf.

    Reconfiguration is necessary only if you modified your configuration.

    IMPORTANT: This is one of the last releases providing full set of configuration files. In the future, only very short syntactically correct examples will be distributed. The configuration setting for VOs, priorities, FQANs will be available in YAIM format through the CIC portal.
  • Removal of the default configuration of the FQAN VOViews.
  • YAIMLOG is now only readable by root.
Documentation can be found in the following locations:
Glue Schema

The new version of glue-schema updates to Glue version 1.3. The top-level BDIIs should be updated first, followed by the sites BDIIs and then the GRISs. Only when all the nodes have been updated, new information can be published.



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
 #20767 BDII does not use indices
 #25830 DPM needs ACLs on pools
 #26445 LFC-server-mysql-1.6.4-3 has bad default lcgdm-mapfile location

Updated rpms

Name Version Full RPM name Description
bdii 3.9.0-1 bdii-3.9.0-1.noarch.rpm bdii
DPM-client 1.6.5-1sec.slc3 DPM-client-1.6.5-1sec.slc3.i386.rpm APIs and CLIs for the DPM/DPNS
DPM-interfaces 1.6.5-1sec.slc3 DPM-interfaces-1.6.5-1sec.slc3.i386.rpm Disk Pool Manager Interfaces
glite-UI 3.0.22-1 glite-UI-3.0.22-1.noarch.rpm gLite User Interface
glite-VOBOX 3.0.26-2 glite-VOBOX-3.0.26-2.noarch.rpm gLite VOBOX node
glite-yaim 3.0.1-22 glite-yaim-3.0.1-22.noarch.rpm glite-yaim
glue-schema 1.3.0-2 glue-schema-1.3.0-2.noarch.rpm Glue Schema
lcg-dm-common 1.6.5-1sec.slc3 lcg-dm-common-1.6.5-1sec.slc3.i386.rpm LCG Data Management common libraries and man pages.
lcg-info-dynamic-lsf 2.0.34-1 lcg-info-dynamic-lsf-2.0.34-1.noarch.rpm LSF dynamic information provider.
LFC-client 1.6.5-1sec.slc3 LFC-client-1.6.5-1sec.slc3.i386.rpm Client side libraries for the LFC
LFC-interfaces 1.6.5-1sec.slc3 LFC-interfaces-1.6.5-1sec.slc3.i386.rpm LCG File Catalog Interfaces

The RPMs can be updated using apt 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)