05.11.2008 - 3.1 Update 59

glite-WN, glite-UI, glite-VOBOX

New version of lcg-infosites:

The new patch is solving the bug 37572. it allows therefore the query to multiple BDIIs

28.10.2009 - 3.1 Update 58

glite-FTS_oracle, glite-FTA_oracle, glite-FTM, glite-WN, glite-UI, glite-VOBOX

• SRM-gridftp split
• Logging to syslog according to Middleware Security Audit Logging Guidelines
• Logging IP addresses in SRM calls
• Removed obsolete commands: glite-transfer-placement-submit and glite-transfer-discovery
• Added site group management tools: glite-transfer-group-addmember glite-transfer-group-list glite-transfer-group-removemember
• Added channel management methods for new channel parameters
• Merged transfer-api-c into transfer-cli.
• DB maintenance packages are part of the core FTS package: history, purge
• Compliant with the WLCG SRM MoU for spaces

glite-VOMS_mysql, glite-VOMS_oracle, glite-UI, glite-VOBOX

New version of VOMS Admin and Clients:

New VOMS Admin features:

The VOMS SAML codebase developed during the OMII project has been integrated into the codebase. Now VOMS Admin exposes a service, called VOMSSaml that can be used to obtain a SAML assertion containing signed VOMS attributes.

New VOMS Admin service properties:

• voms.aa.certificate
• voms.aa.key

The voms-admin-configure script has been extended to support flags to set these properties at configuration time.

Type voms-admin-configure --help for more information.

Updated dependencies:

VOMS SAML makes extensive use of the OpenSAML library, which requires a recent version of java xml parsing tools installed in your Java Runtime Environment.

VOMS Admin Server SAML attribute authority configuration handling:

Optional advanced parameters added.

This release introduces also automatic configuration of read-only access for anyone with a valid certificate (needed for the gridmap file generation on the relevant grid hosts). Applies only to newly created VOs.

Please check the service update pages at this link for more details

glite-CREAM, glite-FTA_oracle, glite-FTS_oracle, glite-LFC_mysql, glite-LFC_oracle, glite-PX, glite-SE_dpm_disk, glite-SE_dpm_mysql, glite-UI, glite-VOBOX, glite-VOMS_mysql, glite-VOMS_oracle, glite-WMS, glite-WN, lcg-CE

New version of lcg-vomscerts:

lcg-vomscerts-5.6.0 adds new cert for voms.fnal.gov and removes old certs for voms.fnal.gov, voms.cern.ch and voms-pilot.cern.ch

22.10.2009 - 3.1 Update 57 (rolled-back)

glite-FTS_oracle, glite-FTA_oracle, glite-FTM, glite-WN, glite-UI, glite-VOBOX

New version of FTS and Clients:

• SRM-gridftp split
• Logging to syslog according to Middleware Security Audit Logging Guidelines
• Logging IP addresses in SRM calls
• Removed obsolete commands: glite-transfer-placement-submit and glite-transfer-discovery
• Added site group management tools: glite-transfer-group-addmember glite-transfer-group-list glite-transfer-group-removemember
• Added channel management methods for new channel parameters
• Merged transfer-api-c into transfer-cli.
• DB maintenance packages are part of the core FTS package: history, purge
• Compliant with the WLCG SRM MoU for spaces

glite-VOMS_mysql, glite-VOMS_oracle, glite-UI, glite-VOBOX

New version of VOMS Admin and Clients:

New VOMS Admin features:

The VOMS SAML codebase developed during the OMII project has been integrated into the codebase. Now VOMS Admin exposes a service, called VOMSSaml that can be used to obtain a SAML assertion containing signed VOMS attributes.

New VOMS Admin service properties:

• voms.aa.certificate
• voms.aa.key

The voms-admin-configure script has been extended to support flags to set these properties at configuration time.

Type voms-admin-configure --help for more information.

Updated dependencies:

VOMS SAML makes extensive use of the OpenSAML library, which requires a recent version of java xml parsing tools installed in your Java Runtime Environment.

VOMS Admin Server SAML attribute authority configuration handling:

Optional advanced parameters added.

This release introduces also automatic configuration of read-only access for anyone with a valid certificate (needed for the gridmap file generation on the relevant grid hosts). Applies only to newly created VOs.

Please check the service update pages at this link for more details

glite-AMGA_oracle, glite-AMGA_postgres, glite-BDII, glite-CREAM, glite-FTS_oracle, glite-LB, glite-LFC_mysql, glite-LFC_oracle, glite-MON, glite-PX, glite-SE_dcache_admin_gdbm, glite-SE_dcache_admin_postgres, glite-SE_dcache_info, glite-SE_dpm_disk, glite-SE_dpm_mysql, glite-VOBOX, glite-VOMS_mysql, glite-VOMS_oracle, glite-WMS, lcg-CE

New version of the BDII:

This updated version of the BDII contains support for GLUE 2.0 information. The GLUE 2.0 LDAP schema file has been added to the glue-schema package and the slapd.conf file used by the BDII has been modified to include the new file. A new root o=glue has been added in the slapd.conf file and the BDII has be modified to manage multiple roots.

glite-CREAM, glite-FTA_oracle, glite-FTS_oracle, glite-LFC_mysql, glite-LFC_oracle, glite-PX, glite-SE_dpm_disk, glite-SE_dpm_mysql, glite-UI, glite-VOBOX, glite-VOMS_mysql, glite-VOMS_oracle, glite-WMS, glite-WN, lcg-CE

New version of lcg-vomscerts:

lcg-vomscerts-5.6.0 adds new cert for voms.fnal.gov and removes old certs for voms.fnal.gov, voms.cern.ch and voms-pilot.cern.ch

06.10.2009 - 3.1 Update 56

glite-CREAM

• Advisory 55615
• Advisory 55616

