Operations Room: EVO <ol> <li>Top level BDII service</li> Out of the pool: Austria, instance from UIBK <br> <a href="http://zeus16.cyf-kr.edu.pl/cs-dynamic/bdii-status"> Status of the DNS pool </a><br> <a href="http://zeus16.cyf-kr.edu.pl/cs-dynamic/bdii-comp"> Differences between BDIIs </a>. <br> <li>Report from the PPS sites</li> <br> <li>Switch from SAM to nagios</li> Last week evaluation of nagios-based monitoring in ROCs showed no showstoppers to use it in production. As a result all operations teams will start using nagios-based monitoring for their daily work as of *1st March 2010*. <br> The consequences are the following: <br> <br> 1. Production operations dashboard available at https://operations-portal.in2p3.fr/ will switch to nagios alarms. <br><br> 2. Site Administrators/1st line support teams should use MyEGEE with "ROC_CRITICAL" profile as an equivalent of SAM portal. e.g. https://sam-ce-roc.cern.ch/myegee And check https://twiki.cern.ch/twiki/bin/view/EGEE/NagiosROCURL for a complete list of all regional nagios instances. <br><br> 3. SAMAP equivalence is provided by nagios feature of "Scheduling checks" using nagios mechanisms (more info at: http://egee.grid.cyfronet.pl/core-services/nagios/user-documentation/) <br><br> 4. Detailed test results as included in alarms and tickets will be provided by direct URL to a nagios instance. <br><br> Known issues with the tools will be solved soon. More info at: https://forge.in2p3.fr/attachments/293/Nagios_testing_3rd_round_ROD_summary.doc <br><br> For any other problems with tools a GGUS ticket should be created. <br><br> Note that the monthly site availabilities will still be calculated using SAM. Any discrepancy between SAM and Nagios at the end of the month will be analyzed and recalculated so no site is penalized for this in the first months of Nagios deployment in production. <br> </ol>

1st line support

• Jan Astalos

Room: EVO

Monitoring

• Emir Imamagic (SRCE)

Room: EVO

AOB Room: EVO