This Update contains:

• the first release in EMI of FTS, v. 2.2.6,
• minor releases of BDII core, v. 1.1.0 and dCache, v. 1.9.12-6,
• revision releases of BDII site, v. 1.0.1, BDII top, v. 1.0.1, STORM SE, v. 1.7.1, WMS, v. 3.3.3

BDII core v. 1.1.0 task #21537

What's new:

This release of BDII core addresses a number of minor issues reported with the initial EMI 1 release. Most of the issues fixed are related to packaging and the templates provided by the glite-info-provider-service component.

One new useful feature has been included which is an improved status command which detects that the BDII is not updating. The yaim configuration has also been improved so that the BDII will automatically start on reboot. Improve status command to detect hanging BDII.

Version 1.7.0 of glite-info-provider-service has the following updates in addtion:

• There is a completely new GLUE 2 provider for VOMS. This should be called like:
  • glite-info-glue2-voms glite-info-glue2-voms.conf[,glite-info-glue2-voms-admin.conf] <site-name>

where the voms-admin config file should only be included if voms-admin is running on the server. The relevant config templates are glite-info-glue2-voms.conf.template and glite-info-glue2-voms-admin.conf.template, and it should normally be possible to use them without modification. This provider creates a single GLUE2Service object with one GLUE2Endpoint per VO for each of voms and voms-admin.

• For the WMS (wmproxy) the DN is now extracted using openssl rather than grid-cert-info, but there should be no effect on the published information. Also the GLUE 2 publisher will have GLUE2EndpointServingState: draining if a file /etc/glite-wms/.drain exists.
• The GLUE 2 information for the RTEPublisher (software tag publisher) has been revamped to fit within the ComputingService structure in CREAM. In particular the service type (EndpointInterfaceName) is now org.glite.ce.ApplicationPublisher.
• There is a new GLUE 2 template for the CEMon, again intended to fit within the ComputingService structure for CREAM.
• The VOMS, WMS (wmproxy) and CEMon templates and scripts have been updated to reflect the new paths, environment variables, RPM names and documentation locations in EMI, and hence are no longer compatible with gLite installations.
• A bug in the GLUE 2 publisher has been fixed that prevented the publication of multiple Extension objects with the same Key.
• The old beta-test GLUE 2 publisher has been renamed and replaced by a script which calls the new publisher, so any service which is still configured to use it will publish in the more up-to-date format.
• The wrapper around the service status query has been extended to allow extra arguments to be passed to the init.d script. This is used by voms and should otherwise be transparent.

This release also include the BDII Nagios probe. This probe is already running in production but has been repackaged for release within EMI.

Updated Artefacts

BDII site v. 1.0.1 task #21538

What's new:

This bdii release addresses a minor configuration issue.

Deployment Notes:

The BDII should be reconfigured so that the updated configuration is run.

Updated Artefacts

BDII top v. 1.0.1 task #21539

What's new:

This bdii release addresses a minor configuration issue.

Deployment Notes:

The BDII should be reconfigured so that the updated configuration is run.

Updated Artefacts

dCache v. 1.9.12-6 task #21619

What's new:

We completing the transition to the new configuration system and improved the script to migrate old configurations. We also replaced the pin manager with a faster and more robust implementation. Other changes were: Extending the the dCache script, HTTP support to third party srmCopy transfers, proxy certificate and VOMS support to the HTTP/WebDAV door, reducing file open latency, gPlazma 2 with ARGUS black listing (missing from initial release).

Installation and configuration:

Just do a yum update and restart dCache. Please see the release notes for incompatibilities with version of dCache before EMI (before 1.9.12-2)

Known issues:

There is one open GGUS ticket regarding some minor changes in the documentation. This ticket is already worked on and will be finished soon.

Updated Artefacts

FTS v. 2.2.6 task #18686

Release Notes and product information are available at FTS product page

StoRM SE v.1.7.1 task #21801

StoRM service is composed by 5 sub-components (4 servers and 1 client), which are deployable in distinguished hosts. This release represents the first upgrade of StoRM-SE in EMI-1. It includes updates on: FE, BE, DIP, YAIM and GridHTTPS. Client and GridFTP are the same of 1.7.0 release. Checksum service will be released soon.

StoRM-FrontEnd

What's new

• First update of storm-frontend-server in EMI-1. Server version is 1.7.1-6.
• Fixed bugs:
  • #137: "Request with Autorization Id parameters with non ASCII characters makes FE crash"
    • StoRM-ticket: https://storm.cnaf.infn.it:8443/redmine/issues/137
    • GGUS-ticket : https://ggus.eu/ws/ticket_info.php?ticket=71437 (see also @116)
  • #127: "Erroneous protocol list request does not returns proper SRM error"
    • StoRM-ticket: https://storm.cnaf.infn.it:8443/redmine/issues/127
    • GGUS-ticket : https://ggus.eu/tech/ticket_show.php?ticket=72464 (see also @126)
  • #126: "Erroneous protocol requests fill log file"
    • StoRM-ticket: https://storm.cnaf.infn.it:8443/redmine/issues/126
    • GGUS-ticket : https://ggus.eu/tech/ticket_show.php?ticket=72464 (see also @127)
  • #125: "Caller IP is not logged"
    • StoRM-ticket: https://storm.cnaf.infn.it:8443/redmine/issues/125
    • GGUS-ticket : https://ggus.eu/ws/ticket_info.php?ticket=72867
  • #116: "Storm frontend crashes"
    • StoRM-ticket: https://storm.cnaf.infn.it:8443/redmine/issues/116
    • GGUS-ticket : https://ggus.eu/ws/ticket_info.php?ticket=71437 (see also @137)

