FOR APPROVAL: gLite 3.1 end of support schedule

• Tiziana Ferrari (EGI.EU)
• Mario David (LIP Lisbon)

FOR APPROVAL: Addition of CREAM Nagios results into the monthly site availability calculations

• Tiziana Ferrari (EGI.EU)
• Dimitris Zilaskos (Technical staff)

At the moment in case of sites that only have CREAM CE instances, statistics just consider BDII and SRM test results, so the availability calculation engine just ignores the CE service. You can see this for example from the INFN-Parma site, which only deploys CREAM (see link below). At the moment CREAM CE is considered an independent service type from lcg ce and ARC, and tests per service type are ANDed (see GGUS ticket below).

FOR APPROVAL: org.bdii.freshness test set to critical as of 1.11.2010

• Malgorzata Krakowian (CYFRONET)
• Marcin Radecki (CYFRONET)
• Ron Trompert (SARA)
• Luuk Uljee (SARA)

FOR APPROVAL: modify the APEL-Synch tests to only check results for the last 13 months.

• John Gordon (STFC)
• Claire Devereux (STFC)

Dear all, Since migrating the APEL tests from SAM to Nagios, there seems to be some confusion between the test result “CRITICAL” and what are critical tests. In the case of APEL, we provide two different tests, APEL-Pub and APEL-Sync. APEL-Pub is a critical test; APEL-Sync is not. However, sites will assume that when the APEL-Sync Nagios test is in a “CRITICAL” status, their site will have their availability/reliability affected. The problem in our case (the reason why more sites are failing the APEL-Sync test) is that this test is calculated by checking all the historical data of a site (currently since January 2008) both in the site’s local database and in the central database and raising an error if there are any synchronisation issues. This means that if a site has published correctly all their accounting data, except for some records in January 2008, their APEL-Sync Nagios test today will have a result of “CRITICAL”. We have two different proposals: * Reduce the window to calculate the results of the APEL-Sync tests to 13 months only. Any unsynchronised data before that won’t result on an error. * Remove the status “CRITICAL” for the APEL-Sync test and only return a “WARNING” if there are discrepancies. (Cristina Del Cano)

FOR APPROVAL: New procedures

• Marcin Radecki (CYFRONET)
• Malgorzata Krakowian (CYFRONET)
• Ron Trompert (SARA)
• Luuk Uljee (SARA)

1) minor changes in NGI creation procedure GGUS tickets will be created by COD to all active NGIs to catch up their status along with the current version of the procedures. 2) ROC decomissioning procedure: ROC decomission procedure Question to all NGIs about accounting issue: https://gus.fzk.de/ws/ticket_info.php?ticket=62256 3) COD escalation procedure

Proposal of Policy Development process in EGI-InSPIRE

• Damir Marinovic (EGI.EU)

Update from OLA Task Force

• Dimitris Zilaskos (Technical staff)

AOB. - Face to face meeting in January 24-25 2010. Session 1: OMB on network support 24/01, 11:00 Session 2: New NGIs session, 24/01, afternoon Session 3: General OMB, 25/01 9:00 Session 4: OTAG, 25/01 14:00 - Quarterly report 2 - UPDATE on Requiments gathering for EMI Y1