ITB1131 Documentation

Introduction

This page has the update and testing instructions for the current ITB 1.1.31 (OSG 1.2.19 candidate) update.

If you are updating from version 1.1.21 or earlier, you need to do a fresh installation. This is because the ITB cache changed locations to a different server.

If you are updating from version 1.1.22 - 1.1.25 see these update instructions.

If you are updating from version 1.1.26 or later see these update instructions.

Updating

Testing and Validation

Components Changed

The full list is available here: http://vdt.cs.wisc.edu/releases/2.0.0/release-p26.html

Highlights:

  • New RSV version with two bug fixes
    • Fixed race condition that could generate empty records
    • Fixed bug that caused metrics and consumers to get a permission denied error if the RSV service was started from the /root directory (or any other directory that is not readable by the RSV user)
  • Tomcat updated to 5.5.32
  • Java updated to 1.6.0_23
  • mysql updated to 5.0.92
  • configure-osg update

Testing

Admins should try the steps outlined in the General Testing Guidelines:

General OSG 1.2 Testing Instructions

This document is a guide to help OSG VTB and ITB tester know what to test for a given release of the VDT.

General expectations for VTB testing

VTB testers should expect:

  • To do a fresh installation, not upgrades
  • There might be a need to do multiple installations per release (as bugs are fixed)
  • The should do a basic "smoke test": Can they do an installation? Are there unexpected error messages or unusual warnings?
  • Unless otherwise informed, VTB testing should focus on verifying that the CE and Bestman SE are working. (See details below.)
  • For each VDT release, there will be description of what extra testing needs to be done for that release.
  • Do all RSV tests still pass?

General expectations for ITB testing

ITB testers should expect:

  • Usually they can simply upgrade their ITB installation.
  • Sometimes the upgrades will fail and they'll need to try again.
  • The goal is to test the upgrade process as well as functionality.
  • The should do a basic "smoke test": Can they do an installation? Are there unexpected error messages or unusual warnings?
  • Unless otherwise informed, ITB testing should focus on verifying that the CE and Bestman SE are working. (See details below.)
  • For each VDT release, there will be description of what extra testing needs to be done for that release, and what VO testing needs to be done.
  • Do all RSV tests still pass?
    • Is information displayed correctly on the html-consumer?
    • Is information reported to the GOC? Look at your site in /Integration.MyOSG to determine this.

Components to Test

Testing a CE

  • Installation: Did you have Pacman problems, new messages during installation, etc?
  • Configuration:
    • Did you have problems with vdt-post-install or configure-osg?
    • configure-osg
      • Are there any undocumented changes to config.ini or unexpected behavioral changes?
      • Are there output messages that need improvement/clarification?
  • Overall:
    • Does the site-verify script return any errors?
  • Job submission:
    • Run a Globus job against the fork job manager
    • Run a Globus job against the batch system job manager of your choice (Condor, etc)
    • (ITB only) Run jobs with the Panda-based test suite
  • Authorization:
    • Does a grid-mapfile still work?
    • Can you authorize with GUMS (via PRIMA)?
  • Gratia:
    • Is Gratia recording data for your batch system jobs?
      • Look at $VDT_LOCATION/gratia/var/logs
      • Is data reaching the central ITB collector?
  • RSV:
    • Are all RSV probes green?
    • (ITB only) Are RSV records showing up on MyOSG page?
  • ITB-specific testing:
    • VO testing (As needed)

Testing a SE

  • Installation: Did you have Pacman problems, new messages during installation, etc?
  • Configuration: Did you have problems with vdt-post-install or configure-osg?
  • File Transfer: Can you still transfer files in and out of Bestman?

-- ScotKronenfeld - 09 Apr 2010

In addition, please try the following specific tests related to software components that we've updated:

  • Verify that information reporting to bdii is working and the correct information is being reported. Also:
    • Verify WLCG site attributes are being reported correctly
    • Verify allowed_vos work corrrectly for SEs
  • Check MyOSG to verify that BDII and RSV information is being reported correctly
  • Check authentication to make sure that the new CA certs are working correctly

Open bugs and workarounds

How to report a bug?

Bug reports for the installation and documentation should be filed with GOC at https://ticket.grid.iu.edu/itb/open. Please don't use the VDT support center or any other support center as the recipient since that will cause a email loop

Testing Status

This table will be updated by Suchandra and/or Scot to help track the status of sites. Admins, please feel free to update it if you would like.

Site Admin Status Notes
UC-ITB Suchandra    
TTU Poonam    
BNL Xin    
FNAL Steve Timm    
OU Horst / Karthik Updated to 1.1.31  

-- SuchandraThapa - 04 Mar 2011

Topic revision: r3 - 07 Mar 2011 - 23:48:24 - KarthikArun

Hello, TWikiGuest!
Register

 
TWIKI.NET

TWiki | Report Bugs | Privacy Policy

This site is powered by the TWiki collaboration platformCopyright by the contributing authors. All material on this collaboration platform is the property of the contributing authors..