Alert.png 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

Page title matches

Page text matches

  • ...he A/R calculation is related to the OLA. As in case of Operations Portal, availability calculation component receives results from NGI/ROC SAM instances. The procedure for adding Nagios test to Availability and Reliability Profile ([[PROC08|PROC08]]).<br>
    522 bytes (77 words) - 15:15, 24 July 2014
  • It is mandatory that services provide a minimum monthly Availability/Reliability as specified below &nbsp; (see the [https://documents.egi.eu/document/2170 | '''Minimum availability:''' 99% (as a percentage per month)
    4 KB (512 words) - 14:16, 20 March 2015
  • #REDIRECT [[Ticket generator Availability Reliability]]
    55 bytes (5 words) - 17:11, 7 December 2012
  • #REDIRECT [[PROC10 Recomputation of SAM results or availability reliability statistics]]
    88 bytes (10 words) - 17:05, 24 October 2012
  • #REDIRECT [[PROC08 Management of the EGI OPS Availability and Reliability Profile]]
    83 bytes (11 words) - 17:04, 24 October 2012
  • = How to use ticket generator for WI03 (Availability / Reliability followup) = ''ROC/NGI support unit in GGUS; Site name; Availability; Reliability;''
    2 KB (256 words) - 14:48, 23 October 2014
  • ...ry that services operated by EGI.eu provide a minimum monthly Availability/Reliability as specified below &nbsp; (see the [https://documents.egi.eu/public/ShowDoc '''Minimum availability:''' 97% (as a percentage per month)
    21 KB (2,434 words) - 16:13, 29 August 2014
  • ...that EGI certified Resource Centres provide a minimum monthly Availability/Reliability as specified below (see the [https://documents.egi.eu/document/31 RC Operat Availability/Reliability statistics (OPS VO) are issued on a monthly basis.
    2 KB (220 words) - 11:05, 29 September 2014
  • *[[Availability_and_reliability_monthly_statistics|Availability/Reliability monthly statistics]]
    271 bytes (32 words) - 18:04, 24 December 2014
  • == Monthly Availability/Reliability ==
    908 bytes (101 words) - 12:30, 12 October 2015
  • ...SU can also be contacted to request extensions to the correct Availability/Reliability reporting framework. Note: VO-specific Availability/Reliability reports are out of scope.
    2 KB (299 words) - 15:43, 19 April 2016
  • ..._GOCDB#Services NGI&nbsp;core services] operated by NGIs provide a minimum availability of 99% (see the [https://documents.egi.eu/document/463 RP Operational Level | '''Availability'''
    2 KB (240 words) - 11:05, 29 September 2014
  • | Quality verification of monthly availability and reliability statistcs | Availability and Monitoring
    4 KB (526 words) - 19:16, 28 November 2012
  • * an '''AVAILABILITY''' test whose result is used for Resource Centre availability calculation by ACE (see the [https://mon.egi.eu/poem/admin/poem/profile/26/ == Availability and reliability profile ==
    4 KB (655 words) - 11:48, 19 July 2016
  • |O_Task_name = Availability/Reliability statistics ...site scores has lead to better follow up, also increased awareness via the availability wiki about issues in the tools that may affect the accuracy of the results.
    1 KB (181 words) - 16:06, 6 January 2015
  • | Service Monitoring for Availability and Reliability ** The profile for Availability/Reliability computation of EGI Resource Centres (OPS VO), subset of ARGO_MON tests.
    4 KB (629 words) - 11:11, 30 April 2020
  • | '''Availability/reliability followup procedure''' ...//wiki.egi.eu/wiki/PROC04 Quality verification of monthly availability and reliability statistics]<br>
    5 KB (645 words) - 17:27, 2 May 2018
  • ...ilable service. The minimum quality requirements (monthly Availability and Reliability) are defined in the [https://documents.egi.eu/document/463 Resource Infrast = top-BDII Availability and Reliability (no more collected) =
    8 KB (1,175 words) - 13:47, 13 September 2019
  • * Service name: Service Availability Monitoring (SAM) central services ...SON supported). On top of that, the SAM Reporting System generates monthly availability reports about sites and operational tools for use of the EGI management.
    3 KB (491 words) - 15:46, 6 June 2016
  • | '''Availability/reliability followup procedure''' ...//wiki.egi.eu/wiki/PROC04 Quality verification of monthly availability and reliability statistics]<br>
    5 KB (685 words) - 17:17, 28 July 2016
  • * Availability/reliability statistics - Availability/reliability statistics asked for recomputation https://helpdesk.ngi-de.eu/index.php?mod
    2 KB (244 words) - 15:58, 22 March 2013
  • The [[SAM | Service Availability Monitoring (SAM) ]] system is used to monitor the resources within the ...structure. SAM monitoring data is used for calculation of availability and reliability of
    3 KB (488 words) - 12:34, 13 August 2021
  • [[Availability and reliability monthly statistics|Availability and reliability]] [https://operations-portal.egi.eu/availability/topbdiiList AR at Op.Portal]
    3 KB (390 words) - 18:39, 25 November 2014
  • #'''SLM''':&nbsp;Produce '''Availability/Reliability report''' ============= RC Availability Reliability [2]==========
    6 KB (936 words) - 16:18, 30 July 2021
  • == Monthly Availability/Reliability ==
    3 KB (419 words) - 16:36, 11 January 2016
  • == Monthly Availability/Reliability ==
    3 KB (434 words) - 14:56, 20 July 2015
  • *EGI sites availability recalculation procedure was finalized (PROC10) ...nagement Support Unit was created in GGUS and wil be used for availability/reliability issues
    3 KB (389 words) - 19:18, 6 January 2015
  • Given the critical nature of the activity bid must contain an availability and continuity plan for the service. ...ON supported). On top of that, the ARGO Reporting System generates monthly availability reports about sites and operational tools for use of the service owners. In
    4 KB (585 words) - 13:52, 13 March 2018
  • === Operations tool and availability computation === ==== Evaluate the impact of increased availability suspension threshold ====
    6 KB (941 words) - 20:46, 24 December 2014
  • = Availability reporting = ==== Operations tools and availability computations ====
    5 KB (688 words) - 19:59, 24 December 2014
  • =Use case 1: NGI availability reports= We would like to have NGI Availability reports. These reports should include the central services operated by the
    5 KB (821 words) - 16:11, 6 January 2015
  • * Starting from Jan. 2012 the minimum Top-BDII monthly availability of NGIs has to be 99% = 6. NGI Monthly Availability and Reliability Results =
    4 KB (526 words) - 19:18, 6 January 2015
  • * Availability/reliability statistics
    987 bytes (135 words) - 16:18, 5 September 2011
  • ** based on the availability reliability of monitored services in cloudmon, EGI Operations will start follow up with == Monthly Availability/Reliability ==
    6 KB (896 words) - 15:19, 8 February 2016
  • ...s such it is a critical infrastructure component whose continuity and high availability configuration must be ensured. * Testing and high availability configuration
    2 KB (329 words) - 15:47, 6 June 2016
  • ...ON supported). On top of that, the ARGO Reporting System generates monthly availability reports about sites and operational tools for use of the service owners. ...e to a full central deployment, the Monitoring service will include a high availability deployment of Nagios services to monitor the entire EGI Feration (more than
    5 KB (655 words) - 15:19, 6 June 2016
  • ...structure. SAM monitoring data is used for calculation of availability and reliability of grid sites. * an '''AVAILABILITY''' test whose result is used for Resource Centre availability calculation by ACE (see the [https://mon.egi.eu/poem/admin/poem/profile/26/
    7 KB (1,025 words) - 12:15, 13 July 2016
  • GOCDB must be deployed in a master-slave distributed high availability configuration. The two instances cannot be deployed on the same site. *Provisioning of a high availability configuration
    2 KB (330 words) - 15:19, 6 June 2016
  • ...tion monitoring. GOCDB must be deployed in a master-slave distributed high availability configuration. The two instances cannot be deployed on the same site. *Provisioning of a high availability configuration
    2 KB (324 words) - 09:43, 25 October 2016
  • ...AM services and status of A/R mini project, advancement of VO availability/reliability measurement =SA1.8 Availability and core services=
    3 KB (437 words) - 18:17, 6 January 2015
  • = 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 configuration
    3 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 in
    6 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 handle
    4 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 Vi
    6 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 ind
    4 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 loadbalanci
    4 KB (589 words) - 18:59, 6 January 2015
  • =SA1.8 Availability and core services= * distribution of availability/reliability monthly statistics for August
    4 KB (521 words) - 18:15, 6 January 2015
  • * Provisioning of a high availability configuration *Minimum availability/reliability: 99%/99%
    2 KB (337 words) - 15:46, 6 June 2016
  • ...July 3rd. The major change in new versions is module for availability and reliability of core NGI services. Detailed list of new features can be found in JRA1 se |High availability of central operational tools is needed. || '''GOCDB''': dynamic loadbalanci
    4 KB (614 words) - 19:00, 6 January 2015
  • 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 (986 words) - 16:33, 2 July 2021
  • 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,066 words) - 10:53, 9 December 2021
  • ...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 handle
    5 KB (711 words) - 09:46, 25 October 2016
  • 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,130 words) - 12:04, 14 January 2022
  • Back to main page: [[Services Availability Continuity Plans]] ...ailability and continuity of the service. The process is concluded with an availability and continuity test.
    8 KB (1,153 words) - 14:48, 18 February 2021
  • '''Availability followup''' ...es RODs the oportunity to contact and help sites with low availability and reliability in order to prevent A/R GGUS tickets and site suspension.
    7 KB (1,050 words) - 19:15, 6 January 2015
  • ...l provides tools supporting security operations, VO management, broadcast, availability reporting. Both MySQL and the web module are clustered to provide High Availability. Different instances of the services must be deployed to ensure HA.
    4 KB (557 words) - 15:21, 6 June 2016
  • * Provisioning of a high availability configuration ...rship management service for the OPS VO needed to run tests by the Service Availability Monitoring service:
    4 KB (581 words) - 15:45, 6 June 2016
  • * High availability configuration *Minimum availability/reliability: 99%/99%
    3 KB (354 words) - 15:46, 6 June 2016
  • == Monthly Availability/Reliability ==
    6 KB (816 words) - 14:45, 15 November 2021
  • | Operations Tools and Availability Calculation (EGI TF) | Dedicated EGI TF session on operational tools monitoring and availability calculation.
    7 KB (1,076 words) - 19:09, 6 January 2015
  • * Availability/reliability statistics
    2 KB (244 words) - 16:02, 9 March 2012
  • == Monthly Availability/Reliability ==
    6 KB (911 words) - 15:20, 19 June 2017
  • * Availability/reliability statistics
    2 KB (251 words) - 15:56, 8 February 2013
  • == Monthly Availability/Reliability ==
    7 KB (1,044 words) - 15:27, 25 October 2017
  • ** based on the availability reliability of monitored services in cloudmon, EGI Operations will start follow up with == Monthly Availability/Reliability ==
    8 KB (1,224 words) - 13:44, 9 May 2016
  • ** based on the availability reliability of monitored services in cloudmon, EGI Operations will start follow up with == Monthly Availability/Reliability ==
    8 KB (1,237 words) - 10:58, 18 April 2016
  • * The minimum service target (Availability/Reliability) of the NGI Information Discovery service (top-BDII) are set to 99%/99%.
    2 KB (235 words) - 15:54, 15 October 2012
  • **Provisioning of a high availability configuration Provisioning of a high availability configuration
    4 KB (492 words) - 15:20, 6 June 2016
  • **Provisioning of a high availability configuration ...aily running of the system Support Unit maintenance Provisioning of a high availability configuration
    4 KB (492 words) - 17:33, 20 October 2016
  • | Availability and Reliability computation | [[Availability reliability|wiki page]]
    6 KB (805 words) - 13:48, 19 June 2015
  • ...l provides tools supporting security operations, VO management, broadcast, availability reporting. Both MySQL and the web module are clustered to provide High Availability. Different instances of the services must be deployed to ensure HA.
    4 KB (591 words) - 17:36, 20 October 2016
  • * meeting with Availability/Reliability Mini Project, discussion of wider adoption of the software product by EUDAT * revision of May availability statistics
    5 KB (660 words) - 18:25, 6 January 2015
  • ** based on the availability reliability of monitored services in cloudmon, EGI Operations will start follow up with == Monthly Availability/Reliability ==
    7 KB (1,108 words) - 16:42, 14 March 2016
  • === Availability/reliability statistics=== This task includes the validation of distribution of monthly availability statistics, and the coordination of the evolution of the EGI OLA framework.
    9 KB (1,292 words) - 16:17, 6 January 2015
  • ...n status issue. This issue renders the computation of the availability and reliability of sites to inaccurate for some sites and/or NGIs. We consider this to be o ...s and it does not generate alarms or adversely affect the availability and reliability of sites.
    5 KB (725 words) - 19:59, 24 December 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.
    9 KB (1,376 words) - 18:30, 3 January 2022
  • Back to main page: [[Services Availability Continuity Plans]] ...ailability and continuity of the service. The process is concluded with an availability and continuity test.
    8 KB (1,231 words) - 17:43, 10 February 2021
  • ...release and to assess which of these probes will affect site Availability/Reliability in case of failure (affecting In EGI OPS Availability and Reliability Profile:
    5 KB (648 words) - 13:54, 19 June 2015
  • #'''Availability/Reliability metrics''' ##NGI _PL availability for May 94% was&nbsp; and in June&nbsp;96%
    4 KB (582 words) - 17:52, 22 January 2015
  • ...portance of the activity the proposals should include information about an availability and continuity plan for the service. Operations of the delegation service and the online CA in high availability and in compliance with the IGTF and EGI security policies.
    4 KB (581 words) - 09:44, 25 October 2016
  • ...;DB is created by every NGI to make possible to calculate availability and reliability of NGIs based on ava/rel of its core services.<br>
    10 KB (1,556 words) - 16:09, 26 September 2022
  • Back to main page: [[Services Availability Continuity Plans]] ...ailability and continuity of the service. The process is concluded with an availability and continuity test.
    8 KB (1,202 words) - 14:35, 20 May 2020
  • Availability of the technical services: Availability 90%, Reliability 95%
    3 KB (454 words) - 09:49, 25 October 2016
  • ! Avg. Availability&nbsp;% ...age availability and reliability are calculated starting from August (the availability data are not available before in the tool)
    26 KB (3,773 words) - 16:19, 6 January 2015
  • Back to main page: [[Services Availability Continuity Plans]] ...ailability and continuity of the service. The process is concluded with an availability and continuity test.
    8 KB (1,297 words) - 11:54, 14 January 2022
  • * Availability/reliability statistics hours. But we will do a recomputation of the availability statistics
    5 KB (685 words) - 17:39, 20 March 2013
  • Back to main page: [[Services Availability Continuity Plans]] ...ailability and continuity of the service. The process is concluded with an availability and continuity test.
    8 KB (1,269 words) - 11:40, 17 December 2021
  • * Availability/reliability statistics The Availability/Reliability League statistics for July 2011 have been added to
    4 KB (624 words) - 16:20, 5 September 2011
  • The incident has an impact on OPS Availability and Reliability statistics of sites. Statistics will be recomputed automatically by the SAM =SA1.8 Availability and core services= <!--C. Kanellopoulos-->
    7 KB (1,017 words) - 17:46, 6 January 2015
  • * Availability/Reliability miniP meeting, definition of structure for requirements gathering * meeting on layout and functionality of the Operations Portal availability/reliability dashboard
    4 KB (632 words) - 18:24, 6 January 2015
  • * Provisioning of a high availability configuration *Minimum availability/reliability: 99%/99%
    3 KB (460 words) - 15:47, 6 June 2016
  • Back to main page: [[Services Availability Continuity Plans]] ...ailability and continuity of the service. The process is concluded with an availability and continuity test.
    8 KB (1,262 words) - 16:22, 20 January 2022
  • * Management of the EGI OPS Availability and Reliability Profile ([[PROC08]]) === High Availability implementation for Operational Tools ===
    9 KB (1,339 words) - 20:31, 24 December 2014
  • * Participation in the task force on availability/reliability computation * 100% availability/reliability for the topbdii.core.ibergrid.eu service
    4 KB (514 words) - 16:13, 7 January 2015
  • Back to main page: [[Services Availability Continuity Plans]] ...ailability and continuity of the service. The process is concluded with an availability and continuity test.
    8 KB (1,215 words) - 11:31, 3 December 2021
  • As usual attached to the December Availability/Reliability you can find the Availability report for the NGI's Core services (that are Top-BDIIs): [https://documents * Starting from January 2012 Top-BDII below the 99% availability threshold will trigger an official follow-up and NGIs will be requested to
    4 KB (497 words) - 17:19, 29 November 2012
  • == Monthly Availability/Reliability ==
    9 KB (1,263 words) - 15:27, 25 October 2017
  • Back to main page: [[Services Availability Continuity Plans]] ...ailability and continuity of the service. The process is concluded with an availability and continuity test.
    9 KB (1,297 words) - 12:02, 10 January 2022
  • '''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 in
    10 KB (1,681 words) - 19:13, 6 January 2015
  • * Provisioning of a high availability configuration *Minimum availability/reliability: 99%/99%
    3 KB (464 words) - 15:47, 6 June 2016
  • =SA1.8 Availability and core services= <!--C. Kanellopoulos--> *Revision of A/R algorithm for the computation of NGI availability/reliability statistics
    6 KB (913 words) - 18:26, 6 January 2015
  • == Monthly Availability/Reliability ==
    7 KB (1,139 words) - 13:53, 11 February 2019
  • * Availability/reliability statistics The Availability/Reliability League statistics for June 2011 have been added to
    5 KB (765 words) - 16:16, 5 September 2011
  • ...d in a distributed and high available architecture. The bid should include availability and continuity plan(s) for the technical service(s). *Operations in high-availability of all the components described at the beginning of this section
    5 KB (659 words) - 09:44, 25 October 2016
  • * Availability/reliability statistics The Availability/Reliability League statistics for September 2011 have been added to:
    4 KB (606 words) - 15:25, 24 October 2011
  • Back to main page: [[Services Availability Continuity Plans]] ...ailability and continuity of the service. The process is concluded with an availability and continuity test.
    10 KB (1,607 words) - 17:19, 15 December 2021
  • * Participation in the task force on availability/reliability computation * 100% availability/reliability for the topbdii.core.ibergrid.eu service during QR13
    4 KB (586 words) - 16:12, 7 January 2015
  • '''Availability followup''' ...ops portal and it will now generated alarms when a site's availability and reliability is below 70%/75%. As a consequence, COD will stop the activity of monthly i
    9 KB (1,321 words) - 19:11, 6 January 2015
  • == Monthly Availability/Reliability ==
    8 KB (1,215 words) - 14:25, 10 October 2016
  • == Monthly Availability/Reliability - October Underperforming RCs follow-up ==
    6 KB (851 words) - 15:06, 14 December 2015
  • From the experience obtained so far through the Availability/reliability results publication process, a document with proposal to the operations too |November Availability League results were wrong for sites in AT_RISK DT || Issue was investigated
    6 KB (845 words) - 19:16, 6 January 2015
  • 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 (954 words) - 10:39, 10 November 2020
  • == Monthly Availability/Reliability ==
    10 KB (1,524 words) - 13:26, 9 August 2021
  • Back to main page: [[Services Availability Continuity Plans]] ...ailability and continuity of the service. The process is concluded with an availability and continuity test.
    9 KB (1,311 words) - 17:32, 14 May 2021
  • ...moved to https://confluence.egi.eu/display/SUPWORKMAN/EGI+Workload+Manager+Availability+and+Continuity+plan Back to main page: [[Services Availability Continuity Plans]]
    10 KB (1,412 words) - 16:58, 28 January 2022
  • ...astructure: grid oversight, security operations, VO management, broadcast, availability reporting. * Provisioning of a high availability configuration
    5 KB (668 words) - 15:47, 6 June 2016
  • Back to main page: [[Services Availability Continuity Plans]] ...ailability and continuity of the service. The process is concluded with an availability and continuity test.
    9 KB (1,427 words) - 12:18, 7 December 2021
  • == Monthly Availability/Reliability ==
    10 KB (1,550 words) - 15:00, 30 June 2021
  • *Provisioning of a high availability configuration *Minimum availability/reliability: 99%/99% for both the Accounting repositories and the accounting portal
    4 KB (540 words) - 15:18, 6 June 2016
  • == Monthly Availability/Reliability ==
    9 KB (1,377 words) - 14:24, 14 September 2020
  • == Monthly Availability/Reliability ==
    8 KB (1,186 words) - 15:11, 16 November 2020
  • == 2.3 June Availability/Reliability & Sites Suspension == * [https://ggus.eu/?mode=ticket_info&ticket_id=106738 - Availability/Reliability Reports for June 2014]
    10 KB (1,448 words) - 17:30, 23 October 2014
  • *Provisioning of a high availability configuration *Minimum availability/reliability: 99%/99% for both the Accounting repositories and the accounting portal
    4 KB (545 words) - 17:36, 20 October 2016
  • * Provisioning of a high availability configuration *Minimum availability/reliability: 99%/99%
    4 KB (524 words) - 15:45, 6 June 2016
  • Based on the discussions about automating the generation of tickets with availability reports that may require corrections, ticket #1084[https://rt.egi.eu/rt/Tic Impact of increasing the suspension threshold from 50% Availability for 3 consecutive months to 70% has been evaluated and presented in the OMB
    5 KB (749 words) - 19:17, 6 January 2015
  • == Monthly Availability/Reliability ==
    11 KB (1,607 words) - 12:08, 8 July 2021
  • #Availability/Reliability metrics ##Availability Feb/Mar/Apr 98%/95%/&nbsp;???%
    4 KB (619 words) - 16:37, 7 January 2015
  • Back to main page: [[Services Availability Continuity Plans]] ...ailability and continuity of the service. The process is concluded with an availability and continuity test.
    10 KB (1,533 words) - 10:01, 4 August 2021
  • Back to main page: [[Services Availability Continuity Plans]] ...ailability and continuity of the service. The process is concluded with an availability and continuity test.
    9 KB (1,361 words) - 10:42, 7 April 2021
  • #Availability/Reliability metrics ##Availability November/December/January 96%/91%/&nbsp;???%
    5 KB (750 words) - 16:36, 7 January 2015
  • #'''Availability/Reliability metrics''' ##NGI _PL availability for February was 95% and in March 90%
    6 KB (867 words) - 17:52, 22 January 2015
  • | M.SA1.Operation.1, NGI monthly availability and reliability - P ...nerator. This metric is the arithmetic average of the weigted availability/reliability scored by all EGI certified sites. For each site the weight is the amout of
    16 KB (2,273 words) - 16:16, 6 January 2015
  • !Avg. Availability % ...age availability and reliability are calculated starting from August (the availability data are not available before in the tool)
    26 KB (3,918 words) - 16:11, 6 January 2015
  • Back to main page: [[Services Availability Continuity Plans]] ...ailability and continuity of the service. The process is concluded with an availability and continuity test.
    12 KB (1,879 words) - 15:56, 19 April 2021
  • ...cal services within the region. Enhance or extend fault-tolerance and high availability mechanisms. ...e follow up of problems and issues with site performance, availability and reliability. Overall, the NGI is always well above the goals. Contribution to major ope
    7 KB (894 words) - 12:59, 19 February 2013
  • *With WLCG collaboration, EGI league reports now use the new ACE availability calculation system, which supports different profiles, an important step to ...resholds for suspending a site have been increased to 70%/75% Availability/Reliability, based on the evaluation perform in recent months
    4 KB (496 words) - 19:18, 6 January 2015
  • * Provisioning of a high availability configuration *Minimum availability/reliability: 99%/99%
    4 KB (589 words) - 15:46, 6 June 2016
  • * based on the availability reliability of monitored services in cloudmon, EGI Operations will start follow up with == Monthly Availability/Reliability ==
    11 KB (1,725 words) - 14:07, 9 May 2016
  • #Availability/Reliability metrics [https://wiki.egi.eu/wiki/Availability_and_reliability_monthly_stat ##Availability Task Force
    4 KB (517 words) - 16:37, 7 January 2015
  • #Availability/Reliability metrics ##Availability August/September/October 94%/92%/ 89%
    5 KB (672 words) - 15:12, 9 January 2015
  • == Monthly Availability/Reliability ==
    9 KB (1,427 words) - 14:25, 8 October 2018
  • ** Follow up of sites failing to provide 70%/75% monthly availability/reliability ** [[Performance|Follow up of availability issues]] in the country
    7 KB (986 words) - 23:26, 24 December 2014
  • == Monthly Availability/Reliability ==
    8 KB (1,194 words) - 18:22, 14 January 2022
  • ...n status issue. This issue renders the computation of the availability and reliability of sites to inaccurate for some sites and/or NGIs. We consider this to be o ...s and it does not generate alarms or adversely affect the availability and reliability of sites.
    6 KB (898 words) - 20:46, 24 December 2014
  • #Availability/Reliability metrics [https://wiki.egi.eu/wiki/Availability_and_reliability_monthly_stat ##Availability Task Force
    4 KB (466 words) - 16:38, 7 January 2015
  • == Monthly Availability/Reliability ==
    8 KB (1,230 words) - 11:54, 13 December 2021
  • ...ger (SSM) updated - Added a delay when receiver is reconnecting to improve reliability. Improved the log output for SSM receivers so that there are fewer trivial == Monthly Availability/Reliability ==
    11 KB (1,531 words) - 11:33, 22 September 2020
  • == 3.1 Oct Availability/Reliability ==
    9 KB (1,348 words) - 16:03, 18 November 2014
  • * Availability/reliability statistics
    2 KB (325 words) - 15:20, 6 September 2013
  • == Monthly Availability/Reliability ==
    12 KB (1,753 words) - 13:51, 11 October 2021
  • ...ough a GGUS to motivate the poor performance provided. Sites which have an availability of less than 70% for three consecutive months will be suspended.
    7 KB (1,180 words) - 10:36, 8 July 2011
  • == Monthly Availability/Reliability ==
    11 KB (1,694 words) - 13:55, 10 May 2021
  • #Availability/Reliability metrics [https://wiki.egi.eu/wiki/Availability_and_reliability_monthly_stat ##Availability Task Force
    4 KB (532 words) - 16:37, 7 January 2015
  • == Monthly Availability/Reliability ==
    12 KB (1,785 words) - 14:01, 13 September 2021
  • | NGI_RO had low availability/reliability on Q11 overall. This was mainly due to some sites hardware upgrades, and gL
    2 KB (323 words) - 13:37, 9 January 2015
  • ...culation of availability and reliability of NGIs based on availability and reliability of its core services (https://helpdesk.aegis.rs/index.php?mode=ticket_info&
    6 KB (871 words) - 14:03, 9 January 2015
  • == Monthly Availability/Reliability ==
    8 KB (1,160 words) - 15:37, 5 December 2016
  • == Monthly Availability/Reliability ==
    10 KB (1,492 words) - 14:11, 12 November 2018
  • #Availability/Reliability metrics [https://wiki.egi.eu/wiki/Availability_and_reliability_monthly_stat ##Availability Task Force
    4 KB (532 words) - 16:37, 7 January 2015
  • * setting up of a task force for requirements gathering for Availability/Reliability computation (in collaboration with the A/R mini project) =SA1.8 Availability and core services=
    4 KB (545 words) - 18:24, 6 January 2015
  • == Monthly Availability/Reliability ==
    13 KB (1,869 words) - 13:52, 14 October 2019
  • == Monthly Availability/Reliability ==
    10 KB (1,520 words) - 15:02, 14 January 2019
  • == Monthly Availability/Reliability ==
    10 KB (1,533 words) - 15:26, 25 October 2017
  • ...re services= <!--C. Kanellopoulos--> Distribution of July availability and reliability figures
    4 KB (563 words) - 18:15, 6 January 2015
  • ...o&ticket_id=109229 109229] - - site solved the issues and the availability/reliability improved ...nfo&ticket_id=109230 109230] - issues were solved and the availability and reliability are 100%
    29 KB (4,118 words) - 10:33, 10 August 2018
  • * Availability/reliability statistics ...wn during our (KIT, FZKA-LCG2) downtime last week. We will recalculate the availability numbers for
    4 KB (644 words) - 11:32, 22 March 2012
  • == Monthly Availability/Reliability ==
    11 KB (1,646 words) - 13:56, 10 September 2018
  • == Monthly Availability/Reliability ==
    10 KB (1,442 words) - 15:27, 25 October 2017
  • #'''Availability/Reliability metrics''' ...tion of NGI_PL_SERVICES site, designed for calculation RP availability and reliability metrics
    6 KB (824 words) - 17:52, 22 January 2015
  • * setting up database to track top bdii availability, availability/reliability,unknowns of sites, certification status changes and the rod performance ind =SA1.8 Availability and core services=
    5 KB (705 words) - 18:25, 6 January 2015
  • * Availability/reliability statistics -> This two main problems influenced reliability/availability statistics for the August but but we are concerned about the two
    5 KB (859 words) - 10:41, 7 September 2011
  • == Monthly Availability/Reliability ==
    11 KB (1,581 words) - 11:06, 14 June 2016
  • == Monthly Availability/Reliability ==
    9 KB (1,238 words) - 15:04, 9 February 2015
  • * GPGPU resource availability and reliability testing.
    3 KB (405 words) - 03:05, 4 December 2016
  • == 3.1 Monthly Availability/Reliability ==
    10 KB (1,544 words) - 15:22, 12 January 2015
  • == Monthly Availability/Reliability ==
    13 KB (1,956 words) - 16:16, 26 September 2016
  • * Availability/reliability statistics
    3 KB (431 words) - 15:22, 14 June 2013
  • The EGI Availability and Reliability (A/R) reports are being computed on a monthly basis via a centralized infra
    3 KB (470 words) - 11:49, 16 September 2013
  • ...sulted in rejection of submitted results by the engine, and the report for availability showd no data for NGI_MARGI sites.
    4 KB (628 words) - 18:11, 22 January 2015
  • == Monthly Availability/Reliability ==
    12 KB (1,700 words) - 15:26, 25 October 2017
  • .../ws/ticket_info.php?ticket=96877 request to add QCG tests] to Availability Reliability profile =SA1.8 Availability and core services=
    4 KB (638 words) - 18:15, 6 January 2015
  • * Availability/reliability statistics
    3 KB (474 words) - 10:13, 23 April 2012
  • |High availability of central operational tools is needed. || '''GOCDB''': dynamic loadbalanci ...rperforming sites. || COD team has proposed monitoring of availability and reliability of sites. In case of decreased A/R alarm would be raised against the site.
    5 KB (710 words) - 18:59, 6 January 2015
  • |NIHAM had low availability/reliability in Q10
    3 KB (420 words) - 13:37, 9 January 2015
  • == Monthly Availability/Reliability ==
    12 KB (1,785 words) - 13:17, 17 June 2019
  • == Monthly Availability/Reliability ==
    12 KB (1,798 words) - 17:08, 9 July 2019
  • * revision of availability/reliability figures during the last 12 months for planning of an update of unperformanc =SA1.8 Availability and core services=
    5 KB (637 words) - 18:25, 6 January 2015
  • ...upport with Montenegro in order to improve infrastructure availability and reliability.
    3 KB (420 words) - 19:16, 9 January 2015
  • .... Expressions of interest to participate to the task force on availability/reliability computation
    4 KB (487 words) - 15:56, 4 December 2020
  • == Monthly Availability/Reliability ==
    12 KB (1,802 words) - 14:10, 3 July 2018
  • * Configure database replication to improve reliability/availability of the service
    4 KB (556 words) - 19:58, 24 December 2014
  • * Maintained high availability and reliability
    4 KB (530 words) - 14:38, 7 January 2015
  • *Preparation of the EGI Core services availability tables = SA1.8 Availability and core services = <!--C. Kanellopoulos-->
    5 KB (807 words) - 17:45, 6 January 2015
  • ...repository (GOCDB), the accounting repository and portal, and the Service Availability Monitoring framework. ===TJRA1.2.6 Service Availability Monitoring===
    9 KB (1,275 words) - 20:58, 24 December 2014
  • ...ls for virtual organisations, a new approach to computing availability and reliability, enhancements to EGI’s service registry to support other projects and inf | TSA4.10: A new approach to Computing Availability and Reliability Reports
    8 KB (1,255 words) - 14:27, 8 October 2013
  • == Monthly Availability/Reliability ==
    12 KB (1,655 words) - 14:00, 9 September 2019
  • ...sted by the new mini-project "A new approach to Computing Availability and Reliability Reports".
    3 KB (506 words) - 18:53, 6 January 2015
  • * Operations Portal: discussion of VO availability/reliability computation algorithm for implementation of the first prototype * request of input on availability of a SSM2 central DB (in production) from collection of usage records from
    6 KB (884 words) - 18:24, 6 January 2015
  • * Availability/reliability statistics
    3 KB (495 words) - 17:19, 13 February 2012
  • * Management of the EGI OPS Availability and Reliability Profile ([[PROC08]]) |High availability of central operational tools is needed. || '''GOCDB''': dynamic loadbalanci
    5 KB (802 words) - 18:59, 6 January 2015
  • * Meeting on VO availability and reliability statistics + NGI statistics: discussion on how to consume topology, status =SA1.8 Availability and core services=
    5 KB (796 words) - 18:17, 6 January 2015
  • ...l security, and maintenance are compatible amongst all partners, improving availability and lowering access barriers for use of the infrastructure. This coordinati *Minimum availability/reliability: 90%/90%
    6 KB (909 words) - 15:21, 6 June 2016
  • == Monthly Availability/Reliability ==
    13 KB (1,850 words) - 14:02, 15 April 2019
  • == Monthly Availability/Reliability ==
    13 KB (1,869 words) - 09:57, 27 May 2019
  • ...GIs. The central monitoring services are critical and need to deliver high availability.
    9 KB (1,304 words) - 16:20, 6 January 2015
  • == Monthly Availability/Reliability ==
    14 KB (2,212 words) - 12:04, 14 May 2018
  • == Monthly Availability/Reliability ==
    13 KB (2,044 words) - 13:21, 12 June 2018
  • ...iod, All NGI_DE sites ran the Grid services well with the availability and reliability as high as 96.7% in average. Operation problems were discussed in the regul ...the information system and CREAM CE, which influenced the availability and reliability. ||The CREAM CE problem was caused by lack of memory. It was solved.
    7 KB (1,037 words) - 15:39, 7 January 2015
  • == Monthly Availability/Reliability ==
    12 KB (1,759 words) - 15:31, 7 November 2016
  • Minimum availability/reliability: 95%/95%
    4 KB (582 words) - 15:21, 6 June 2016
  • ...e and maturity, Resource Centres were operated reliability and the overall availability of EGI services was not affected by the start of the operations of the new ...eted in January 2011 without affecting the infrastructure availability and reliability.
    23 KB (3,456 words) - 16:19, 6 January 2015
  • * NGI_BY solved some seriuos network problems that caused law Availability/Reliability statistics during the period of Q6.
    3 KB (494 words) - 16:39, 6 January 2015
  • == Monthly Availability/Reliability ==
    18 KB (2,649 words) - 14:25, 8 June 2020
  • ...nal security, and maintenance are compatible among all partners, improving availability and lowering access barriers for use of the infrastructure. This coordinati *Minimum availability/reliability: 90%/90%
    7 KB (990 words) - 17:30, 20 October 2016
  • ...sted by the new mini-project "A new approach to Computing Availability and Reliability Reports". Due to the new developments release of Operations Portal was post
    4 KB (545 words) - 18:53, 6 January 2015
  • == Monthly Availability/Reliability ==
    14 KB (2,142 words) - 14:25, 9 April 2018
  • * NGI_BY Availability/Reliability statistics has been improved during the period of Q5.
    3 KB (495 words) - 16:40, 6 January 2015
  • * Availability/reliability statistics
    4 KB (575 words) - 17:20, 13 February 2012
  • * Availability/reliability statistics
    3 KB (502 words) - 13:12, 6 October 2011
  • ...being further developed by volunteering NGIs, to improve the usability and reliability. The status of HINTS has been reported by FranceGrilles and UREC; the curre *'''Availability/Reliability'''
    12 KB (1,829 words) - 18:44, 22 January 2015
  • == Monthly Availability/Reliability ==
    14 KB (2,174 words) - 14:04, 16 July 2018
  • = SA1.8 Availability and core services= <!--C. Kanellopoulos--> * Published the EGI Availability and Reliability Reports for August 2012
    6 KB (851 words) - 17:44, 6 January 2015
  • To assure reliability and availability of national top BDII service we started preparation for deployment of HA se
    4 KB (515 words) - 18:41, 22 January 2015
  • * Availability/reliability statistics
    4 KB (596 words) - 16:45, 30 November 2012
  • Minimum availability/reliability: 95%/95%
    4 KB (623 words) - 09:46, 25 October 2016
  • Back to main page: [[Services Availability Continuity Plans]] ...ailability and continuity of the service. The process is concluded with an availability and continuity test.
    16 KB (2,213 words) - 11:00, 6 January 2022
  • * Availability/reliability statistics
    4 KB (561 words) - 17:29, 17 May 2013
  • == Monthly Availability/Reliability ==
    13 KB (1,943 words) - 09:12, 13 April 2019
  • * Availability/reliability statistics problem site (BMRZ-FRANKFURT) ticket 1304, 73%/73% availability/reliability
    8 KB (1,304 words) - 16:18, 5 September 2011
  • ...ngagement with new communities, consider outreach event subject to funding availability ...ith minimal disruption. NGI developed a VOMS configuration tool to improve reliability of new VO enablement.
    5 KB (578 words) - 15:07, 22 February 2013
  • ...paign in GOCDB of NGI core services in preparation to the NGI availability/reliability monthly statistics =SA1.8 Availability and core services=
    6 KB (884 words) - 18:20, 6 January 2015
  • ...work will be to set up database replication to improve the reliability and availability of the service.
    4 KB (665 words) - 19:02, 6 January 2015
  • * Availability/reliability statistics
    4 KB (632 words) - 14:55, 28 September 2012
  • * Availability/reliability statistics
    4 KB (638 words) - 23:29, 16 July 2012
  • * Availability and Reliability statistics for Feburary, March and April were excellent - The exception wa
    4 KB (623 words) - 18:45, 22 January 2015
  • == Monthly Availability/Reliability ==
    18 KB (2,466 words) - 15:25, 25 October 2017
  • ...-NAGIOS production release was installed in January increasing the overall reliability of the service.
    7 KB (1,040 words) - 18:46, 22 January 2015
  • .... Expressions of interest to participate to the task force on availability/reliability computation ...t of tests generating results that are taken into account for Availability/Reliability reports)
    28 KB (4,120 words) - 10:48, 1 May 2015
  • *All NGI_CZ sites have more than 90% in availability and reliability.
    4 KB (649 words) - 15:10, 7 January 2015
  • # M. Caballer et al, Platform to Ease the Deployment and Improve the Availability of TRENCADIS Infrastructure | Platform to Ease the Deployment and Improve the Availability of TRENCADIS Infrastructure
    15 KB (2,150 words) - 16:12, 7 January 2015
  • ...federated operations centres encompassing multiple NGIs. Availability and Reliability reached 94.50% and 95.42% (yearly average), which amounts to a +1% increase ...es and sites, and a hardened DNS-based failover configuration. The Service Availability Monitoring (SAM) underwent five different upgrades and is currently the lar
    36 KB (5,349 words) - 16:20, 6 January 2015
  • #'''Availability/Reliability metrics''' ##NGI _PL availability for August 80% and in September 89; low A/R due to new services and hardwar
    7 KB (1,068 words) - 17:52, 22 January 2015
  • ...oothly operating Grid services in the region. The service availability and reliability achieved both 100%. Hardware capacities (storage & CPU) was kept increasing
    4 KB (611 words) - 15:37, 7 January 2015
  • Improved availability/reliability numbers - fixed problems with national BDII and WMS, which lead to bad moni
    5 KB (667 words) - 15:10, 7 January 2015
  • * 100% availability/reliability for the topbdii.core.ibergrid.eu service
    5 KB (654 words) - 16:13, 7 January 2015
  • ...eral virtual organizations are operated with satisfactory availability and reliability level. New requirements on the services are provided quickly.
    6 KB (956 words) - 18:56, 19 December 2012
  • == Monthly Availability/Reliability ==
    15 KB (2,190 words) - 15:24, 25 October 2017
  • == Monthly Availability/Reliability ==
    22 KB (3,091 words) - 15:26, 25 October 2017
  • ...ntrol framework for parallel scientific applications aiming to improve the reliability and efficiency of job execution by providing automatic load balancing, fine * Increase reliability and success rate for job management
    12 KB (1,703 words) - 11:33, 23 November 2012
  • ...pers of DCI applications to use EGI and its resources due to the immediate availability of the software that they need to use; and 2) to avoid duplication of effor ...of databases for the persistent storage of information about test results, Availability statistics, monitoring profiles and aggregated topology information. The ce
    30 KB (4,383 words) - 23:06, 24 December 2014
  • * Availability and Reliability statistics for November, December and January were excellent (despite misce
    5 KB (690 words) - 18:46, 22 January 2015
  • ...request from WLCG, we have developed a schema to support TopBDIIs in high availability mode. # Assessement of the high availability schema for the regional TopBDIIs
    10 KB (1,436 words) - 18:46, 22 January 2015
  • ...ying ARGO and raising a fake alarm in case of low results (Availability or Reliability - average values for the last 30 days )
    17 KB (2,286 words) - 16:53, 10 October 2019
  • == Monthly Availability/Reliability ==
    7 KB (995 words) - 14:14, 12 October 2020
  • |Low availability/reliability numbers for prague_cesnet_lcg2 cluster in December (73%)|| Problem was inv
    5 KB (742 words) - 15:10, 7 January 2015
  • ...for the registration of NGI services in order to produce NGI Availability/Reliability statistics ** Resource amount, availability and reliability.
    11 KB (1,566 words) - 18:43, 22 January 2015
  • #'''Availability/Reliability metrics'''
    6 KB (815 words) - 19:04, 9 January 2015
  • ...d implementation of suggested mitigation methods in order to maintain high availability of NGI_AEGIS top-BDII instance. * Maintaining an excellent NGI availability/reliability and ROD performance index metrics.
    7 KB (1,068 words) - 18:41, 22 January 2015
  • ...mation and for the computation of performance indicators (availability and reliability). SAM is installed by individual National Grid Initiatives, monitoring data
    9 KB (1,334 words) - 14:38, 2 June 2014
  • #'''Availability/Reliability metrics'''
    5 KB (747 words) - 18:03, 22 January 2015
  • ...pers of DCI applications to use EGI and its resources due to the immediate availability of the software that they need to use; and 2) to avoid duplication of effor ...of databases for the persistent storage of information about test results, Availability statistics, monitoring profiles and aggregated topology information. The ce
    32 KB (4,677 words) - 23:07, 24 December 2014
  • ...eing further developed by volunteering NGIs, to improve the usability and reliability. The status of HINTS has been reported by FranceGrilles and UREC; the curr 3. Continue the investigation on how to improve availability and reliability metrics.
    10 KB (1,676 words) - 19:13, 6 January 2015
  • ...e best practices, the tools they are familair with, and asking about theri availability to provide a PERT contact point for the EGI project. 4. Initiate the investigation on how to improve availability and reliability metrics.
    11 KB (1,737 words) - 19:12, 6 January 2015
  • order to improve and check availability and reliability statics for MPI sites a
    596 KB (64,758 words) - 11:10, 8 February 2013
  • == Monthly Availability/Reliability ==
    9 KB (1,230 words) - 13:28, 11 January 2021
  • *** APEL-SSM 2.1.7 - Added a delay when receiver is reconnecting to improve reliability. Improved the log output for SSM receivers so that there are fewer trivial ...release in UMD4/C7. Added a delay when receiver is reconnecting to improve reliability. Improved the log output for SSM receivers so that there are fewer trivial
    14 KB (2,066 words) - 15:25, 25 October 2017
  • ...goc.egi.eu EGI Service Registry (GOCDB)] to activate the availability and reliability monitoring for the framework with the [http://argo.egi.eu EGI ARGO] service ...perational Level Agreement (OLA) defining for example the availability and reliability targets, helpdesk ticket response times.
    25 KB (3,775 words) - 12:04, 23 December 2020
  • == Monthly Availability/Reliability ==
    9 KB (1,341 words) - 14:55, 8 February 2021
  • * Availability/reliability statistics
    7 KB (1,086 words) - 15:54, 17 November 2011
  • Monitoring in this context is the monitoring of the availability and reliability of the cloud resources provided by the resource providers. What will be tes
    9 KB (1,323 words) - 10:26, 23 September 2015
  • * Investigations about what can be done to increase VOs' reliability with VO Nagios box and Vapor * [CompEng] Started: Background work for supporting the use of Availability Profiles in the computations
    12 KB (1,709 words) - 23:04, 24 December 2014
  • ...n the operations area by making sure that the infrastructure delivers high availability, is secure, meets the demand of existing user communities and that infrastr ...l security, and maintenance are compatible amongst all partners, improving availability and lowering access barriers for use of the infrastructure. Today, the Secu
    45 KB (6,684 words) - 16:17, 6 January 2015
  • **Availability **Reliability
    23 KB (3,236 words) - 17:23, 17 January 2014
  • * Resource amount, availability and reliability.
    7 KB (1,078 words) - 19:18, 9 January 2015
  • ...c/RetrieveFile?docid=2305&version=2&filename=EGI_Sep2014.pdf Availability/Reliability Reports for Sept 2014]
    8 KB (1,131 words) - 17:31, 23 October 2014
  • == Monthly Availability/Reliability ==
    11 KB (1,610 words) - 12:41, 9 March 2021
  • ...for the registration of NGI services in order to produce NGI Availability/Reliability statistics
    8 KB (1,208 words) - 18:46, 22 January 2015
  • == Monthly Availability/Reliability ==
    16 KB (2,342 words) - 14:38, 13 January 2020
  • == Monthly Availability/Reliability ==
    15 KB (2,324 words) - 15:21, 10 February 2020
  • == Monthly Availability/Reliability ==
    16 KB (2,344 words) - 14:44, 16 March 2020
  • == Monthly Availability/Reliability ==
    12 KB (1,824 words) - 14:31, 12 April 2021
  • == Monthly Availability/Reliability ==
    9 KB (1,378 words) - 15:25, 25 October 2017
  • ...GIs. The central monitoring services are critical and need to deliver high availability. ...Resource Communities are provided by various technical services to collect availability, accounting and monitoring information about their VOs. The VO Services gro
    23 KB (3,395 words) - 18:36, 19 December 2012
  • | align="left" | [[Fedcloud-tf:WorkGroups:Scenario5|Reliability/Availability of Resource Providers]]
    12 KB (1,632 words) - 17:32, 24 October 2016
  • == Monthly Availability/Reliability ==
    17 KB (2,511 words) - 15:20, 20 April 2020
  • ...iod NGI_DE keeps the Grid running smoothly in the region. Availability and Reliability was kept high (96% in average). Operation problems are discussed in the reg
    9 KB (1,322 words) - 15:39, 7 January 2015
  • |Availability |Reliability
    10 KB (1,421 words) - 15:57, 30 July 2015
  • # Nagios probes: New monitoring probes for the EGI Service Availability Monitor (SAM) has been defined. These will be implemented and put into pro *Checking for MPI availability -- mostly decided by checking installed applications.
    18 KB (2,818 words) - 09:04, 18 February 2014
  • Availability and reliability threshold should be defined with EGI Operations team depending on the criti
    12 KB (1,799 words) - 15:20, 18 September 2019
  • == Monthly Availability/Reliability ==
    13 KB (2,032 words) - 10:16, 20 March 2018
  • ...ches: modularise the Core Monitoring Engine, monitoring availability &amp; reliability as a Cloud Service and provide clean interfaces for end-users, operations a ...racing of resource centre configuration, monitoring of resources delivery, availability analysis for agreed services, capacity reports analysis and billing. Anothe
    18 KB (2,697 words) - 16:54, 13 January 2016
  • == Monthly Availability/Reliability ==
    19 KB (2,747 words) - 14:04, 11 May 2020
  • In EGI OPS Availability and Reliability Profile:
    13 KB (1,995 words) - 13:55, 19 June 2015
  • == Monthly Availability/Reliability ==
    15 KB (2,202 words) - 15:24, 11 December 2017
  • ...eployed monitoring the general service reachability, OCCI availability and reliability, EGI Accounting compliance, and Information Discovery service compliance. T
    23 KB (3,100 words) - 11:29, 10 December 2013
  • == Monthly Availability/Reliability ==
    15 KB (2,254 words) - 15:43, 20 November 2017
  • == Monthly Availability/Reliability ==
    16 KB (2,358 words) - 15:33, 15 January 2018
  • ...ce registry, a Virtual Machine Image marketplace, service availability and reliability monitoring service, usage accounting system and user certificate generation
    12 KB (1,636 words) - 13:16, 26 June 2015
  • == Monthly Availability/Reliability ==
    17 KB (2,469 words) - 15:04, 12 February 2018
  • With a common language at hand, presence and availability discovery of services and resources is possible without ambiguity. Through ...cture resources is inherently dynamic, changes in a resource’s state (e.g. availability, or load) are propagated through messaging facilities and endpoints.
    40 KB (5,743 words) - 14:59, 24 October 2014
  • EGI OPS Availability and Reliability Profile:
    18 KB (2,664 words) - 13:54, 19 June 2015
  • Details on Resource Centres availability and reliability are available on [http://argo.egi.eu/lavoisier/cloud_reports?accept=html AR
    38 KB (4,930 words) - 09:09, 20 December 2019
  • |Availability |Reliability
    33 KB (4,816 words) - 09:42, 12 July 2016