The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.
Difference between revisions of "Regionalized Nagios use cases"
Jump to navigation
Jump to search
| Line 4: | Line 4: | ||
Nagios/SAM provides regionalized version which is synchronized with the central instance. SAM/Nagios releases follow EGI software release process. List of NGI instances can be found on the following page: [[SAM Instances]]. | Nagios/SAM provides regionalized version which is synchronized with the central instance. SAM/Nagios releases follow EGI software release process. List of NGI instances can be found on the following page: [[SAM Instances]]. | ||
''ATPs at NGI instances are independent from the central one, meaning that they perform synchronization with information sources directly. NGI instance could in theory point ATP to different information sources (e.g. alternative VO feeds).'' | |||
<!-- Copy the block below to add a use case --> | <!-- Copy the block below to add a use case --> | ||
Revision as of 14:13, 17 March 2011
| Main | EGI.eu operations services | Support | Documentation | Tools | Activities | Performance | Technology | Catch-all Services | Resource Allocation | Security |
Current status of regionalization
Nagios/SAM provides regionalized version which is synchronized with the central instance. SAM/Nagios releases follow EGI software release process. List of NGI instances can be found on the following page: SAM Instances.
ATPs at NGI instances are independent from the central one, meaning that they perform synchronization with information sources directly. NGI instance could in theory point ATP to different information sources (e.g. alternative VO feeds).