gLite Data Management Single Catalog (Fireman)

1. Release Description

This release contains the gLite Data Management Single Catalog (Fireman) for MySQL module v. 1.1.0. 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.

2. Changes in this Release

This release contains the following changes:

From this release, the Fireman service runs by default as a secure web service on the https port 8443 and requires the installation of the gLite Security Utilities. In order to open the non-secure http port 8080, the following new parameter must be set to true in the configuration:

<allow.unsecure.port
      description="Enable using the unsecure port 8080. It can be true or false.
      Example: false"
      value="true"/>
The configuration script now checks if the Fireman catalog is already installed before trying to load the database schema to prevent destroying an existing database. If the database must be reinstalled from scratch the following new parameter must be set to true in the configuration:

<db.force.create
      description="If the catalog mysql database has already been created
            on this node, running the configuration script will drop and recreate
            it if this parameter is set to true. If the parameter is set to false
            the database will be created only if it doesn't exist.
            The default value is false [Type: boolean]"
      value="true"/>
It is now possible to specify a root password for mysql in the configuration file using the new parameter mysql.root.password. Alternatively, the password can be specified in the standard mysql configuration file (mysql.conf). In this case the mysql.root.password parameter must be removed or left empty in the module Single Catalog configuration file
All R-GMA service publishing instances in the configuration template now have default values except the new vo.name parameter that has to be set from ‘changeme’ to a valid VO name for each service instance (one instance per service type per VO)

3. Release contents

The gLite Data Management Single Catalog v. 1.1.0 is composed of the following gLite components:

Component name	Version	File
org.glite.deployment.data-single-catalog	1.1.0	../../../../../../../glite-web/egee/packages/R1.1/R20050430/installers/glite-data-local-transfer-service_installer.sh ../../../../../../../glite-web/egee/packages/R1.1/R20050430/bin/rhel30/noarch/RPMS/glite-data-local-transfer-service-config-1.1.0-2.noarch.rpm apt-get install glite-data-single-catalog-config
org.glite.deployment.config	1.1.1	../../../../../../../glite-web/egee/packages/R1.1/R20050430/bin/rhel30/noarch/RPMS/glite-config-1.1.1-3.noarch.rpm
glite-data-catalog-service-fr-mysql	1.2.1	../../../../../../../glite-web/egee/packages/R1.1/R20050430/bin/rhel30/noarch/RPMS/glite-data-catalog-service-fr-mysql-1.2.1-1.noarch.rpm
glite-data-common	1.2.1	../../../../../../../glite-web/egee/packages/R1.1/R20050430/bin/rhel30/noarch/RPMS/glite-data-common-1.2.1-1.noarch.rpm

4. Dependencies

The gLite Data Management Single Catalog module has the following dependencies:

Component name	Version	RPM file name
gLite Security Utilities	1.0.1	../../../../../../../glite-web/egee/packages/R1.1/R20050430/installers/glite-security-utils_installer.sh
gLite R-GMA Service Publisher	4.2.0	../../../../../../../glite-web/egee/packages/R1.1/R20050430/installers/glite-security-utils_installer.sh
MySQL-server	4.0.20	../../../../../../../glite-web/egee/packages/externals/bin/rhel30/RPMS/MySQL-server-4.0.20-0.i386.rpm
MySQL-client	4.0.20	../../../../../../../glite-web/egee/packages/externals/bin/rhel30/RPMS/MySQL-client-4.0.20-0.i386.rpm
Tomcat	5.0.28	../../../../../../../glite-web/egee/packages/externals/bin/rhel30/RPMS/tomcat5-5.0.28-6_EGEE.i386.rpm
Java SDK/JRE	1.4.2	http://java.sun.com/j2se/1.4.2/download.html

5. Known bugs and issues

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 .

It is not possible to create files and directories in the catalog using the APIs or CLIs when using the secure endpoints. This is due to the fact that the root of the catalog filesystem is owned by a user not mapped to any certificate. This issue will be fixed in the future release of the administration tools. The current workaround is to use non-secure endpoints or to create top-level directories using non-secure endpoints and then switch to secure endpoints. The directories created in this way are writable by all users belonging to the default group egee-group (that is all users not having a valid VOMS group in the certificate).
No removal procedure is provided with this release apart from the removal of the RPMS. Any account, group or other resource created during the module configuration must be manually cleaned.

Known open bugs:

Bug number	Description
#6861	Incorrect error message from glite-catalog-ls command
#7089	glite-catalog-mkdir error message has a typo
#7103	glite-catalog-ls /tmp/*.data ... only list part of matches
#7238	glite-catalog-rmdir doesn't produce a exception when directory is not empty
#7251	glite-catalog-ls doesn't let me read a directory when an entry exists more than once.
#7277	glite-data-single-catalog-config v. 0.1.3 scratches my DB
#7469	Cannot call glite-catalog-ls from 2 machines at the same time in MySQL Fireman, pointing to the same directory
#7730	glite-catalog-ls returns different message for MySQL and Oracle catalog when dir doesn't exist
#7833	Problem with glite-catalog-mv
#7932	missing dependency in catalogue cli
#7993	option parsing of glite-catalog-find
#8053	Problem with glite-catalog-create with -S option
#8057	Problem with glite-catalog-chmod
#8416	glite-catalog-find returns all entries
#8437	Not possible to create dirs/files in MySQL Fireman catalog in secure mode
#8438	glite-catalog-chkperm (MySQL version) only checks user permissions

