gLite 3.1
glite-TORQUE_client - Update to version 3.1.0-2
|
| Date |
12.11.07 |
| Priority |
Normal |
Description
New TORQUE/MAUI Version
It is expected that this torque (2.1.9-4) will work with the previous
EGEE released version (2.1.6-1cri_sl3_2st) if it is convenient to be
deployed or installed in a mixed version mode of pbs_server, pbs_mom
or client commands.
Maui 3.2.6p19-4 is built with a shared key across all architectures.
This was not previously the case and all builds had their own random key.
Subsequently a 32bit build of maui-client will now talk to a 64bit build
of maui-server.
After install verify that pbs_server, pbs_mom and maui have been restarted
everywhere. For the pbs_mom restarts the momctl utility in the torque-server
rpm can be utilized.
IMPORTANT NOTE, workaround required: /var/spool/maui/maui.cfg permissions should be 0644.
Additional issues:
- glite-TORQUE_utils: "... -n TORQUE_utils" should now be used to indicate the configuration of this node type with yaim.
- glite-TORQUE_utils meta-package should be installed together with a Computing Element to serve torque batch system.
glite-yaim-core
The new version of glite-yaim-core (4.0.1-6) includes a series of new changes and several bug fixes.
New features:
- YAIM 4.0.1 offers now the following new options:
-- explain : Doesn't perform configuration but explains what the functions are doing by printing out the comments found inside them.
-- available : Prints out the available configuration targets.
-- debug : defines a loglevel, which overwrites the value of YAIM_LOGGING_LEVEL defined in site-info.def. Values: 1-7
- A warning message is printed out when the glite CE configuration is called. This version of yaim does no longer configure the glite CE since it's not
deployed in production.
- Special comments have been added to most functions to allow for the 'explain' option of the yaim command.
- Only SE_castor is now configurable from node-info.def. All the other node types distribute their configurations in the corresponding yaim module.
- GLITE_LOCATION_VAR, GLITE_LOCATION_LOG and GLITE_LOCATION_TMP are now defined by default in site-info.post
- convert_fqan is now safe against FQANs having no leading "/"
- config_gip has been modified to support the new 3.1 VOBOX
- config_initd has been improved
- Added support in config_mkgridmapdir to read grid/groupmapfile from env variables defined in <node-type>.pre
Removed features:
- config_glite_env just now deletes the old /etc/profile.d/gliteenv.sh since now all the environment should be defined in grid-env.sh
- config_gip_scheduler_plugin is now distributed in yaim lcg CE.
site-info.def changes:
- The following variables have been removed from site-info.def: RB_RLS
- The following variables are new in site-info.def: DPM_INFO_USER and DPM_INFO_PASS
- Variable SITE_HTTP_PROXY is commented out by default in site-info.def.
- Fix for bug #29403 where variable BATCH_LOG_DIR is defined again in site-info.def instead of BATCH_SPOOL_DIR.
- The default value of BDII_HTTP_URL has changed to http://lcg-bdii-conf.cern.ch/bdii-conf/bdii.conf and a comment has been included to check that the URL is actually correct.
Known issues:
- Fix for bug #27146 -> The implemented fix is not very clean and it will be improved in a future release. Read the bug comments for more details.
- Fix for bug #29403 -> Although BATCH_LOG_DIR has been reintroduced in site-info.def, it is not mentioned in any 'requires'. This has to be fixed.
glite-yaim-clients
The new version of glite-yaim-clients (4.0.1-1) contains:
- the new configuration for the 3.1 VOBOX.
- Fix for patch #1257 in the 3.1 UI.
- Fix for GGUS ticket #10533 in 3.1 WN.
- Fix for bug #28809 in the TAR UI.
The TORQUE clients are now distributed in its own yaim module called glite-yaim-torque-client.
The way to configure the TORQUE clients is:
yaim -c -s site-info.def -n glite-WN -n TORQUE_client
The metapackage TORQUE_client should have a dependency in the glite-yaim-torque-client module.
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 |
|
#25033 |
BDIIs could publish themselves and even better what their view is. |
|
#25142 |
maui-private.cfg |
|
#27146 |
YAIM overwrites /etc/java/java.conf |
|
#27356 |
PPS tarUI: X509_CERT_DIR |
|
#27694 |
config_mkgridmap adds non-pool accounts to gridmapdir |
|
#28020 |
CE_OS_ARCH should be required by config_gip in yaim-3.1.1 |
|
#28058 |
config_users doesn't create home directories for users |
|
#28240 |
config_gip default values for ldif files too small |
|
#28314 |
bdii: openldap 2.2 only uses v3 |
|
#28317 |
C-shell environment setup |
|
#28656 |
Torque start failure does not stop yaim |
|
#28807 |
config_crl should only do something if no central certs |
|
#28809 |
UI_TAR should set X509_VOMS_DIR to other than default if wanted |
|
#29247 |
LFC_oracle doesn't need oracle-instantclient-jdbc |
|
#29300 |
yaim configuration should define GLOBUS_LOCATION to point to right globus |
|
#29403 |
BATCH_LOG_DIR variable in site-info.def undefined |
|
#29716 |
There is a possible vulnerability in pbs-mom |
|
#29780 |
Maui Fairshare does not work with group and %fairshare. |
|
#29878 |
YAIM could not correctly configure GLOBUS_TCP_PORT_RANGE |
Updated rpms
The RPMs can be updated using yum via
Service reconfiguration after update
Service must be reconfigured.
Service restart after update
Service must be restarted.
How to apply the fix
- Update the RPMs (see above)
- Update configuration (see above)
- Restart the service if necessary (see above)
|
|
