Difference between revisions of "Operations Portal Availability and Continuity Plan"
Line 45: | Line 45: | ||
| External network connectivity outage. Network outage with causes external of the site (e.g. internet provider outage) | | External network connectivity outage. Network outage with causes external of the site (e.g. internet provider outage) | ||
| Cluster web / Databases / Lavoisier | | Cluster web / Databases / Lavoisier | ||
| | | RENATER has redundant network connectivity | ||
| text | | text | ||
| text | | text | ||
Line 53: | Line 53: | ||
| Hardware failure | | Hardware failure | ||
| Cluster web / Databases | | Cluster web / Databases | ||
| | | Web service and databases are hosted on a cluster of machines.The other nodes will continue to work | ||
| text | | text | ||
| text | | text | ||
Line 61: | Line 61: | ||
| Hardware failure | | Hardware failure | ||
| Lavoisier | | Lavoisier | ||
| | | Lavoisier configuration is stored centrally . One machine could be restarted with the same configuration in 15 min.The interruption is short . | ||
| text | | text | ||
| text | | text | ||
Line 69: | Line 69: | ||
| Unavailability of key technical and support staff (holidays period, sickness, ...) | | Unavailability of key technical and support staff (holidays period, sickness, ...) | ||
| Cluster web / Databases | | Cluster web / Databases | ||
| | | No measures | ||
| text | | text | ||
| text | | text | ||
Line 77: | Line 77: | ||
| 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 | ||
| Cluster web / Databases | | Cluster web / Databases | ||
| | | The computing centre has electric backup system and fire control devices | ||
| text | | text | ||
| text | | text | ||
Line 85: | Line 85: | ||
| 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. | ||
| Cluster web / Databases / Lavoisier | | Cluster web / Databases / Lavoisier | ||
| | | The backend database store is operated in clustered mode with backups. The code is stored in Gitlab and stored in backup files . Lavoisier is stateless and does not store historical datas. So there is no problem to start a new Operations Portal from backup and new machines. | ||
| text | | text | ||
| text | | text | ||
Line 93: | Line 93: | ||
| (D)DOS attack. The service is unavailable because of a coordinated DDOS. | | (D)DOS attack. The service is unavailable because of a coordinated DDOS. | ||
| Cluster web / Databases | | Cluster web / Databases | ||
| | | RENATER and local team network provides protection for DOS attacks, firewall can limit impact of the DDoS | ||
| text | | text | ||
| text | | text |
Revision as of 17:05, 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.
In the OLA it was agreed the following performances targets, on a monthly basis:
- Availability 99%
- Reliability 99%
Over the past years, the Operations Portal hadn't particular Av/Co issues highlighted by the performances that need to be further investigated.
Risks assessment and management
For more details, please look at the google spreadsheet. We will report here a summary of the assessment.
Risk id | Risk description | Affected components | Established measures | Risk level | Expected duration of downtime | Comment |
---|---|---|---|---|---|---|
1 | External network connectivity outage. Network outage with causes external of the site (e.g. internet provider outage) | Cluster web / Databases / Lavoisier | RENATER has redundant network connectivity | text | text | text |
2 | Hardware failure | Cluster web / Databases | Web service and databases are hosted on a cluster of machines.The other nodes will continue to work | text | text | text |
3 | Hardware failure | Lavoisier | Lavoisier configuration is stored centrally . One machine could be restarted with the same configuration in 15 min.The interruption is short . | text | text | text |
4 | Unavailability of key technical and support staff (holidays period, sickness, ...) | Cluster web / Databases | No measures | text | text | text |
5 | Major disruption in the data centre. Fire, flood or electric failure for example | Cluster web / Databases | The computing centre has electric backup system and fire control devices | text | text | text |
6 | Major security incident. The system is compromised by external attackers and needs to be reinstalled and restored. | Cluster web / Databases / Lavoisier | The backend database store is operated in clustered mode with backups. The code is stored in Gitlab and stored in backup files . Lavoisier is stateless and does not store historical datas. So there is no problem to start a new Operations Portal from backup and new machines. | text | text | text |
7 | (D)DOS attack. The service is unavailable because of a coordinated DDOS. | Cluster web / Databases | RENATER and local team network provides protection for DOS attacks, firewall can limit impact of the DDoS | text | text | text |