Description
- Issue from QR: For some production sites there were some issues in this reporting period caused by the deployment of certain gLite updates which were not properly verified, and despite that have been put into production. For clients, such problems are avoided testing all updates locally before installing them in production at the site (regional/site certification). With other services (e.g. CE, SE, VOMS etc.) some small sites take the approach of waiting several days to see if problems are reported on common lists or through EGEE broadcasts, and only then they proceed. This introduces some delays to deploy new released versions into production. SA1 will discuss in the next quarter how this could be solved, mainly by building on the informal process already started by some sites.
Similar issue raised for yesterday's ops meeting by SEE: In the light of the recent "urgent" update for the BDII / WMS released on Friday the sites responded that they do not trust urgent m/w upgrades in general and they prefer to hold back for others to try them out first. This is a rather serious issue that tend to come back every now and then and I reckon we should try to solve it once and for all.
Also There are quite a few GGUS tickets related to the BDII issues
https://gus.fzk.de/ws/ticket_info.php?ticket=43230
https://gus.fzk.de/ws/ticket_info.php?ticket=43578
https://gus.fzk.de/ws/ticket_info.php?ticket=42684
- next COD F2F meeting April 2 to April 4th 2009; change of format, with training session on the regional dashboard before the meeting.
