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

View (previous 50 | next 50) (20 | 50 | 100 | 250 | 500)