Installation and configuration

• To install storm-frontend-server, install its metapackage RPM: emi-storm-frontend-server-mp
• To configure storm-frontend-server use yaim on node se_storm_frontend. A good explanation of the required YAIM variable is available in /opt/glite/yaim/examples/siteinfo/services/se_storm_frontend
• To upgrade storm-frontend-server: stop the service, upgrade with yum, and restart the service.

Known issues

• None

StoRM-BackEnd-Server

What's new

• First update of storm-backend-server rin EMI-1. Server version is 1.7.1-3.
• Fixed bugs:
  • #145: "During initialization phase the space used is undefined (-1) causing an error on space reported"
    • StoRM-ticket: https://storm.cnaf.infn.it:8443/redmine/issues/145
    • GGUS-ticket : https://ggus.eu/ws/ticket_info.php?ticket=73025
  • 140: "Default GridHTTPs server port number"
    • StoRM-ticket: https://storm.cnaf.infn.it:8443/redmine/issues/140
    • GGUS-ticket : https://ggus.eu/ws/ticket_info.php?ticket=72845
  • 135: "Cron file points to wrong logrotate file"
    • StoRM-ticket: https://storm.cnaf.infn.it:8443/redmine/issues/135
    • GGUS-ticket : https://ggus.eu/ws/ticket_info.php?ticket=72683 (see also @134)
  • 134: "Logrotate file points to wrong logging file paths"
    • StoRM-ticket: https://storm.cnaf.infn.it:8443/redmine/issues/134
    • GGUS-ticket : https://ggus.eu/ws/ticket_info.php?ticket=72683 (see also @135)
  • 133: "StoRM backend fills host memory"
    • StoRM-ticket: https://storm.cnaf.infn.it:8443/redmine/issues/133
    • GGUS-ticket : N/A
  • 114: "BackEnd service name and status"
    • StoRM-ticket: https://storm.cnaf.infn.it:8443/redmine/issues/114
    • GGUS-ticket : N/A
  • 123: "Storage Space data Initialization"
    • StoRM-ticket: https://storm.cnaf.infn.it:8443/redmine/issues/123 * GGUS-ticket : N/A

Installation and configuration

• To install storm-backend-server, install its metapackage RPM: emi-storm-backend-server-mp
• To configure storm-backend-server use yaim on node se_storm_backend. A good explanation of the required YAIM variable is available in /opt/glite/yaim/examples/siteinfo/services/se_storm_backend
• If you configure other services with yaim on the same host always specify also se_storm_backend node
• To upgrade storm-backend-server: stop the service, upgrade with yum, and restart the service.

Known issues

• #146: "DIP get_size() incorrectly handles the info (kb insteadof bytes)"
• #147: "Glue2 GLUE2StorageShareCapacity* sizes always 0"
• #148: "Available space reported by InfoService is always zero"
• #149: "wrong yaim-storm version in the file /opt/glite/yaim/etc/versions/yaim-storm"
• #150: "Wrong calculation of SA_AVAILABLE_SIZE_KB and SA_USED_SIZE_KB"

Workarounds:

• For all above bugs unresolved will be distributed new scripts containing fixed functions. Consult our site for news and info about those fixes: http://storm.forge.cnaf.infn.it Those fixes will be available on the next StoRM updates.
• For #148 please modify file /opt/glite/yaim/functions/local/config_storm_namespace line 190:

  		TOTAL_ONLINE_SIZE=$((${SA_ONLINE_SIZE}*1024/(1000*1000*1000))) 

  By

  		TOTAL_ONLINE_SIZE=${SA_ONLINE_SIZE} 

  and Line 194:

  		TOTAL_NEARLINE_SIZE=$((${SA_NEARLINE_SIZE}*1024/(1000*1000*1000)) 

  By

  		TOTAL_NEARLINE_SIZE=${SA_NEARLINE_SIZE} 

StoRM-GridFTP-Server

What's new

• Nothing. This component is the same of the previous release.

Installation and configuration

• To install storm-gridftp-server, install its metapackage RPM: emi-storm-gridftp-server-mp
• To configure storm-gridftp-server use yaim on node se_storm_gridftp. A good explanation of the required YAIM variable is available in /opt/glite/yaim/examples/siteinfo/services/se_storm_gridftp
• The service needs to be installed on a machine on which storm file system is mounted.

Known issues

• None

StoRM-GridHTTPS-Server

What's new

• This component is the same of the previous release, except the name of RPM package in order to be compliant to EMI guidelines.

Installation and configuration

• To install storm-gridhttps-server install its metapackage RPM: emi-storm-gridhttps-mp
• To configure storm-gridhttps-server use yaim on node se_storm_gridhttps. A good explanation of the required YAIM variable is available in /opt/glite/yaim/examples/siteinfo/services/se_storm_gridhttps
• The service uses ports 8443 and (by default) 8080, so open them on your firewall.
• The service needs to be installed on a machine on which storm file system is mounted.

Known issues

• None

StoRM-SRM-Client

What's new

• Nothing. This component is the same of the previous release.

Installation and configuration

• To install storm-srm-client, install its metapackage RPM: emi-storm-srm-client-mp

Known issues

• None

Documentation

What's new

• Some enhancements on SysAdminGuide (added the "lost" part)

Updated Artefacts

WMS v. 3.3.3 task #21777

What's new

• This update of WMS addresses the problem causing authorization failure when submission to the WMS is done using a proxy retrieved from Myproxy (as this is the case in Nagios tests)

Deployment notes

• Yaim (re)configuration is required after installation/update

Updated Artefacts