gLite R-GMA SERVICETOOL
This release contains the gLite R-GMA Servicetool module v. 5.2.2. The following sections provide additional information about the release content, the module dependencies, the know bugs and issues and a list of bugs closed since the previous release. For information about installing and using the gLite R-GMA Servicetool, please refer to the gLite Installation and User Guides.
The R-GMA servicetool provides default values for the following parameters:
o R-GMA Servicetool enable (true)
o R-GMA Servicetool instance name (empty string)
These values must be overridden by individual services when publishing instances.
In addition it is not necessary anymore to configure the instances to be published in the individual configuration files. All instances are created programmatically by the configuration scripts, although all parameters can be overridden in the configurations files if required. For more information please refer to the gLite 1.5 configuration guide.
The module provides an updated, easier to use configuration file to define non-gLite instances to be published in R-GMA. This template (/opt/glite/etc/config/templates/glite-rgma-servicetool-externalServices.cfg.xml) can be used to publish for example SEs, myproxy servers, etc. If such custom file is found in the /opt/glite/etc/config directory it is used to create the additional instances when the servicetool configuration script is run. For more information please refer to the gLite 1.5 configuration guide. A new command line parameter is available in the script to publish the custom instances:
/opt/glite/etc/config/scripts/glite-rgma-servicetool-config.py --addExternalServices
A new command line switch is now available to remove configured service instances from the servicetool disk cache:
/opt/glite/etc/config/scripts/glite-rgma-servicetool-config.py --removeService=<serviceId>
If publishing of a service must only be temporarily stopped, it is better to set its enable flag to false.
The configuration of the module has changed. Please update your configuration if you upgrade from a previous version of the R-GMA servicetool.
The following configuration parameters have been added:
|
Parameter name |
Default value |
Description |
|
rgma.servicetool.siteId |
${HOSTNAME} |
Unique Id of site. It has to be a DNS entry owned by the site and does not have to be shared with another site (i.e it uniquely identifies the site). It normally defaults to the DNS name of the R-GMA Server running the Site Publisher service. [Example: lxb1420.cern.ch] [Type: 'string'] This parameter obsoletes the parameter: rgma.site-publisher.sitename |
|
rgma.servicetool.enable |
true |
Enable this service to be published to R-GMA. This parameter can be also specified separately per servicetool instance in your service configuration file. The value defined here is the fallback value if no value is defined in the individual servicetool instance. [Example: 'true'] [Type: 'boolean'] |
|
rgma.servicetool.name |
<empty string> |
Human-readable name for the service. Need not be globally unique. If value is empty/not specified, the serviceId is taken as the service name. This parameter can be also specified separately per servicetool instance in your service configuration file. The value defined here is the fallback value if no value is defined in the individual servicetool instance. [Example: Testservice to interface to my application] [Type: 'String'] |
No parameter has been removed in this release.
|
Parameter name |
Reason |
|
rgma.site-publisher.sitename |
This parameter has been obsoleted by the new parameter rgma.site-publisher.siteId |
The gLite R-GMA Servicetool module installs/uses the following set of gLite deployment modules:
Please see the corresponding release notes of these modules for details.
The gLite R-GMA Servicetool module is composed of the following gLite components (list includes the gLite components of the other used gLite deployment modules in section 3.1):
|
Component name |
Description |
Version |
File |
|
glite-config |
gLite configuration scripts |
1.6.22 |
|
|
glite-essentials-java |
Set of JAVA libraries essential for gLite middleware |
1.2.0 |
|
|
glite-rgma-api-java |
Java API for R-GMA |
5.0.3 |
|
|
glite-rgma-base |
R-GMA basic configuration and documentation |
5.0.4 |
|
|
glite-rgma-common-config |
gLite rgma common configuration items installation |
5.0.1 |
|
|
glite-rgma-servicetool |
R-GMA service tool |
5.0.3 |
|
|
glite-rgma-servicetool-config |
gLite R-GMA Servicetool configuration files |
5.2.2 |
|
|
glite-rgma-stubs-servlet-java |
Java client implementation stubs for R-GMA |
5.0.3 |
|
|
glite-security-trustmanager |
The java certificate path checkin for proxy certs in SSL with plugins for tomcat and axis. |
1.8.2 |
|
|
glite-security-util-java |
The java utilities library for security |
1.3.0 |
|
|
glite-security-utils-config |
gLite Security Utilities configuration files |
1.2.2 |
The gLite R-GMA Servicetool module has the following dependencies:
|
Component name |
Description |
Version |
File |
|
j2re |
Java JRE |
1.4.2 |
../../../../../../../glite-web/egee/packages/externals/bin/rhel30/RPMS/j2re-1_4_2_08-linux-i586.rpm |
For the list of dependencies of the gLite sub-deployment modules, listed in section 3.1, please see the release notes of the corresponding modules for their list of dependencies.
This release has no known bugs and issues. Bug numbers refer to the gLite Bug Tracking system database hosted on the CERN Savannah system at https://savannah.cern.ch/bugs/?group=jra1mdw.
|
Bug number |
Description |
|
|
|
||
|
Publication rate and LRP for site and service publishers should be configurable |
|
|
|
|
||
|
When servicetool endpoints are changed in config they don't seem to update properly |
|
|
|
|
||
|
|
This release fixes the following bugs and issues. Bug numbers refer to the gLite Bug Tracking system database hosted on the CERN Savannah system at https://savannah.cern.ch/bugs/?group=jra1mdw
|
Bug number |
Description |
|
|
|
||
|
|