gLite I/O Server
This release contains the gLite I/O Server module v. 2.1.4. 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 I/O Server, please refer to the gLite Installation and User Guides.
This release includes the following changes:
update the file size in the catalog if there is a failure in the connection between the gLite I/O client and the server, EVEN when the file transmission hasn't yet begun (this means that the file size in the Catalog for this situation shall be 0)
Disabled the resetting of port to the min-max port range to be more firewall friendly.
RPM dependency on glite-data-io-daemon >= 2.0.0
updated version for the updated dependencies
updated version for the updated dependencies
The following new parameters have been added to the glite-io-server.cfg.xml file:
Parameter name |
Default value |
Description |
instanceDescription |
${vo.name}-${init.CatalogType} |
A short description of the instance used to create the different instance files [Example: ${vo.name}-${init.CatalogType}] [Type: string]
This parameter is a more general way of naming the I/O Server instances. In previous releases the name was forced to be ${vo.name}-${init.CatalogType}. Now this is the default value, but it can be replaced with any user string |
autocalculate.port |
true |
If this value is true, the I/O Server port for each instance is calculated automatically starting from the value of the parameter io-daemon.Port. If the value is false, the io-daemon.Port value is taken without modifications. In this case, users must defined instance to have a different port configured in this file |
rgma.servicetool.activate |
true |
Turn on/off servicetool for the node. [Example: true ] [Type: 'boolean'] |
The following parameters have been changed in the glite-io-server.cfg.xml file:
Parameter name |
Old value |
New value |
Description |
io-daemon.Port |
9999 |
The value is not changed, but the way this parameter is used is now different. Typically this value is now used as a starting point for calculating the ports for all instances in case the instances are created automatically by iterating on the VO list. If instance are defined manually, the autocalculate.port parameter must be set to false and the desired port number must be set here explicitly. |
The port to be used to contact the server. This port is only used for authentication and session establishment messages. When the real data transfer will be perfomed using a QUANTA paralled TCP stream a pool of sockets are opened on the server side binding a tuple of available ports from 50000 to 51000. This port should not be higher than 9999 and different I/O Server instances should not run on contiguos ports (for example set one to 9999 and another one to 9989). If the parameter autocalculate.port is true or this parameter is absent or empty, the ports are automatically set by the configuration script following this rule and starting from 9999. If a value is given and the autocalculate.port parameter is true, the ports are set using the given value as port for the first instance and the other are calculated according to the rule. In all other case the value of this parameter is used without modifications |
log.FileName |
${GLITE_LOCATION_LOG}/ |
${GLITE_LOCATION_LOG}/ |
The location of the log file |
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 I/O Client module requires the following sub-modules:
- gLite Security Utilities
- gLite R-GMA Servicetool
The sub-modules are automatically installed with the I/O Server module unless differently specified. For more information about these sub-modules please refer to the specific release notes and installation instructions.
The gLite I/O Server v. 2.1.4 is composed of the following gLite components:
Component name |
Description |
Version |
File |
glite-config |
gLite configuration scripts |
1.6.22 |
|
glite-data-catalog-api-c |
gLite Data Catalogs C/C++ API |
2.0.0 |
|
glite-data-catalog-interface |
gLite Catalog Interfaces |
2.0.0 |
|
glite-data-config-service |
GLite Data Config Service |
1.2.4 |
|
glite-data-io-authz-catalogs |
GLite Data IO Authorization Plugin |
1.0.1 |
|
glite-data-io-authz-fas |
GLite Data IO FAS Plugin |
1.2.0 |
|
glite-data-io-base |
GLite Data IO Base |
2.0.0 |
|
glite-data-io-daemon |
GLite Data IO Daemon Server |
2.0.2 |
|
glite-data-io-gss-auth |
GLite Data IO GSS Authentication QUANTA Plugin |
1.0.0 |
|
glite-data-io-protocol-dcap |
gLite Data I/O dcap Protocol Plugin |
1.1.2 |
|
glite-data-io-protocol-rfio |
GLite Data IO rfio Protocol Plugin |
1.3.3 |
|
glite-data-io-quanta |
GLite Data IO Quanta Transport Layer |
1.0.0 |
|
glite-data-io-resolve-catalogs |
GLite Data IO Resolve Catalogs Plugin |
1.3.0 |
|
glite-data-io-resolve-common |
GLite Data IO Resolve Common |
1.3.0 |
|
glite-data-io-resolve-fireman |
GLite Data IO Resolve FiReMan |
1.4.0 |
|
glite-data-io-resolve-fr |
GLite Data IO Resolve FR Plugin |
1.4.0 |
|
glite-data-srm-api-c |
gLite Data SRM C/C++ API |
1.1.0 |
|
glite-essentials-cpp |
Essential C/C++ libraries for gLite software |
1.1.1 |
|
glite-io-server-config |
gLite I/O Server configuration files |
2.1.4 |
|
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 I/O Server module v. 2.1.4 has the following dependencies:
Component name |
Description |
Version |
File |
CGSI_gSOAP_2.6 |
GSI plugin for gSOAP |
1.1.9 |
|
gpt |
The Grid Packaging Toolkit (GPT) |
VDT1.2.2rh9 |
../../../../../../../glite-web/egee/packages/externals/bin/rhel30/RPMS/gpt-VDT1.2.2rh9-1.noarch.rpm |
vdt_globus_essentials |
Virtual Data Toolkit |
VDT1.2.2rh9 |
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 they have not been tested yet:
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 |
|
|
||
|
||
I/O server config: starts/stops/checks rfio, even if not using |
|