The following bugs have been fixed in this or previous releases, but not yet tested:

Bug number	Description
#5581	Cannot remove files from the catalog
#5633	Fireman catalog: "java.lang.reflect.InvocationTargetException" during bulk creation of entries
#5723	Fireman catalog: "500 Internal Server Error" response to readDir call after killing a client during a bulk create call
#5923	Fireman catalog: Exceptions while creating entries (via bulks) with 10 clients simultaneously
#6465	services/FileCatalog automatically added to the Fireman endpoint
#7190	SC: link to installer wrong
#7690	problem with glite-catalog-ls
#7746	rmdir in output from glite-catalog-rm command
#7790	glite-security-utils_installer.sh is not run by the Single Catalog installation script
#7995	SC: reference to glite-data-local-transfer-service left in Single Catalog Installation section
#8068	SC: "rgma.servicetool.status_script" really to be configured by SA?

6. Bugs closed since last release

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
#6730	LFN normalisation needs to be done in Fireman catalogs
#6936	glite-catalog-ls doesn't works for Oracle server?
#6946	MySQL Fireman configuration doesn't create indexes
#7309	Single Catalog config script looks for J2SDK
#7476	Single Catalog MySQL config script does not modify tomcat5.conf file
#7754	glite-data-single-catalog-config.py fails with an indentation error
#7761	indentation error for the MySQL Single Catalog python deployment script
#7789	Release Notes of the gLite Data Management Single Catalog dependencies broken link
#7836	Problem to create a directory which has the same name than a file

7. Previous Releases

7.1. Release 1.0.0

7.1.1. Release Description

This release contains the gLite Data Management Single Catalog for MySSQL module v. 1.0.0. 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.

7.1.2. Changes in this Release

This release doesn’t contain any functional changes, just bug fixing. The version number has been increased for the official release of gLite v. 1.0

7.1.3. Release contents

The gLite Data Management Single Catalog v. 1.0.0 is composed of the following gLite components:

Component name	Version	File
org.glite.deployment.data-single-catalog	1.0.0	../../../../../../../glite-web/egee/packages/R1.0/R20050331/installers/glite-data-local-transfer-service_installer.sh ../../../../../../../glite-web/egee/packages/R1.0/R20050331/bin/rhel30/noarch/RPMS/glite-data-local-transfer-service-config-1.0.0-1.noarch.rpm
org.glite.deployment.config	1.0.0	../../../../../../../glite-web/egee/packages/R1.0/R20050331/bin/rhel30/noarch/RPMS/glite-config-1.0.0-1.noarch.rpm
glite-data-catalog-service-fr-mysql	1.2.1	../../../../../../../glite-web/egee/packages/R1.0/R20050331/bin/rhel30/noarch/RPMS/glite-data-catalog-service-fr-mysql-1.2.1-1.noarch.rpm
glite-data-common	1.1.8	../../../../../../../glite-web/egee/packages/R1.0/R20050331/bin/rhel30/noarch/RPMS/glite-data-common-1.1.8-1.noarch.rpm

7.1.4. Dependencies

The gLite Data Management Single Catalog module has the following dependencies:

Component name	Version	RPM file name
gLite R-GMA Service Publisher	4.2.0	../../../../../../../glite-web/egee/packages/R1.0/R20050331/installers/glite-security-utils_installer.sh
MySQL-server	4.0.20	../../../../../../../glite-web/egee/packages/externals/bin/rhel30/RPMS/MySQL-server-4.0.20-0.i386.rpm
MySQL-client	4.0.20	../../../../../../../glite-web/egee/packages/externals/bin/rhel30/RPMS/MySQL-client-4.0.20-0.i386.rpm
Tomcat	5.0.28	../../../../../../../glite-web/egee/packages/externals/bin/rhel30/RPMS/tomcat5-5.0.28-4_EGEE.i386.rpm
Java SDK/JRE	1.4.2	http://java.sun.com/j2se/1.4.2/download.html

7.1.5. Known bugs and issues

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 .

No removal procedure is provided with this release apart from the removal of the RPMS. Any account, group or other resource created during the module configuration must be manually cleaned.

Known open bugs:

Bug number	Description
#7256	data-catalog-api-c-2.0.0 let me create twice the same entry in the catalog
#7277	glite-data-single-catalog-config v. 0.1.3 scratches my DB
#5581	Cannot remove files from the catalog
#6730	LFN normalisation needs to be done in Fireman catalogs
#7089	glite-catalog-mkdir error message has a typo

The following bugs have been fixed in this or previous releases, but not yet tested:

Bug number	Description
#7309	Single Catalog config script looks for J2SDK
#7476	Single Catalog MySQL config script does not modify tomcat5.conf file
#5633	Fireman catalog: "java.lang.reflect.InvocationTargetException" during bulk creation of entries
#5723	Fireman catalog: "500 Internal Server Error" response to readDir call after killing a client during a bulk create call
#5923	Fireman catalog: Exceptions while creating entries (via bulks) with 10 clients simultaneously
#6465	services/FileCatalog automatically added to the Fireman endpoint

7.1.6. Bugs closed since last release

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
#5037	Cannot retrieve file newly added to the catalog (on lxb1432.cern.ch)
#5755	Fireman catalog: "500 Internal Server Error" response to readDir after simultaneous bulk create from multiple clients
#5820	Fireman catalog: "500 (Internal Server Error) read timeout" when calling readDir
#7482	catalog gives strange message if endpoint is malformed