Description

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-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".

Fixed bugs

Updated rpms

The RPMs can be updated using yum via

• via apt: yum update
• or via a download from:
  
  http://glitesoft.cern.ch/EGEE/gLite/R3.1/glite-LSF_utils/sl4/i386/RPMS.updates/

Service reconfiguration after update

Not needed.

Service restart after update

Not needed.

How to apply the fix

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