Difference between revisions of "Operations Portal Availability and Continuity Plan"
Line 20: | Line 20: | ||
= Performances = | = Performances = | ||
The performances reports in therms of Availability and Reliability are produced by [[http://argo.egi.eu/ar-opsmon ARGO]] on an almost real time basis and they are also collected every 6 months into the Documentation Database (last period | The performances reports in therms of Availability and Reliability are produced by [[http://argo.egi.eu/ar-opsmon ARGO]] on an almost real time basis and they are also collected every 6 months into the Documentation Database (last period [https://documents.egi.eu/document/3270 July 2017 - December 2017]. | ||
= Risks assessment and management = | = Risks assessment and management = |
Revision as of 16:21, 27 March 2018
Main | EGI.eu operations services | Support | Documentation | Tools | Activities | Performance | Technology | Catch-all Services | Resource Allocation | Security |
Documentation menu: | Home • | Manuals • | Procedures • | Training • | Other • | Contact ► | For: | VO managers • | Administrators |
work in progress
Service Availability and continuty plan structure
- Performances (A/R targets agreed in the OLA, comment about the past behaviour and any particular issue)
- summary of the risks assessment
- Av.Co. tests and results
Introduction
This page reports on the Availability and Continuity Plan for the Operations Portal and it is the result of the risks assessment conducted for this service: a series of risks and treats has been identified and analysed, along with the correspondent countermeasures currently in place. Whenever a countermeasure is not considered satisfactory for either avoiding or reducing the likely of the occurrence of a risk, it is agreed with the service provider a new treatment for improving the availability and continuity of the service. The process is concluded with an availability and continuity test.
Performances
The performances reports in therms of Availability and Reliability are produced by [ARGO] on an almost real time basis and they are also collected every 6 months into the Documentation Database (last period July 2017 - December 2017.