gLite > gLite 3.1 > glite-PX > Update to glite-PX 3.1.16-0  
 
 

 

 

gLite 3.1

glite-PX - Update to version 3.1.16-0


Date 16.12.2008
Priority Normal

Description

The following fixes are released with glite-PX 3.1.16-0:

1. Improved myproxy server with a set of new features:

- A new /etc/init.d/myproxy start up script is include in myproxy-config. This starts the service using 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.
- Configuration improvements in the yaim myproxy module:

  • node-info.d files are now marked as config files.
  • man pages are created for yaim myproxy.
  • config_gip_service_release is also part of the function list.
  • myproxy specific variables are now distributed under services/glite-px.
Info provider configuration notes
=======================

- New function config_info_service_px that created dynamically the GlueService related information for MyProxy.
- Modification of config_gip_px which only performs cleaning tasks (delete previous ldif file for MyProxy).

MYPROXY Configuration notes
=======================

YAIM now creates a /opt/glite/etc/myproxy-server.conf file directly for use by the myproxy init.d start up script.

Extra YAIM variables are available:

GRID_AUTHORIZED_RENEWERS
GRID_DEFAULT_RENEWERS
GRID_AUTHORIZED_RETRIEVERS
GRID_DEFAULT_RETRIEVERS
GRID_AUTHORIZED_KEY_RETRIEVERS
GRID_DEFAULT_KEY_RETRIEVERS
GRID_TRUSTED_RETRIEVERS GRID_DEFAULT_TRUSTED_RETRIEVERS

to set up a richer myproxy-server.conf.

2. Upgrade of lcg-vomscerts-5.2.0:

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

3. Fix for GGUS ticket 44201. WMS do not match jobs which should match. This requires a change in the glue schema.

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
 #12289 myproxy config needs to allow authorized renewers list too
 #12292 myproxy config needs to allow authorized retrievers list too
 #12293 yaim hardcodes authorized_renewers for myproxy
 #17319 Reassigned item: Service type for myproxy unclear
 #17414 myproxy-fts provider publishes wrong access control rules
 #17623 Info providers required to advertise service versions
 #25898 Require Myproxy config to be built by ETICS.
 #35341 myproxy-config (What is the point of it?)
 #36920 proposed patches/cleanups for myproxy
 #42604 /etc/init.d/myproxy status fails when host dn has a space in.
 #43395 Request to have voms cert file called <something>.pem
 #45278 Removing Multivalue SE from GlueCESEBind
 #6531 MyProxy accepted_credentials redundant configuration
 #9275 myproxy server: cannot add authorized_retrievers with myproxy-config-1.1.8-13.edg1

Updated rpms

Name Version Full RPM name Description
glite-PX 3.1.16-0 glite-PX-3.1.16-0.i386.rpm gLite metapackage (glite-PX)
glite-info-provider-service 1.0.1-3 glite-info-provider-service-1.0.1-3.noarch.rpm glite-info-provider-service
glite-yaim-myproxy 4.0.3-1 glite-yaim-myproxy-4.0.3-1.noarch.rpm glite-yaim-myproxy module configures myproxy server.
glue-schema 1.3.0-5 glue-schema-1.3.0-5.noarch.rpm glue-schema
lcg-vomscerts 5.2.0-1 lcg-vomscerts-5.2.0-1.noarch.rpm lcg-vomscerts
myproxy-config 2.0.2-1 myproxy-config-2.0.2-1.noarch.rpm Provides an init.d script for MyProxy

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

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