• Migration to voms-api-java. This also means that the VOMS server host certs are not required anymore in the CREAM CE node (the /etc/grid-security/vomsdir/*/*.lsc files are sufficient)
• First release of new BLAH blparser for LSF and PBS/Torque (use of batch system status/history commands instead of parsing the log files). However due to some problems found after the first certification, it is suggested to keep using the old parser (i.e. BLPARSER_WITH_UPDATER_NOTIFIER=false, which is the default) which is still fully supported
• IPv6 support for BLAH

• Fix for a problem with purge (not deleting the job sandbox dir in some cases)
• Fix for a problem for which there could be at most 32000 active jobs per user
• Fix for a problem for which the produced accounting logs (used by APEL and DGAS) was not properly filled if the CREAM CE is not the Torque server

22.09.2009 - 3.1 Update 55

glite-WMS

• Improvements in performance and scalability
• Much less use of memory
• Use of jobdir instead of filelist as input for ICE

glite-UI, glite-WN, glite-VOBOX

31.08.2009 - 3.1 Update 54

glite-MON, lcg-CE, glite-TORQUE_utils, glite-CONDOR_utils, glite-SGE_utils, glite-LSF_utils, glite-CREAM

• Publisher OutOfMemory error when publishing large amounts of records. APEL will now publish records in batches instead of selecting all records in one go. However, there is still an out of memory error when processing large numbers of grid_jobmap files. In that case, follow this recipe.
• The value for the ExecutingCE in the accounting records will be taken from the configuration file in each CE and not from the log files, which will stop sites having records with the hostname for the scheduler.
• APEL database schema changes. Some of the fields in the APEL local database have been changed. The APEL parser needs to be run at least once with the following setting enabled to have the changes applied: <DBProcessor inspectTables="yes"/>
• YAIM changes:
  • There's a new variable APEL_PUBLISH_LIMIT, in order to be able to configure the number of records to be selected. Default value is 300000.
  • A number of outstanding YAIM bugs have been addressed.
  • The configuration no longer attempts to fix problems in the tomcat installation as this code was rather fragile. According to the precise version of tomcat you may need to set JAVA_HOME yourself in the /etc/tomcat/tomcat5.conf file.
  • YAIM no longer assumes that you have one tomcat service called tomcat5. You can set the YAIM variable TOMCAT_SERVICE if needed. It defaults to "tomcat5". The corresponding entry in /etc/sysconfig is modified.
  • ulimit is no longer set by modifying /etc/init.d/rc.d/tomcat5 but is set by a line at the end of the /etc/sysconfig/ file. This file is sourced by the init.d script.
  • YAIM sets up the glite-info-provider-service to make the R-GMA status available via the BDII.
  • There is an known problem with the version of urllib used by the MON gip plugins, where the provider does not return the correct information in the case where the site uses a HTTP proxy. The problem is due to an issue in the OS vendor supplied urllib. A workaround, which requires a minor modification to YAIM /opt/glite/yaim/functions/config_info_service_mon. This fix unsets the https_proxy variable for the duration of running the GIP scripts. Full details may be found in Bug 40764.

glite-AMGA_oracle, glite-AMGA_postgres, glite-BDII, glite-CONDOR_utils, glite-CREAM, glite-FTA_oracle, glite-FTM, glite-FTS_oracle, glite-HYDRA_mysql, glite-LB, glite-LFC_mysql, glite-LFC_oracle, glite-LSF_utils, glite-MON, glite-MPI_utils, glite-PX, glite-SE_dcache_admin_gdbm, glite-SE_dcache_admin_postgres, glite-SE_dcache_info, glite-SE_dcache_pool, glite-SE_dpm_disk, glite-SE_dpm_mysql, glite-SGE_utils, glite-TORQUE_client, glite-TORQUE_server, glite-TORQUE_utils, glite-UI, glite-VOBOX, glite-WMS, glite-WN, lcg-CE

• Configuration changes needed for a new version of trustmanager and util-java. These changes are included in a new function not used yet by any yaim module. The idea is that any service configuring tomcat will use this function in the future.
• The creation of users specifying a home directory wasn't working. This is fixed now.
• GLOBUS_TCP_PORT_RANGE is not defined for the WN and it's properly defined for the TAR UI. MYPROXY_TCP_PORT_RANGE is not defined any more.
• YAIM checks whether fetch-crl is installed and fails otherwise.
• groups.d/ structure is now available for all the node types.
• gridview is configured only if it's installed.
• The verify-proxy plugin is not present in the lcmaps configuration for gridftp.
• /opt/edg/var/info directories for the software tags are again created by yaim.
• New site-info.pre and .post variables:
  • BDII_ARCHIVE_SIZE: It is the number of dumps of the database to keep for debugging purposes. Default is 0.
  • BDII_BREATHE_TIME: It is the time in seconds between updates of the bdii. Default is 120.
  • BDII_PASSWD: This is the password for the LDAP database used by the bdii. Default is $(mkpasswd -s 0).
  • BDII_READ_TIMEOUT: It is the amount of time to wait until an information is assumed to have timed out. Default is 300.
  • CONFIG_GRIDMAPDIR: It enables or disables the creation of the gridmap file. If set to yes, it creates it. If set to no, it doesn't create the gridmap file. Default is yes.
  • TRUSTMANAGER_CRL_UPDATE_INTERVAL: This variable is used in the trustmanager configuration and it defines how often the X509_CERT_DIR is polled for changes in the files. It's a number followed by h,m or s time units. Default is 2h.
  • TOMCAT_HOSTCERT_LOCATION: path of the tomcat host certificate. Default is /etc/grid-security/tomcat-cert.pem.
  • TOMCAT_HOSTKEY_LOCATION: path of the tomcat host key. Default is /etc/grid-security/tomcat-key.pem.
  • TOMCAT_USER: tomcat user. Default is "tomcat".

glite-UI, glite-VOBOX, glite-WN, glite-SE_dcache_admin_gdbm, glite-SE_dcache_admin_postgres, glite-SE_dcache_info, glite-SE_dcache_pool

glite-UI, glite-VOBOX, glite-WN

glite-BDII, glite-CREAM, glite-FTS_oracle, glite-LB, glite-HYDRA, glite-LFC_mysql, glite-LFC_oracle, glite-SE_dpm_mysql, glite-VOBOX, glite-WMS

lcg-CE, glite-WMS, glite-SCAS, glite-GLEXEC_wn, glite-CREAM, glite-VOBOX

lcg-CE

This version fixes an issue in globus-gma that only shows up when CE suffers from overload, batch or file system malfunction. In such conditions some pool account may become irresponsive to jobmanager requests. It will cause globus-gma child processes to be killed by the parent one after a time-out (usually 60 seconds). E.g. if a bad account has 1000 associated jobs (running or queued) it will take globus-gma 17 hours to dig through and will prevent all other accounts from receiving job status updates during this time, effectively bringing the whole CE down. There's a logic in globus-gma to avoid this: after a configurable number (4 by default) of consecutive timeouts for a single account all remaining jobs belonging to it will be skipped till the next poll cycle to allow other possible healthy accounts to receive job status updates. Unfortunately this logic didn't work before as expected because of one extra line in the code. It was hard to catch this issue as it cannot be reproduced during certification/testing with a healthy CE.

glite-LSF_utils

• The new version doesn't replace the configuration file in /opt/glite/etc but creates the new template as rpmnew file.
• A new parameter can now be specified in the configuration file: LSF_CE_PRODUCTION_STATUS. It can have two possible values: "Production" or "Preproduction". If the CE state is taken from the batch system, this value is taken and reported in the information system. This allows to embed preproduction CEs in production environments.

glite-GLEXEC_wn

All the detailed information about these scripts is here. Background information: The gLExec wrapper scripts are able to preserve the process environment variable in a safe way. As a security measure gLExec will wipe all environment variables from the process to avoid tampering or exploitation. This has been a struggle for Pilot Job Framework (PJF) developers to be able to overcome this security measure. Each PJF would have to come up with their own solutions to be able to preserve the environment variables which are used a a form of global variable space, paths to specific software areas, or other unknown use cases.To help the VOs we've come up with these scripts to have a easy to use, uniform and supported way of preserving the environment variable between the users contexts in a safe way.

24.08.2009 - 3.1 Update 53

glite-WMS, glite-UI, glite-VOBOX, glite-WN

What's WMS 3.2 in gLite 3.1?: The new WMS has version 3.2 within the WMS project. This is an internal version that shouldn't be confussed with gLite 3.2. The first release of WMS 3.2 is available in gLite 3.1 and corresponds to glite-WMS 3.1.20-0 in the gLite repository.

This update contains a new release of the WMS which is a complete redesign of the service. For a summary of the changes introduced in this version, please check these web pages:

• gLite WMS 3.2 project page
• Release notes of the new version prepared by the WMS development team.

• WMS Known issues
• YAIM WMS Known issues

glite-CREAM, glite-LB, lcg-CE, glite-UI, glite-VOBOX, glite-WMS, glite-WN

This LB update provides fixes for known issues identified since the release of the previous update. The following text gives an overview of modules and respective fixes.

• client: fix edg_wll_NotifDrop prototype.
• client-interface: fix edg_wll_NotifDrop prototype.
• common: fix bug #35770.
• logger: support chconfig in startup scripts and proper kill signal handling.
• proxy:s upport chconfig in startup scripts.
• server:
  • Support for chconfig in startup scripts
  • Support for JP importer in startup scripts
  • Support for variant DN certificates
  • Recalculate subjob states after DB version upgrade
  • Ignore reseource_usage events when computing job states
  • Fix sequence code processing for Change ACL events
  • Reflect job conditions while processing queries for events

29.07.2009 - 3.1 Update 52

glite-CREAM

• Fixed a problem concerning publication in the BDII of FQAN voviews and DENY tags.
• CREAM and CEMon services publish themselves in the Information Service.
• Support for new blparser for LSF and PBS/Torque (not released yet) implemented. Since the new parser has not been released yet, don't try it.
• Implemented a workaround for the LB-locallogger restart problem.
• INNODB is not set anymore as default mysql engine (since CREAMDB tables are created specifying that INNODB should be used). Clean up your etc/my.cnf if needed.
• Variable SE_MOUNT_INFO_LIST is now compulsory
• New variable BLPARSER_WITH_UPDATER_NOTIFIER to support the use of new blparser (with updater and notifier) or the old one (which parses the log files). Values are true or false, default is false..

glite-CREAM, glite-FTA_oracle, glite-FTS_oracle, glite-LFC_mysql, glite-LFC_oracle, glite-PX, glite-SE_dpm_disk, glite-SE_dpm_mysql, glite-UI, glite-VOBOX, glite-VOMS_mysql, glite-VOMS_oracle, glite-WMS, glite-WN, lcg-CE

• Adds next certificates for voms.cern.ch and voms-pilot.cern.ch
• Removes old certificate for lcg-voms.cern.ch

glite-WN

15.07.2009 - 3.1 Update 51

glite-UI, glite-WN, glite-VOBOX

• VOBOX service provider correctly publishes the supported VOs.
• FTS endpoint can be now specified by the user.

• GLITE_LOCAL_CUSTOMISATION_DIR: This is an optional variable to define a scratch area for pool accounts via EDG_WL_SCRATCH. For more information please check glite-WN-3.0.15-3 Update
• GLITE_SD_PLUGIN: Service discovery settings to determine the FTS endpoint. Possible values are: 1) file : look for the FTS endpoint in a static file specified in GLITE_SD_SERVICES_XML. 2) bdii : look for the FTS endpoint dynamically from the BDII. Both options can be specified. The first one is tried first. Default is "file,bdii".
• GLITE_SD_SERVICES_XML: Location of the FTS services.xml cache file. This has to be used in combination with GLITE_SD_PLUGIN="file,bdii". Default is "${INSTALL_ROOT}/glite/etc/services.xml".

glite-SE_dpm_mysql, glite-SE_dpm_disk, glite-FTA_oracle, glite-FTS_oracle, glite-WN, glite-UI, glite-VOBOX

• DPM gridftp v1.7.1-2: saves the calculated checksum (via gridftp CKSM) to the name server, e.g. for later reporting via srmLs. The dpm-gridftp is able to calculate Adler32, Crc32 and MD5 checksums.
• Improved the error reporting of 'dpm-drain'.
• Clear the saved namespace checksum, if file as changed.
• Using libvomsapi, instead of the deprecated libvomsc.
• Avoiding /etc/services for rfio port lookup (wrong value).
• rfio bugfixes and improvements
• The DPM/LFC sources, configuration and init scripts have been improved for portability to SL5, Debian, OS X and Solaris.

glite-LFC_mysql, glite-LFC_oracle, glite-WN, glite-UI, glite-VOBOX

• The LFC sources, configuration and init scripts have been improved for portability to SL5, Debian, OS X and Solaris.
• Two new methods have been added to the LFC server and the API: lfc_delreplicasbysfn() and lfc_registerfiles(), for the bulk removal or addition of entries.

glite-LFC_mysql, glite-LFC_oracle

14.07.2009 - 3.1 Update 50

glite-WN

New version of grid-cm-* packages to remove /opt/glite/lib/python/logging. This is to address GGUS ticket 50148, only happening in glite-WN version 3.1.31-0. In fact this private logging version was only ever required on SL3 and can cause problems for people using private python 2.5 versions with the supplied 2.3 versions.

06.07.2009 - 3.1 Update 49

lcg-CE, glite-WMS, glite-VOBOX, glite-CREAM, glite-SCAS

Both LCAS and LCMAPS exist in library form only. They need an eco system in which they can live. This used to be the gridftp for example and nowadays glexec is used. This also means that LCAS and LCMAPS are mostly shielded from the end user and that the interaction primarely goes through glexec.

From a site point of view there is the configuration of LCAS and LCMAPS and the end user should have no control over it. Other then that, there is not much more interaction required.

glite-SCAS

New Site Central Authorization Service (SCAS). SCAS is a Web Service that allows client programs to query for an authorization decision based upon user credentials to access a particular resource. For more information please check the service node page.

SCAS YAIM configuration
====================

For a description of the YAIM variables needed to configure the SCAS server please visit: SCAS configuration variables.

The command to configure SCAS using YAIM is:
./yaim -c -s site-info.def -n SCAS

lcg-CE, glite-SGE_utils

New version of the yaim module for the lcg CE containing configuration changes as requested in:

• The WN Working Group. See WN Working group wiki (Key item B)
• The Installed Capacity Document (page 13)

• Service provider configuration
• LDIF file fixes

• CE_OTHERDESCR: This YAIM variable is used to set the GlueHostProcessorOtherDescription attribute. The value of this variable MUST be set to: Cores=<typical number of cores per CPU> [, Benchmark=<value>-HEP-SPEC06] where <typical number of cores per CPU> is equal to the number of cores per CPU of a typical Worker Node in a SubCluster. The second value of this attribute MUST be published only in the case the CPU power of the SubCluster is computed using the Benchmark HEP-SPEC06.
• CE_CAPABILITY: This YAIM variable is a blank separated list and is used to set the GlueCECapability attribute. In particular, site administrators MUST define the following values: CPUScalingReferenceSI00=<referenceCPU SI00>; the reference CPU SI00 is the internal batch scaling factor used to normalize the GlueCEMaxCPUTime. The <referenceCPU SI00> is expressed in SI00. If internal scaling is not done this capability MUST be published and its value set to the minimum value of the corresponding SubClusters GlueHostBenchmarkSI00. Share=<VO>:<share>; this value is used to express specific VO shares if set. If there is no special share, this value MUST NOT be published. <VO> is the VO name and <share> can assume values between 1 and 100 (it represents a percentage). Please note that the sum of the shares over all WLCG VOs MUST BE less than or equal to 100. The syntax is CPUScalingReferenceSI00=value [Share=vo-name1:value [Share=vo-name2:value [...]]]
• SE_MOUNT_INFO_LIST: This YAIM variable is used to set the GlueCESEBindMountInfo attribute for each defined SE. The variable is a space separated list of SE hosts from SE_LIST with the export directory from the Storage Element and the mount directory common to worker nodes part of the Computing Element like SE1:export_dir1,mount_dir1. If any SE from SE_LIST doesn't support he mount concept, don't define anything for that SE in this variable. If this is the case for all the SEs in SE_LIST, put the value none. The GlueCESEBindMountInfo will be in both cases "n.a".

• CLUSTER_HOST: this variable must be set to CE_HOST for the time being. It's defined under INSTALL_ROOT/glite/yaim/defaults/lcg-ce.post.

lcg-CE, glite-BDII, glite-PX, glite-WMS, glite-VOBOX, glite-SE_dpm_mysql, glite-AMGA_oracle, glite-AMGA_postgres

glite-AMGA_oracle, glite-AMGA_postgres, glite-BDII, glite-CREAM, glite-FTS_oracle, glite-HYDRA_mysql, glite-LB, glite-LFC_mysql, glite-LFC_oracle, glite-MON, glite-PX, glite-SE_dcache_admin_gdbm, glite-SE_dcache_admin_postgres, glite-SE_dcache_info, glite-SE_dpm_mysql, glite-VOBOX, glite-VOMS_mysql, glite-VOMS_oracle, glite-WMS, lcg-CE

glite-WMS, glite-UI, glite-VOBOX

The ability to submit jobs to ARC CEs has been included in the WMS. Any ARC CEs that wish to be used this way will need to install the gLite runtime environment. The instructions for doing this can be found here. For more details please check the documentation in ARC-WMS

lcg-CE, glite-CREAM, glite-GLEXEC_wn, glite-VOBOX, glite-SCAS, glite-WMS

• Improved error codes
• Code cleanups prevent crashes. The most interesting ones are when having to work with secondary GIDs that are not shown with their groupname, because the machine can't resolve them.
• More distinct error message reporting, every problem that is not a 202 system error will be reported on the stderr. To prevent misuse a 202 system error is not written to stderr, it will only be readable in the gLExec log.
• Added glexec.conf option "use_lcas {yes,no}" to enable or disable LCAS. Could be good to use in SCAS setups.
• Restored glexec.conf option "lcmaps_get_account_policy = scas:voms:local". You can now use multiple LCMAPS policies and specifically configured LCMAPS policies.
• Default special group is 'glexec' and not 'apache' (not used due to usage of the whitelist function).
• Added glexec.conf option "target_lock_mechanism {flock,fcntl,disabled} to select the locking mechansim for the $GLEXEC_TARGET_PROXY (or its default) location. Requested by the CREAM-BLAH-gLExec team. The default is still flock, but you can also use fcntl or bypass it (not safe) completely, see also below.
• Added glexec.conf option "input_lock_mechanism {flock,fcntl,disabled} to select the locking mechansim for the $GLEXEC_SOURCE_PROXY (if set) location and GLEXEC_CLIENT_CERT. Requested by the CREAM-BLAH-gLExec team. The default is flock, but you can also use fcntl or bypass it (not safe) completely, see also below.
• Manpages are cleaned up and reflect the current state of gLExec.
• $SSL_CLIENT_CERT is not usable anymore as this is very error prone. Use GLEXEC_CLIENT_CERT instead.
• The $GLEXEC_MODE="lcmaps_verify_account setting is disabled. This deprecated functionality is not used, functioned badly and is not supported in all the LCMAPS plugins.
• New scas-client plug-in
  • The SCAS Client will properly be able to work now with root-squashed enabled network filesystems, by lowering its effective Unix credentials to the calling user. This will allow for the SCAS Client to read in the certificate and private key with the proper credentials (similar to the gLExec code).
  • The "--endpoint <url>" option can be set multiple times in the lcmaps.db file. The maximum amount of endpoints configurable is 32.
  • New option is "--endpoint-strategy round-robin|round-robin-random-start|random": The endpoint strategy tells the client in which order the configured endpoints should be tried to be contacted. With round-robin the list of endpoints will be tried from top to bottom as written in the lcmaps.db file. The option round-robin-random-start will follow the list of endpoints as written in the lcmaps.db file, but it will randomly start somewhere in the list of end-points. The random option will randomly choose an endpoint to try. When unlucky the same endpoint could be tried twice. This is true pseudo-random. The round-robin-random-start is made default. This will automagically provide a load balancing effect by randomly selecting a configured endpoints.
  • New option: "--retry <0-9+>"This will alter the retry count when interacting with an SCAS endpoint. By default each endpoint is tried twice by default before any other endpoint is tried (this excludes the various TCP/IP layer retries that are always performed at a lower level). This option can alter this default behavior. It can be set to any number as long as its more than 1. Between two tries there is a small amount of (random) time of delay build-in.

25.06.2009 - 3.1 Update 48

glite-WN

grid-cm-* packages provide worker node configuration monitoring. For more information, please check The Worker Node Client Documentation. In this document you can find the instructions about how to disable the publisher, if needed.

glite-AMGA_oracle, glite-AMGA_postgres, glite-CREAM, glite-FTA_oracle, glite-FTS_oracle, glite-LB, glite-LFC_mysql glite-LFC_oracle, glite-MON, glite-PX, glite-SE_dpm_disk, glite-SE_dpm_mysql, glite-UI, glite-VOBOX, glite-VOMS_mysql, glite-VOMS_oracle, glite-WMS, glite-WN, lcg-CE

• Warnings and errors are now counted. If there are errors in the download or verification process for one or more CRLs, the exit status will be 1; if there are errors in the local setup or in the script invocation, the exit status will be 2.
• The installed CRLs no longer have the textual representation of the CRL, but only the PEM data blob, thus reducing IO and memory requirements.
• the CRL aging threshold is now set by default to 24 hours. The previous default was 0. The CRL aging threshold is set in the config file using CRL_AGING_THRESHOLD=<xx>, or with the "-a" command-line argument.
• Default network timeouts reduced to 10 seconds (was 30) and retries to 2.
• Added caching and conditional downloading. When CACHEDIR is set, the original downloads are preserved and wget timestamping mode enabled. When the content did not change, only the timestamp on the installed CRL is updated. If SLOPPYCRLHASHES is set, the has is calculated based on the name of the crl_url file, otherwise it is taken from the CRL itself.
• The CACHEDIR must be exclusively writable by the user running fetch-crl.
• Setting CACHEDIR significantly reduced the bandwidth used by fetch-crl.
• Added RESETPATHMODE setting in sysconfig. It defines whether or not to set re-set $PATH to "/bin:/usr/bin" before start. The search for OpenSSL may be done based on the old path. yes=always replace; searchopenssl=search for openssl first and then reset; no=keep original path, whatever that me be (may be empty if called from cron) Default="yes". This replaces the hard-coded path in the tool!
• Hidden "FORCE_OVERWRITE" option now has a regular name. This is backwards-compatible. Set FORCE_OVERWRITE=yes if you want files overwritten that have a CRL-like name and ought to have CRL content, but currently do not.

glite-SE_dcache_info, glite-SE_dcache_pool, glite-SE_dcache_admin_gdbm, glite-SE_dcache_admin_postgres, glite-VOBOX, glite-WN, glite-UI

• Info service and info provider
• Permanent registration of deleted files
• SRM Client Tools
• Log4j Runtime User Interface
• dCacheConfigure Script

lcg-CE, cream-CE

Following a requirement of the WN Working Group, the new lcg-info-dynamic-software GIP plugin now supports an additional method to load software tags for SubClusters. Software tags can now be configured in:

• in /opt/glite/var/info/<vo>/<vo>.list (old method)
• in a per-SubCluster list /opt/glite/var/info/<SubCluster>/<vo>/<vo>.list (new and recommended method).

Note: For clean installations of cream CE and lcg CE, or when adding a new VO: YAIM creates /opt/glite/var/info/<SubCluster>/<vo>/<vo>.list and, due to bug 49831, /opt/edg/var/info/<vo>/<vo>.list is no longer created. It will be created again in the upcoming yaim-core 4.0.8-7 release. For a workaround see known issues pages of lcg CE and cream CE.

• tags configured in /opt/edg/var/info/<VO> are added to all SubClusters.
• tags configured in /opt/glite/var/info/<SubCluster>/<vo> Are added to the particular subclusters.

glite-VOBOX

This patch is just for enabling the installation of CREAM and CEMon client in the VOBOX (besides the UI and the WMS). The specified RPMs are the one currently in production (patch #2845)

16.06.2009 - 3.1 Update 47

glite-AMGA_postgres, glite-AMGA_oracle, glite-SE_dpm_mysql

• The AMGA service is now published in the Information System by using the service provider.
• YAIM improvements.

lcg CE

• Fix for GGUS ticket 42981
• Workaround for Condor-G bug where Condor-G does not distinguish between different VOMS groups, roles or VOs when the proxies have the same DN (bug #40359).

glite-WN

glite-VOBOX, glite-UI, glite-WN

• gfal_open segfaults on "connection refused". Tracked in #51230

glite-VOBOX, glite-UI, glite-WN

• warning in case of mismatch between command line VO and proxy VO
• asynchronous srmLs support (dCache)
• new synchronous function gfal_bringonline() with retrying/polling mechanism
• new lcg-get-checksum command (and corresponding API function)
• SRMv2 is now used by default if available
• support of checksum verification during file transfers

• When copying a local file to an SE, checksum checking does not work. (SE -> local and SE -> SE works OK). Will be fixed for the next release.
• The lcg-rf commmand no longer prints the guid on success. The "--verbose" option has to be used in order to obtain the value. See bug #50548

12.05.2009 - 3.1 Update 46

glite-SE_dpm_mysql, glite-SE_dpm_disk, glite-LFC_mysql, glite-LFC_oracle, glite-FTA_oracle, glite-FTS_oracle, glite-WN, glite-UI, glite-VOBOX

The new version of DPM and LFC contains a series of new features and bug fixes. See the packages described below for more details.

Known Issue

bug #49369: There is a known problem when configuring DPM 1.7.0-6 using YAIM. For more details please visit the DPM disk and the DPM mysql.

LCG-DM 1.7.0-5

• srmCopy has been fully implemented
• WLCG SRM MoU requirements:
  • support for multiple groups on spaces
  • SRM2.2 srmReleaseFiles can be used without a requestToken
  • srmLs can return information about the spaces in which a file resides
• new dpm-listspaces CLI, which will also serve as information provider

• /opt/glite/etc/gip/provider/glite-info-dpm-space-tokens-provider
• /opt/glite/libexec/glite-info-dpm-space-tokens

• added ADLER32 and CRC32 checksum algorithms to CKSM handler
• Fixes #42623: DM custom packager creates rpms with invalid name

• Fixes #42623: DM custom packager creates rpms with invalid name
• gSOAP 2.7.10 has introduced a virtual destructor, which inserts a pointer to the VMT at the beginning of the 'soap' structure, making the C and C++ versions of the code binary incompatible, so we need to build C++ flavour of the libraries as well with _cpp suffix.
• Added new function, export_delegated_credentials(), to make a delegated credential token available in memory suitable for storage and later reuse by the user.
• Removed some spurious trailing newlines from error messages.
• Fixed descriptor and connection leak on the client side when the authenitcation negociation to a server fails.
• Enhanced some error messages to cover more of the error message recommendations in bug #35320.

• dpm-httpd-cmd, dpm-httpd-cp: fixing X509 environment variable names X509_USERCERT->X509_USER_CERT ... similiar X509_USERKEY & X509_USERPROXY
• Checking the default proxy location in /tmp/x509up_u* as well.

• Fixes #42623: DM custom packager creates rpms with invalid name.
• Improving stability: initialise a couple of pointers in case DPM calls fail
• fix in logrotation script to check if dpm-xrd is actually configured before sourcing the config file.

glite-SE_dpm_mysql, glite-SE_dpm_disk, glite-LFC_mysql, glite-LFC_oracle, glite-WN, glite-UI, glite-VOBOX

This is an update of the DPM and LFC path fixing some outstading issues:

• Fix memory leak in dpm_get_max_get_lifetime()
• Correct problem with bug fix 40553 (dpm-drain)
• update dpm-listspaces to v1.3.1-4

glite-FTA_oracle, glite-FTS_oracle, glite-LB, glite-LFC_mysql, glite-LFC_oracle, glite-SE_dpm_disk, glite-SE_dpm_mysql, glite-UI, glite-VOBOX, glite-VOMS_mysql, glite-VOMS_oracle, glite-WMS, glite-WN, lcg-CE

New version of the VOMS Java APIs to fix some bugs. Please, check the list of bugs in the specific service update pages for more information.

glite-WMS

New version of WMS packages to fix bug #47040

29.04.2009 - 3.1 Update 45

glite-WN

Addition of the glite-wn-info command
============================

The glite-wn-info command is designed to be executed on the WN by a job submitter. It returns information about that worker node in a grid context. Initially the following in particular is supported:

$ glite-wn-info -n GlueSubClusterUniqueId MySubCluster

The unique GlueSubCluster the batch worker is located in is returned.

The configuration file default location is ${GLITE_LOCATION:-/opt/glite}/etc/glite-wn-info.conf.

However the hard coded location /etc/glite-wn-info.conf is also supported and will override $GLITE_LOCATION/etc/glite-wn-info.conf. This last configuration is particularly useful to sites working with the a TAR_WN and allows them to configure their WNs individually.

YAIM support for glite-wn-info:

• A new function, config_wn_info, will create the configuration file needed by glite-wn-info. Please, check the description of the WN_LIST variable in the YAIM guide since a new syntax has been introduced to be able to configure glite-wn-info. More details in the relevant section of the YAIM guide.
• A new default YAIM variable has been introduced for the WN/TAR WN configuration to define the glite-wn-info configuration file. WN_INFO_CONFIG_FILE. Since a default value is provided, the sys admins don't need to worry about it unless they want a non standard configuration. More details in: section on WN variables in the YAIM guide.

glite-UI, glite-VOBOX, glite-WN

Major release of GFAL 1.11.4 and lcg_util 1.7.2
======================================

• failover to other replicas, if an SE is not available
• adjustable timeouts for each type of remote operation
• SULR canonicalization can be disabled (for VOs without BDII)
• improved Python interface (Posix I/O, error handling)
• checksum is displayed in lcg-ls
• accepting negative request ID (dCache)
• using single gridftp session (CASTOR)
• obsoletes RMC/LRC functionality (not removed yet)
• and a number of bug fixes
• lcg-del fails when specifying the LFN and the SE, a simple workaround consists in specifying the corresponding SURL.

glite-AMGA_postgres, glite-AMGA_oracle, glite-BDII, glite-CONDOR_utils, glite-CREAM, glite-FTA_oracle, glite--FTM, glite-FTS_oracle, glite-LB, glite-LFC_mysql, glite-LFC_oracle, glite-LSF_utils, glite-LFC_mysql, glite-LFC_oracle, glite-MON, glite-MPI_utils, glite-PX, glite-SE_dcache_admin_gdbm, glite-SE_dcache_admin_postgres, glite-SE_dcache_info, glite-SE_dcache_pool, glite-SE_dpm_disk, glite-SE_dpm_mysql, glite-SGE_utils, glite-TORQUE_client, glite-TORQUE_server, glite-TORQUE_utils, glite-UI, glite-VOBOX, glite-WMS, glite-WN, lcg-CE

Updates for YAIM
=============

This release contains an update for yaim clients and yaim core. Both have been updated from version 4.0.5 to version 4.0.7, but they contain also all the bug fixes made available in 4.0.6. The release pages only highlight the bugs fixed in yaim core 4.0.7. If you also want to know the list of bugs fixed in 4.0.6, please look at the list of attached bugs in the yaim core patch (#2636) and yaim client patch (#2757).

Known Issue

Bug #49831: After introducing the fix for Bug #45887, YAIM has stopped to create /opt/edg/var/info directories. This is a mistake since the version of lcg-tags that will be able to write in the new directory /opt/glite/var/info/<SubClusterUniqueId>/<vo> is released in Patch #2940 that hasn't been certified yet. Old directories need to be supported for a while. The following workaround is needed in fresh installations of the lcg CE and cream CE or when a new VO is added to an existing CE. Edit $INSTALL_ROOT/glite/yaim/functions/cofig_gip_vo_tag and add at the end the old code to create the /opt/edg/var/info directory. Visit the lcg CE and the cream CE known issues pages for the details.

• #43278: config_users is now always creating the cleanup-grid-accounts cron job, no matter if CONFIG_USERS is yes or no.
• #39389: WMS now limits concurrent GridFTP connections using a new variable, GRIDFTP_MAX_CONNECTIONS (described in the next section).

• UNPRIVILEGED_MKGRIDMAP: In case you want to create a grid-map file which only contains mappings to ordinary users. Values are 'yes' or 'no'. 'no' will create a grid-map file with special users as well, if defined in groups.conf. yes, will create a grid-mapfile containing only mappings to ordinary pool accounts. This variable is defined in site-info.pre. Default is 'no'. You can redefine it in your site-info.def.
• GRIDFTP_CONNECTIONS_MAX: Maximum number of simultaneous connections to the gridftp server. This variable is defined in site-info.pre. Default is '50'. You can redefine it in your site-info.def.
• BDII_LIST: This variable already appeared in the previous yaim core release 4.0.5-7. However, due to a bug it was recommened not to use it. It's an optional variable to define a list of top level BDIIs to support the automatic failover in the GFAL clients. The syntax is my-bdii1.$MY_DOMAIN:port1[,my-bdii22.$MY_DOMAIN:port2[...]]. Be aware that lcg-infosites doesn't work with multiple BDIIs. So it's better you don't define this variable if you need to use lcg-infosites. However gfal, lcg_utils, lcg-info and glite-sd-query work fine with multiple BDIIs.
• SE_MOUNT_INFO_LIST: This YAIM variable is used to set the GlueCESEBindMountInfo attribute for each defined SE. The variable is a space separated list of SE hosts from SE_LIST with the export directory from the Storage Element and the mount directory common to worker nodes part of the Computing Element like SE1:export_dir1,mount_dir1. If any SE from SE_LIST doesn't support the mount concept, don't define anything for that SE in this variable. If this is the case for all the SEs in SE_LIST, put the value 'none'. The GlueCESEBindMountInfo will be in both cases 'n.a'.
• CE_CAPABILITY and CE_OTHERDESCR: These variables affect cream CE and lcg CE and that's why they are included in the example site-info.def. However, they are currently not used until some modifications in the information system configuration are applyed in cream and lcg CE. They will be properly announced by then. You can ignore them for the time being.

• fetch-crl runs now on reboot. A init.d script has been created for it.
• Tomcat configuration is now defined in yaim core to be used by all the modules that need tomcat.
• grid-env.sh doesn't leave garbage in the environment. It's also possible to run the -r option in the yaim command without messing up the grid-env.sh file.
• Old lcas/lcmaps configuration files are no longer created in config_mkgridmap.
• Multiple BDIIs can now be defined for GFAL clients. See the section above for the description of BDII_LIST.
• Update of yaim clients in order to avoid duplication of PYTHONPATH/PERL5LIB definitions.
so that the grid environment has coherent values for 32bit and 64bit platforms.
• With the previous yaim core version, PYTHONPATH/PERL5LIB used to contain a mix of 32bit and 64bit grid libraries after configuring a node type (specially WNs). This is wrong since Python/perl, unlike the dynamic linker, seems not to be able to find the good library when 32bit and 64bit libraries appear in PYTHONPATH/PERL5LIB.The fix consists of:
  • If the machine is 64bit and middleware is 64bit, PYTHONPATH/PERL5LIB only contains 64bit paths.
  • If the machine is 64bit and middleware is 32bit, PYTHONPATH/PERL5LIB only contains 32bit paths.
  • If the machine is 32bit, PYTHONPATH/PERL5LIB only contains 32bit paths.
• Python version specific directories have also been added in PYTHONPATH when they are installed.
• A typo has also been fixed in config_mkgridmap so that the grid-map file generation for LFC and DPM works fine now.
• The .lsc files (files specifying the trusted VOMS servers with their DNs and CA DNs) are now created in the tarball configurations.
• VO SW tag directories are created now under /opt/glite/var/info/<SubClusterUniqueId>/<vo>. Two new variables are used CLUSTERS and CLUSTER_<cluster_name>_SUBCLUSTERS which, for the time being have a default value which is CE_HOST. Sys admins should not change this. There's a new software provider that will publish from old and new directories (not yet in production) and there's a new version of lcg-tags that will write in old and new directories (not yet in production). For the time being, this configuration change can be ignored until the new lcg-tags version is released to production. See the Known Issue described above.

14.04.2009 - 3.1 Update 44

glite-CREAM

Update of CREAM CE. The main changes are:

Configuration
==========

• A problem in BLAH configuration fixed in order to reduce the probability of jobs aborted for "killed by signal 15"
• Publications of VO software tags in a CREAM CE is now supported

• Fixed a "too many open files" problem triggered by the purge operation
• Fixed a memory leak in the BLAH Blparser for LSF
• Fixed some problems in the BLAH BLparser which caused its crash or its inability to send notifications to CREAM
• BLAH is started via a "master" process, which monitors and in case restarts the parser

glite UI, glite-WMS

Upgrade of CREAM and CEmon clients. The main changes are:

• Problem involved with staging of InputSandbox files fixed.
• It is now possible to use the CREAM client even if the relevant VO VOMS cert file is not installed in the clients, as requested by OSG.
• Support for some problems reported in IPv6
• Fixed some problems which prevented the build on sl5_x86_84

glite UI, glite VOBOX

Important fix for WMS clients:

• bug #48598: job submission fails when first WMS tried is draining !!

02.04.2009 - 3.1 Update 43

glite-UI, glite-WN, glite-VOBOX

    * New version of YAIM clients enabling configuration of Service Discovery (PATCH:2596)

glite-SGE_utils

    * New info dynamic plugin + YAIM utils
    * This update fixes a security issue. Please have a look at the corresponding advisory

glite-VOBOXglite infor provider service

    * New info dynamic plugin + YAIM utils

27.03.2009 - 3.1 Update 42

This update can be summarised as: new version of lcg-vomscerts, BDII, WN, FTS and FTA updates, and finally new version of VDT. Please check below for more details on the individual service updates and list of patches.

IMPORTANT NOTE: This update has priority HIGH for the lcg-vomscerts patch. The other patches have priority NORMAL.

glite-CREAM, glite-FTA_oracle, glite-FTS_oracle, glite-LFC_mysql, glite-LFC_oracle, glite-PX, glite-SE_dpm_disk, glite-SE_dpm_mysql, glite-UI, glite-VOBOX, glite-VOMS_mysql, glite-VOMS_oracle, glite-WMS, glite-WN, lcg-CE

- New version of lcg-vomscerts-5.4.0: it adds next certificate for lcg-voms.cern.ch (old one expires on 07/04/2009); and removes old certs of cclcgvomsli01.in2p3.fr and vo.racf.bnl.govi.

glite-BDII, glite-MON, glite-WMS, glite-LB, lcg-CE, glite-CREAM, glite-FTS_oracle, glite-LFC_mysql, glite-LFC_oracle, glite-SE_dcache_info, glite-SE_dpm_mysql, glite-VOMS_mysql, glite-VOMS_oracle, glite-PX, glite-VOBOX

- Upgrade of BDII. The main change is that the starting cache size used for the Berkeley Database in the BDII has been reduced from 1 GB to 50 MB. This should significantly reduce the memory footprint and still provide the necessary performance.

- DB_CONFIG now has "set_lk_max_locks 10000" (10k) to fix GGUS ticket 43230 ("gLite 3.1u34: lcg-cp failing on a BDII error in a MPI job")

glite-AMGA_oracle, glite-AMGA_postgres, glite-LB, glite-CREAM, glite-FTA_oracle, glite-FTS_oracle, glite-LFC_mysql, glite-LFC_oracle, glite-PX, glite-SGE_utils, glite-SE_dpm_disk, glite-SE_dpm_mysql, glite-UI, glite-VOBOX, glite-VOMS_mysql, glite-VOMS_oracle, glite-WMS, glite-WN, lcg-CE

- New version of VDT that introduces GridFTP2 support.

glite-WN

- Add Which as a dependency in the WN.

glite-FTS_oracle

- FTS job submission sometimes ends up with an invalid delegated proxy certificate in the FTS service, thus transfers will fail. This update fixes the FTS web service's delegation code that the delegated proxy certificates should not be corrupted.

The fix is transparent for the clients and there is no configuration change on the server side. One only needs to restart the FTS web service (Tomcat) after upgrading the glite-data-transfer-fts package.

id="3.1_Update_41">25.02.2009 - 3.1 Update 41

• Update to WMS 3.1 with numerous bug fixes. This update introduces as well a first version of the ICE plugin, which is functional but is still affected by several known issues. (list available at http://grid.pd.infn.it/cream/field.php?n=Main.ICEKownIssues)
  • Partially enables the WMS to submit to ARC CEs. For more details on this functionality visit the following URL, http://twiki.cern.ch/twiki/bin/view/EGEE/ARC-WMS.
  • Enabled submission to cream CE.
  • LDAP queries to fetch information in the Information Supermarket from the BDII can now be pre-filtered.
  • Added support for MPI jobs.
  • Ability to configure ExpiryPeriod and MatchRetryPeriod via YAIM.
  • New info-providers.
• New version of Cream CE. Among others this version provides:
  • fixes in particular BUG:44712 (Problem with lcmaps config file used for glexec).
  • Proxy renewal mechanisms have been modified following the approach used in the LCG-CE (it is not necessary anymore to have a set of open ports in the WN, as it was required before)
  • gJAF code included in org.glite.ce software i.e. removed the dependency on security.authz-framework-java
  • Several bug fixes in CREAM and CEMon (the CEMon ones were required in particular by VDT/OSG)

glite-BDII, glite-CREAM, glite-LB, glite-PX, glite-VOBOX, glite-WMS, glite-WN, lcg-CE

04.02.2009 - 3.1 Update 40

glite-CREAM, glite-FTA_oracle, glite-FTS_oracle, glite-LFC_mysql, glite-LFC_oracle, glite-PX, glite-SE_dpm_disk, glite-SE_dpm_mysql, glite-UI, glite-VOBOX, glite-VOMS_mysql, glite-VOMS_oracle, glite-WMS, glite-WN, lcg-CE

22.01.2009 - 3.1 Update 39

This update contains a new version of cream CE with a set of bug fixes. Please, check below for a summary of the most important changes and check in the cream CE update page for more details.

General information concerning all node types

glite-CREAM

15.12.2008 - 3.1 Update 38

This update contains multiple bug fixes in various areas. Please see below for a summary of the bug fixes, the individual service updates and list of patches.

glite-HYDRA

This is the first release of the new gLite Hydra service, which provides support for data encryption on Storage Elements. For more details on the hydra service check the glite-HYDRA_mysql update page. For more details on the hydra clients, check the glite-WN, glite-UI or glite-VOBOX update pages.

glite-PX

Improved myproxy server with a set of new features. Some of them:

- A new /etc/init.d/myproxy start up script is include in myproxy-config. This starts the service with the file /opt/glite/etc/myproxy-server.conf created by YAIM.
- The information provider now publishes much richer information about how the MyProxy service can be used.
- Some improvements have been done in the yaim myproxy module.

For more details check the glite-PX updates page.

glite-CREAM glite-FTS_oracle glite-MON glite-UI glite-VOBOX glite-VOMS_mysql glite-VOMS_oracle glite-WN lcg-CE

Update of glite-security-trustmanager rpm to have the right bouncycastle dependency

This is a simple fix for the bouncycastle libraries moved to a new location with bouncycastle 1.41. If the lcg CE is working, this change has no effect. When the lcg CE is next time reconfigured or if there is a clean install this change has an effect and will use the algorithm described in patch 2644. See original submission.

glite-CREAM glite-FTA_oracle glite-FTS_oracle glite-LFC_mysql glite-LFC_oracle glite-PX glite-SE_dpm_disk glite-SE_dpm_mysql glite-UI glite-VOBOX glite-VOMS_mysql glite-VOMS_oracle glite-WMS glite-WN lcg-CE

Upgrade of lcg-vomscerts-5.2.0:

- renamed all certificates with .pem suffixes because of bug 43395.
- removed expired certificate of voms.cern.ch

glite-CREAM lcg-CE glite-MON glite-SGE_utils glite-LFC_utils glite-CONDOR_utils glite-TORQUE_utils

Update of the APEL rpm to solve the new bouncycastle release problem.

For more details on the update instructions check the relevant servide update page.

glite-BDII glite-CREAM glite-FTS_oracle glite-LB glite-LFC_mysql glite-LFC_oracle glite-MON glite-PX glite-SE_dcache_admin_gdbm glite-SE_dcache_admin_postgres glite-SE_dcache_info glite-SE_dpm_disk glite-SE_dpm_mysql glite-VOBOX glite-VOMS_mysql glite-VOMS_oracle glite-WMS lcg-CE

Fix for GGUS ticket 44201 reporting that WMS does not match jobs which should match. The fix to this problem requires a change in the glue schema and therefore all the node types depending on the glue schema need to be updated.

28.11.2008 - 3.1 Update 37

glite-BDII, glite-SE_dcache_info and lcg-CE

26.11.2008 - 3.1 Update 36

glite-CREAM

glite-FTA, glite-FTS , glite-FTM

14.11.2008 - 3.1 Update 35

glite-SGE_utils

VOMS

glite-SE_dcache

./yaim -c -s site-info.def -n glite-SE_dcache_pool
./yaim -c -s site-info.def -n glite-SE_dcache_admin_postgres

• Error message of SrmSpaceManager command 'reserve' is misleading/useless.
• PinManager fills up log files with SQL queries pool <-> xrootd-door interaction.
• /opt/d-cache/bin/dcache script doesn't start replica manager ( upper case lower case issue)
• FTP Bug, cd (ftp CWD) does not work anymore (RT #3007) busy loop in SpaceSweeper
• gPlazma returns the same FQAN for the same DN even if the FQAN changes for subsequent requests.
• ftp clinet/server checksum format miss match
• undefied NAMESPACE did not fall back to pnfs
• 'rc onerror fail' doesn't work properly.
• gPlazma web interface to verify correct configuration.
• gsidcap failes if connected to two different doors.
• high pnfs load on srmrm
• Cannot open files with PROOF
• TChain from ROOT not working properly against xrootd
• lcg-ct returns Xrootd:// instead of root://
• SrmSpaceManager : 'ls -l' doesn't report access latency and retention policy of space tokens.
• etc/node_config interpreter problem fixed
• Number of database connections seems not be limited (PinManager)
• Various fixes/improvements in installation system (rt #3082, #3160, #3252)
• File couldn't be unpinned if the disk copy didn't exist any more.
• Pin Manager is leaking db connections
• Permission handler does not respects secondary GID
• Multiple GID support in gPalzma
• globus-url-copy doesn't use the WriteToken tag to select a Space Token
• Size of removed file(s) is not returned to the token using the chimera fs backend.
• (limited) Pin Time after a bring-online start at the time when file touches the disk after a restore.

GFAL

• Modify ETICS configuration file template to have dcache-client dependency for SLC4 and dcache-dcap for SLC5
• Experimenting with Python 2.5 support.
• Using --with-swig-prefix to really use ETICS relocated Swig dependency.
• Setting SWIG_LIB, because the one built into the 'swig' binary will not be valid in a userspace build, when Swig is relocated.
• Improve error message in case of soap error different from SOAP_EOF, and with no error string
• added missing libraries to python modules
• The proper fix was using the WITH_NOGLOBAL option instead.
• Added --with-python-location configuration option to be able to build with alternative Python versions.
• SOAP_FMAC3 and SOAP_FMAC5 are used in the generated gSOAP files, however stdsoap2.h uses SOAP_FMAC1, which has to be redefiened as well, when included in these sources. This should fix the SL5 build.

• Unregister LFN in lcg_cr function when not able to register SURL in this LFN
• Print error message in lcg_rep function when not able to register SURL in the LFN
• Experimenting with Python 2.5 support.
• Solving library dependies of python module
• using --swig-prefix instead of --swig-location
• Adding 'lib64' variations to the possible SWIG_LIB locations.
• Fixed 'if' tests in configure.ac: [] are removed by m4.
• Setting SWIG_LIB, because the one built into the 'swig' binary will not be valid in a userspace build.
• using relative path to stop libtool being too smart?
• added missing python libraries
• Added --with-python-location configuration option to be able to build with alternative Python versions.