Page History
...
The new xrootd version allows to restrict the access to the GLAST data which is requireda requirement. The current production version does not support access control. The new xrootd version has various improvements and fixes that make the system more reliable.
...
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 xrootdcaused the server to crash when re-reading the updated authorization file. 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. Only glast users are allowed to read data and certain production accounts are
allowed to write to xrootd.
...
- running the crawler
- MC-simulation
- skimmer jobs
- reading and writing with xrdcp
- reading from xrootd with root version 5.18.00(b)
and they run successfullyall tests passed.
The test that required the xrootd client tools (xrdcp to transfer files, xrd.pl to stat,checksum and remove
files) were done with using client tools the one from the new version.
Rollback
...
Deploying the new xrootd version requires to restart the new version on all glast xrootd servers, including the
redirector redirectors (glast-rdr). In addition the client admin tools in /afs/slac/g/glast/applications/xrootd/PROD have to be updated as the current version does not support authorization.
...
- Install new client admin tools:
mv /afs/slac/g/glast/applications/xrootd/TEST to /afs/slac/g/glast/applications/xrootd/PROD
The new version works with the old xrootd servers and this move doesn't cause any disruption to clients. - Stop xrootd on all data servers
- Stop xrootd on the redirectors (glastlnx04/05)
- activate Activate the new version on the redirectors and restart them.
- restart xrootd Activate the new version on the data servers with the new versionand restart them.
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.