Difference between revisions of "EOSC Portal Availability and Continuity Plan"
Line 55: | Line 55: | ||
| 1 | | 1 | ||
| Service unavailable / loss of data due to hardware failure | | Service unavailable / loss of data due to hardware failure | ||
| EOSC Portal user GUI, EOSC Portal database | |||
| | | | ||
| | | | ||
| | |||
| | |||
|- | |||
| 2 | |||
| Service unavailable / loss of data due to CEPH file system in the cloud infrastructure | |||
| EOSC Portal user GUI, EOSC Portal database | |||
| | | | ||
| | | | ||
| | | | ||
| | |||
|- | |- | ||
| | | 3 | ||
| Service unavailable / loss of data due to software failure | | Service unavailable / loss of data due to software failure | ||
| | | EOSC Portal user GUI, EOSC Portal database | ||
| | | | ||
| | | | ||
Line 69: | Line 77: | ||
| | | | ||
|- | |- | ||
| | | 4 | ||
| service unavailable / loss of data due to human error | | service unavailable / loss of data due to human error | ||
| | | EOSC POrtal user GUI | ||
| | | | ||
| | | | ||
Line 77: | Line 85: | ||
| | | | ||
|- | |- | ||
| | | 5 | ||
| service unavailable for network failure (Network outage with causes external of the site) | | service unavailable for network failure (Network outage with causes external of the site) | ||
| | | | ||
Line 85: | Line 93: | ||
| | | | ||
|- | |- | ||
| | | 6 | ||
| Unavailability of key technical and support staff (holidays period, sickness, ...) | | Unavailability of key technical and support staff (holidays period, sickness, ...) | ||
| | | EOSC Portal user GUI, EOSC Portal database | ||
| | | | ||
| | | | ||
Line 93: | Line 101: | ||
| | | | ||
|- | |- | ||
| | | 7 | ||
| Major disruption in the data centre. Fire, flood or electric failure for example | | Major disruption in the data centre. Fire, flood or electric failure for example | ||
| | | EOSC Portal user GUI, EOSC Portal database | ||
| | | | ||
| | | | ||
Line 101: | Line 109: | ||
| | | | ||
|- | |- | ||
| | | 8 | ||
| Major security incident. The system is compromised by external attackers and needs to be reinstalled and restored. | | Major security incident. The system is compromised by external attackers and needs to be reinstalled and restored. | ||
| | | EOSC POrtal user GUI | ||
| | | | ||
| | | | ||
Line 109: | Line 117: | ||
| | | | ||
|- | |- | ||
| | | 9 | ||
| (D)DOS attack. The service is unavailable because of a coordinated DDOS. | | (D)DOS attack. The service is unavailable because of a coordinated DDOS. | ||
| | | |
Revision as of 14:11, 19 June 2020
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 |
Back to main page: Services Availability Continuity Plans
work in progress
Introduction
This page reports on the Availability and Continuity Plan for the EOSC 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 likelihood of the occurrence of a risk, or its impact, 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.
Last | Next | |
---|---|---|
Risks assessment | ||
Av/Co plan and test |
Availability requirements and performances
List the Service Level Targets as agreed in the OLA/UA Other ava requirements: the service is accessible through X509 certificate and/or other authentication system The service is accessible via CLI and/or webUI (link to the probes that checks the authentication and the service in general) (depending on the service, specific requirements can be identified. In case, for each requirement report what is the action/measure in case of failure) Look at monitoring history, in case of particular issues
Risks assessment and management
For more details, please look at the google spreadsheet. We will report here a summary of the assessment.
Risks analysis
Risk id | Risk description | Affected components | Established measures | Risk level | Expected duration of downtime / time for recovery | Comment |
---|---|---|---|---|---|---|
1 | Service unavailable / loss of data due to hardware failure | EOSC Portal user GUI, EOSC Portal database | ||||
2 | Service unavailable / loss of data due to CEPH file system in the cloud infrastructure | EOSC Portal user GUI, EOSC Portal database | ||||
3 | Service unavailable / loss of data due to software failure | EOSC Portal user GUI, EOSC Portal database | ||||
4 | service unavailable / loss of data due to human error | EOSC POrtal user GUI | ||||
5 | service unavailable for network failure (Network outage with causes external of the site) | |||||
6 | Unavailability of key technical and support staff (holidays period, sickness, ...) | EOSC Portal user GUI, EOSC Portal database | ||||
7 | Major disruption in the data centre. Fire, flood or electric failure for example | EOSC Portal user GUI, EOSC Portal database | ||||
8 | Major security incident. The system is compromised by external attackers and needs to be reinstalled and restored. | EOSC POrtal user GUI | ||||
9 | (D)DOS attack. The service is unavailable because of a coordinated DDOS. |
Outcome
Additional information
procedures for the several countermeasures to invoke in case of risk occurrence (put a link if public) Specify if the Availability targets are different in case the plan is invoked. Specify the recovery requirements (in general they are the outcomes of the BIA). Specify if there is a particular approach for the return to normal working conditions if different from what already reported in the risk assessment. The support unit ... shall be used to report any incident or service request The providers can contact EGI Operations via ticket or email in case the continuity plan is invoked, or to discuss any change to it.
Availability and Continuity test
The proposed A/C test will focus on a recovery scenario: the service is supposed to have been disrupted and needs to be reinstalled from scratch. Typically this covers the risks #,#, and #. The last backup of the data will be used for restoring the service, verifying how much information will be lost, and the time spent will be measured. Performing this test will be useful to spot any issue in the recovery procedures of the service.
Test details and outcome
Revision History
Version | Authors | Date | Comments |
---|---|---|---|