1 / 6

Enhancing Quality Monitoring of BDII Information System for GLUE 2 Integration

On December 4, 2012, a meeting was held to address the monitoring challenges of the BDII Information System. Currently, there is insufficient focus on the quality of published information. Efforts are underway to improve this for GLUE 2, utilizing the existing glue-validator. The session discussed current checks against the site BDII, the need for expanded checks on object classes and attributes, and the integration with SAM/Nagios to automate error notifications. LHCb's use case for automated GGUS ticket creation was also a key topic.

dori
Télécharger la présentation

Enhancing Quality Monitoring of BDII Information System for GLUE 2 Integration

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. 4th December 2012 Monitoring the BDII Information System meeting with users

  2. Introduction • No specific effort dedicated to monitoring the quality of the published information • We want to change this for GLUE 2 • glue-validator already in place • Existing checks • Object Class • Mandatory attribute • Singled-valued • Data types • It needs to be extended Maria Alandes Pradillo, CERN

  3. What it is monitored now • gstat-sanity-check runs againstthe site BDII • It checks all the services published in the site BDII: gstat-validate-sanity-check -H “site-bdii-hostname" -t 120 -b Mds-Vo-Name=site-name,o=Grid -p 2170 –n • Only few attributes are checked per objectClass • Two types of errors: ERROR or INFO • If ERROR -> Notification is sent to the EGI COD dashboard https://forge.in2p3.fr/projects/opsportaluser/wiki/Operations_Dashboard https://edms.cern.ch/file/1015741/3/dashboardHOWTO.pdf • From the EGI COD dashboard, GGUS tickets can be created Maria Alandes Pradillo, CERN

  4. glue-validator improvements • Using the EGI profile for GLUE 2 • http://go.egi.eu/glue2-profile • One test per attribute • Raise different types of errors • Info, Warning, Error, Fatal • Allow for the possibility of implementing different profiles Maria Alandes Pradillo, CERN

  5. Integration with SAM/Nagios • Retire gstat-sanity-check and focus on improving glue-validator • Replace gstat-sanity-check with glue-validator in SAM/Nagios • Decide what it is a critical error based on the EGI profile for GLUE 2 • Understand with EGI operations what actions should be taken when these critical errors are raised Maria Alandes Pradillo, CERN

  6. LHCb use case • LHCb would like to automatically open GGUS tickets to sites who publish: • GlueCEPolicyAssignedJobSlots=999999999 • GlueHostBenchmarkSI00=0 • How can we automate this? • Since this is Glue 1.3 -> Update gstat-sanity-check • Raise ERROR when GlueCEPolicyAssignedJobSlots=999999999 and GlueHostBenchmarkSI00=0 • Include the new version of gstat-sanity-check in the next SAM release • Update 20 scheduled for mid January 2013 • Expected to be rolled out in all production Nagios instances by the end of January 2013 • Agree with EGI operations what to do with these errors • Presumably LHCb wants a GGUS tickets for these errors Information System meeting with users - 4th December 2012

More Related