gLite Data Management Single Catalog (Fireman)
This release contains the gLite Data Management Single Catalog (Fireman) for MySQL module v. 2.1.3. 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 Data Management Single Catalog, please refer to the gLite Installation and User Guides.
This release introduces the following changes:
It is not necessary anymore to define a separate Fireman instance for each VO. There is a single instance in the configuration file that is used to iterate automatically over all the VOs defined in the VO list.
The following new parameters have been added to the glite-data-single-catalog.cfg.xml file:
|
Parameter name |
Default value |
Description |
|
set.mysql.root.password |
false |
If this parameter is true, then the root password of the mysql database is set to the value specified in mysql.root.password if it not yet set. This parameter has no effect if the database root password is already set. It can be used to ease automated installation and configuration of the service, if mysql is not managed in some other way [Example: false][Type: boolean] |
|
catalog-service-fr-mysql.ADMIN_VOMS_ATTRIBUTES |
<empty string> |
ADMIN/superuser settings. Note that the extra priviliges defined by the settings below are combined in an OR fashion - a VOMS match OR a mapfile match will result in the client being given the extra authorization. If both of these are empty there is no superuser defined for the service and certain functionality iss unavailable (i.e. if permissions on global default permissions are not tweaked, nobody can change them or create directories in the ROOT path. If a user's certificate contains this VOMS attribute, they are additionally permitted to do any operation upon the service including metadata bits operations. If a user's certificate contains any of these VOMS attributes, they are additionally permitted to do any operation upon the service including creating channel and VO managers [Example: /opt/glite/etc/config/ ADMIN_VOMS_ATTRIBUTES][Type: string] |
|
catalog-service-fr-mysql.ADMIN_MAPFILE |
<empty string> |
If a client's certificate subject name is listed in this file, they are additionally permitted to do any operation upon the service including manage channels. [Example: /opt/glite/etc/config/ADMIN_MAPFILE][Type: string] |
The following parameters have been changed in the glite-data-single-catalog.cfg.xml file:
|
Parameter name |
Old value |
New value |
Description |
|
catalog-service-fr-mysql.DBURL |
jdbc:mysql://localhost:3306/${catalog-service-fr-mysql.DBNAME} |
jdbc:mysql://localhost:3306/${catalog-service-fr-mysql.DBNAME}?zeroDateTimeBehavior=convertToNull |
The DBURL has been augmented with the parameter zeroDateTimeBehavior |
All parameters used to set VO-specific values have been removed from the service configuration files and moved to a dedicated VO configuration file called vo-list.cfg.xml. A template is available in /opt/glite/etc/config/templates. This file is common to all gLite services running on this node or referenced in the same site-config file (unless locally overridden). For more information please refer to the gLite 1.5 installation guide.
The R-GMA Service Publisher (aka R-GMA servicetool) parameters are now automatically handled by the configuration script and do not need to be explicitly set anymore in the configuration file. The parameters can be set in the configuration file to override the default values.
The gLite Data Management Single Catalog (Fireman) for MySQL module includes the following sub-modules:
- gLite Security Utilities
- gLite R-GMA Servicetool
The sub-modules are automatically installed with the Fireman module. For more information about these sub-modules please refer to the specific release notes and installation instructions.
The gLite Data Management Single Catalog v. 2.1.3 is composed of the following gLite components:
|
Component name |
Description |
Version |
File |
|
glite-config |
gLite configuration scripts |
1.6.22 |
|
|
glite-data-single-catalog-config |
gLite Data Single Catalog configuration files |
2.1.3 |
|
|
glite-data-catalog-service-fr-mysql |
gLite Data Catalog Service (MySQL version) |
1.4.6 |
|
|
glite-data-common |
common files for gLite Data Management web-services |
1.2.2 |
|
|
glite-rgma-servicetool-config |
gLite R-GMA servicetool installation |
5.2.2 |
|
|
glite-security-utils-config |
gLite Security Utilities configuration files |
1.2.2 |
The gLite Data Management Single Catalog 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 |
|
MySQL-client |
MySQL - Client |
4.1.11 |
|
|
MySQL-server |
MySQL |
4.1.11 |
|
|
tomcat5 |
Tomcat application server |
5.0.28 |
This
release has the following 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
.
Known open bugs:
The following bugs have been fixed in this or previous releases, but not yet tested:
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