What's new

Version 3.2.10 of the glite-UI contains the following changes:

• New version of WMS and LB clients.
  • These clients are also distributed in SL5/32bits.
  • The dependency glite-wms-brokerinfo-access has been added to the glite-UI metapackage.
• New versions of CREAM clients.
  • Provision of glite-ce-job-output command
  • Other bug fixes
  • Known issues: http://grid.pd.infn.it/cream/field.php?n=Main.KnownIssues
• New version of Data Management clients.
  • Added python 2.5 and python 2.6 bindings for Data Management clients.
• New version of yaim clients including optional SAGA adapters configuration.
• New version of yaim core.
• New version of glite-version (change doesn't actually affect glite-UI).
• New version of VOMS-Admin.
• New versions of lcg-infosites, lcg-ManageVOTag and lcg-info.

The following changes not directly affecting the gLite clients are also included in this release:

• New version of c-ares.
• VOMS fixes for memory leak problems.
• Minor security and gridsite fixes.

Configuration changes

There's a new version of yaim clients and yaim core fixing some general configurations bugs. Some of the bug fixes relevant to this release are listed below:

yaim-core

• correction of the undefined function in /opt/glite/yaim/etc/clean-grid-env-funcs.sh
• support for 32-bit PYTHONPATH: a new gLite UI variable, GLITE_UI_ARCH, can be defined, e.g. with allowed values 32BIT and 64BIT. Allow the desired value to be passed as an argument to the grid-env.sh script as well.
• config_lcgenv is able to configure different python paths (2.5, 2.6)
• yaim runs with umask 022
• removed from utils/detect_platform the unpaired "set +e"
• utils/detect_platform has been slightly enhanced now to allow the admin to
• override the platform OS by defining a new variable YAIM_OS_TYPE e.g. in site-info.def. A warning will then indicate that the platform has been overridden.
• improvement on dealing with GLOBUS_TCP_PORT_RANGE: - always use a comma to separate the port limits; - warn about old syntax with space as separator, then convert it; - bail out on unexpected characters in the port range
• example site-info.def includes needed information for all ATLAS VOMS servers
• correction of the function 'config-vomses' for VOMSES strings containing spaces in some attributes
• corrected utils/convert_fqan for wildcards arguments
• config_ldconf adds also /opt/lcg/lib64

yaim-clients

This update includes:

• YAIM can configure the SAGA adapters if a configuration variable, CONFIG_SAGA is set to 'yes' in site-info.def or services/glite-ui[_tar]. By default configuration of SAGA is not enabled.

Two new variables may also be defined for use during the saga configuration. If not explicitly set they will have the defaults below:

SAGA_LOCATION=${GLITE_EXTERNAL_ROOT}/usr/local 

JAVA_SAGA_LOCATION=${GLITE_EXTERNAL_ROOT}/usr/local

Known issues

As with all glite-UI releases the correct way to update from a previous (RPM) based release is to use "yum groupupdate glite-UI".

If a "yum update" is done on a previous version of the node while the glite-UI repository is enabled a partial update of the UI will happen. To complete the update it becomes necessary to do:

yum -y remove glite-lb-client glite-service-discovery-api-c glite-wms-ui-configuration

yum -y groupupdate glite-UI