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.
Search results
Jump to navigation
Jump to search
- = Availability reporting = ==== Operations tools and availability computations ====6 KB (846 words) - 19:59, 24 December 2014
- *Provisioning of a high availability configuration *Minimum availability/reliability: 99%/99%2 KB (260 words) - 15:21, 21 October 2016
- == Monthly Availability/Reliability ==5 KB (701 words) - 22:36, 9 March 2015
- == Monthly Availability/Reliability ==4 KB (586 words) - 14:18, 15 June 2015
- '''Availability and Reliability calculations formulas:''' <pre>Availability = Uptime / (Total time - Time_status_was_UNKNOWN)4 KB (543 words) - 14:51, 23 October 2014
- Back to main page: [[Services Availability Continuity Plans]] ...ailability and continuity of the service. The process is concluded with an availability and continuity test.6 KB (953 words) - 14:56, 14 October 2021
- ...l core infrastructure platform service component whose continuity and high availability configuration must be ensured. *Daily running of the system in high availability configuration3 KB (368 words) - 15:18, 6 June 2016
- '''Availability followup''' ...elopment that is going to raise an alarm when a site's avaliability and/or reliability is below the 70%/75% threshold. The COD has provided input which was put in6 KB (1,036 words) - 19:13, 6 January 2015
- == Monthly Availability/Reliability ==5 KB (698 words) - 13:08, 21 April 2015
- ...re) and [[Availability and reliability monthly statistics|Availability and reliability monthly statistics]] (reports). New procedure has been created [[PROC16|PRO == Availability reporting ==7 KB (1,032 words) - 19:15, 6 January 2015
- ...l core infrastructure platform service component whose continuity and high availability configuration must be ensured. Given the critical nature of the activity bid must contain an availability and continuity plan for the service.3 KB (455 words) - 15:53, 19 October 2016
- == Availability == ...t-end, as well as the community repository, must have 90% availability and reliability on a monthly base.5 KB (774 words) - 15:45, 6 June 2016
- ...er components used by the UMD team only must have 75% availability and 90% reliability during working hours. Load Balancing and high availability configuration (between two or more servers) is required in order to handle4 KB (642 words) - 15:47, 6 June 2016
- ...ability statistics|PROC04 Quality verification of monthly availability and reliability statistcs ]]3 KB (580 words) - 14:44, 23 October 2014
- Back to main page: [[Services Availability Continuity Plans]] ...ailability and continuity of the service. The process is concluded with an availability and continuity test.7 KB (1,033 words) - 16:34, 2 August 2021
- == Reliability and availability improvements == Although Virtual Queues improve reliability, they can have a negative impact on the scalability of the service. Each Vi6 KB (914 words) - 11:40, 21 January 2012
- * assessment of progress of MiniP on Availability/Reliability computation * setting up database to track top bdii availability, availability/reliability,unknowns of sites, certification status changes and the rod performance ind4 KB (571 words) - 18:25, 6 January 2015
- ''ROC/NGI support unit in GGUS; Availability; Reliability;''1 KB (213 words) - 14:48, 23 October 2014
- Monitoring of availability and reliability of sites and raising alarms in case of issues will be implemented within Op |High availability of central operational tools is needed. || '''GOCDB''': dynamic loadbalanci4 KB (589 words) - 18:59, 6 January 2015
- =SA1.8 Availability and core services= * distribution of availability/reliability monthly statistics for August4 KB (521 words) - 18:15, 6 January 2015