gLite 3.1
glite-PX - Update to version 3.1.24-0
|
Date |
31.08.2009 |
Priority |
Normal |
Description
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
New version of yaim core
- 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".
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 |
#33909 |
[ yaim-core ] Add configurable timeouts to the BDII |
#33936 |
[ YAIM ] remove JAVA_HOME definition |
#40208 |
[ YAIM ] LCG_GFAL_INFOSYS variable is defined in two places |
#44820 |
[ yaim-core ] The lcg-cp parallel data transfer failed on UI_TAR installed gLite-UI 3.1 nodes |
#45269 |
[ yaim-core ] yaim only recognizes the groups.d dir structure for a restrict set of nodes |
#45418 |
[ yaim-core ] Check grid-env.sh exists if -r option is used |
#46194 |
[ yaim-core ] YAIM config_crl should check for /usr/sbin/fetch-crl |
#46369 |
[ yaim-core ] Remove verify-proxy from lcmaps config file for gridftp |
#48206 |
[ yaim-core ] YAIM defines a default for JAVA_LOCATION |
#48452 |
[ yaim-core ] WN should not define GLOBUS_TCP_PORT_RANGE |
#48932 |
[ yaim-core] output is not helpful when a conf target is wrongly stated |
#48991 |
[ yaim-core ] needed to change config_edgusers |
#49017 |
[ yaim-core ] configuration changes for new trustmanager and util-java |
#49464 |
[ yaim-core ] configure gridview only if it's installed |
#49575 |
[ yaim-core ] MYPROXY_TCP_PORT_RANGE can be deleted |
#49803 |
[ glite-yaim-core ] objectClass 'GlueTop' not allowed |
#49831 |
[ yaim-core ] /opt/edg/var/info should still be created by YAIM |
#50735 |
[ yaim-core ] queue_GROUP_ENABLE fails for "/vo" FQAN |
#52885 |
bug in config_gip_vo_tag of glite-yaim-core-4.0.7-9 |
Updated rpms
The RPMs can be updated using yum via
Service reconfiguration after update
Service must be reconfigured.
Service restart after update
Not needed.
How to apply the fix
- Update the RPMs (see above)
- Update configuration (see above)
- Restart the service if necessary (see above)
|
|