2008/05/14
Request to install a new Xrootd production version
First draft Reason for changeThe current production version is 20071101-0808p2. We would like to install the new production candidate version 20080513-1222. The new xrootd version allows to restrict the access to the GLAST data which is a 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.
TestingThe 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 caused 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 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 new version 20080410-0747 and repeated for production candidate version 20080513-1222 on the glast xrootd cluster: The main tests were:
and all 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 the one from the new version. RollbackIt is possible to re-activate the old xrootd version, no data will be lost. CCB JiraDetailsDeploying the new xrootd version requires to restart the new version on all glast xrootd servers, including the 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. The steps are:
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.
2008/05/15
CCB Request for GroupManager 1.8
Reason for changeThe group manager has been updated with very minor changes to support better interaction with the Shift Schedule application. Since the shift schedule app is to be announced tomorrow these changes have already been released, although they can be trivially backed out if need be. Test ProcedureThese changes have all been tested in the dev server http://glast-tomcat03.slac.stanford.edu:8080/GroupManager Rollback procedureIt will be easy to rollback these changes should any problem occur. Related JIRADetails
2008/05/17
CCB Request to release Job Control 1.7
Last changed: May 17, 2008 16:53 by Tony Johnson
Reason for changeThe Job Control daemon is used by Pipeline II to submit jobs to LSF and BQS (at Lyon). This minor change adds a management interface to support monitoring the daemons, and adds improved error reporting when an error occurs during job submission. Neither of these changes will have any effect on operation, but will make tracking down problems easier. Test ProcedureThese changes have been tested on a DEV version of the server Rollback procedureIt will be easy to rollback these changes should any problem occur. Related JIRADetails
2008/05/27
CCB Request to release new Pipeline II, Data Catalog
Reason for changeThis new release incorporates changes required to support multiple "versions" of files as required by Level 1 processing. Currently L1 uses an arbitrary naming scheme which is not understood by the data catalog or tools like the data skimmer. This results in multiple copies of the same event being skimmed. This release fixes this problem, and also simplified the book keeping required by L1Proc. The database will be converted to the new structure. Based on the time taken to convert the DEV database, and the number of datasets in PROD, we estimate that it will take about 8 hours to do the conversion on PROD. Database views have been created which will mean tools which care only about the most recent version of a file, and which do not update the database will not see any change/ Test ProcedureThese changes have been tested on a DEV version of the server. We have tested ASP, MC and L1 tasks using the new release. Rollback procedureThis update requires changes to the data catalog database. They can be rolled back if a problem is found immediately, but rolling back after a substantial number of datasets have been registered in the new schema will be difficult. Related JIRADetailsDataCatalog 2.0Pipeline 1.2This release also incorporates the performance improvements made in release 1.1.1 and minor changes to the job control daemon documented separately. Data Crawler 1.3
2008/05/30
CCB Request to release Pipeline II v1.2.1, Data Catalog v2.0.1
Reason for Change:Database connections are being left open when creating DataCatClient objects. The open connections are exhausting the supply of sockets on the server machine. Test Procedure:Install to TEST, DEV, have Maria Elana test L1Proc there to prove that the connections are being closed correctly. Rollback Procedure:Just restart server using org-glast-pipeline-server-1.2.jar Related JIRADetails:
|
May 15, 2008
May 27, 2008 |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||
