You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

First draft

The current production version is 20071101-0808p2. We would like to install the new production candidate version 20080513-1222.

Reason for change

The new xrootd version allows to restrict the access to the GLAST data which is required. The current production version does not support access control. The new xrootd version has various improvements and fixes that make the system more reliable.

  • allows access control to the data which is required.
  • fix for checksum problems that could crash the server.
  • better handling of redirection for existing files.
  • other small bug fixes.

Testing

The production candidate version 20080513-1222 and its predecessor version 20080410-0747 have been deployed on the glast xrootd cluster running parallel to the production xrootd daemons. This allows using the new version on the glast xrootd cluster without interfering with the production version.

An update from 20080410-0747 to 20080513-1222 was needed as a critical bug was found (https://jira.slac.stanford.edu/browse/GXR-33) that affect the automatic update of the authorization file used by xrootd. Otherwise there are only small bug fixes between 20080410-0747 and 20080513-1222 that don't affect GLAST.
The test setup on the glast xrootd cluster used the configuration that would be used in production, in particular
authorization has been turned on.

The basic functionality of the new xrootd version has been examined in a test cluster. The testing included
reading/writing with xrdcp, stating files and checksumming of files.

All other test were done against the test version on the glast xrootd cluster:

  • Crawler tests ?
  • A MC-simulation was run successfully against the 20080410-0747
  • skimmer jobs run successfully

Rollback

It is possible to re-activate the old xrootd version now data will be lost.

CCB Jira

Details

The activation of the new version will be done the following way:

  1. Stop xrootd on all data server
  2. Stop xrootd on the redirector
  3. activate new version on redirector and restart it.
  4. restart xrootd on the data server with the new version

The whole procedure should take less then five minutes and clients will retry to access xrootd during that time
and not fail. User will be informed when the restart will happen in order to reduce the load on xrootd, just as a precaution.

  • No labels