Difference between revisions of "Operations Portal Availability and Continuity Plan"
Line 57: | Line 57: | ||
! Risk level | ! Risk level | ||
! Expected duration of downtime / time for recovery | ! Expected duration of downtime / time for recovery | ||
! | ! Treatment (Protective, mitigation measures, recovery activities, controls) | ||
|- | |- | ||
| 1 | | 1 | ||
Line 65: | Line 65: | ||
| style="background: green"| Low | | style="background: green"| Low | ||
| 1 min | | 1 min | ||
| the | | Recovery activities : daily backup , protective measures / controls : monitoring of the nodes | ||
|- | |- | ||
| 2 | | 2 | ||
Line 73: | Line 73: | ||
| style="background: green"| Low | | style="background: green"| Low | ||
| 1 min | | 1 min | ||
| the | | Recovery activities : daily backup , protective measures / controls : monitoring of the nodes | ||
|- | |- | ||
| 3 | | 3 | ||
Line 81: | Line 81: | ||
| style="background: yellow"| Medium | | style="background: yellow"| Medium | ||
| 15 min | | 15 min | ||
| the | | Protective measures / controls : monitoring of the nodes , Recovery activities : the pre-production instance could be restarted in production mode, if it is a problem of configuration we can revert it from gitlab | ||
|- | |- | ||
| 4 | | 4 | ||
Line 89: | Line 89: | ||
| style="background: yellow"| Medium | | style="background: yellow"| Medium | ||
| 15 min | | 15 min | ||
| the | | Protective measures / controls : monitoring of the nodes , Recovery activities : the pre-production instance could be restarted in production mode, if it is a problem of configuration we can revert it from gitlab | ||
|- | |- | ||
| 5 | | 5 | ||
Line 97: | Line 97: | ||
| style="background: yellow"| Medium | | style="background: yellow"| Medium | ||
| 1 working day | | 1 working day | ||
| | | mutiple and redundant links to renater | ||
|- | |- | ||
| 6 | | 6 | ||
Line 105: | Line 105: | ||
| style="background: yellow"| Medium | | style="background: yellow"| Medium | ||
| 1 or more working days | | 1 or more working days | ||
| the | | Monitoring of the services, vpn accesses to work from home | ||
|- | |- | ||
| 7 | | 7 | ||
Line 113: | Line 113: | ||
| style="background: yellow"| Medium | | style="background: yellow"| Medium | ||
| less than 1 hour | | less than 1 hour | ||
| the | | Monitoring of the building and mutlple redundant systems (electricity and cooling systems) | ||
|- | |- | ||
| 8 | | 8 | ||
Line 121: | Line 121: | ||
| style="background: yellow"| Medium | | style="background: yellow"| Medium | ||
| until the resolution of the security incident | | until the resolution of the security incident | ||
| | | Security monitoring systems | ||
|- | |- | ||
| 9 | | 9 | ||
Line 129: | Line 129: | ||
| style="background: yellow"| Medium | | style="background: yellow"| Medium | ||
| until the end of the attack | | until the end of the attack | ||
| | | Security monitoring systems, firewall | ||
|} | |} | ||
Revision as of 15:52, 6 December 2019
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
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.
Last | Next | |
---|---|---|
Risks assessment | 2018-03-23 | 2019 March |
Av/Co plan and test | in progress | -- |
Previous plans are collected here: https://documents.egi.eu/secure/ShowDocument?docid=3538
Performances
In the OLA it was agreed the following performances targets, on a monthly basis:
- Availability 99%
- Reliability 99%
Other availability requirements:
- the service is accessible through EOSC AAI and EGI Checkin
- the service is also accessible with a certificate by using "IGTF Proxy certificate" in AAI
- a web service is also exposing information through REST API
The service availability is regularly tested by nagios probe org.nagiosexchange.OpsPortal-WebCheck: https://argo-mon.egi.eu/nagios/cgi-bin/status.cgi?servicegroup=SERVICE_egi.OpsPortal&style=detail
The performances reports in terms of Availability and Reliability are produced by ARGO on an almost real time basis and they are also periodically collected into the Documentation Database.
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.
Risks analysis
to update
Risk id | Risk description | Affected components | Established measures | Risk level | Expected duration of downtime / time for recovery | Treatment (Protective, mitigation measures, recovery activities, controls) |
---|---|---|---|---|---|---|
1 | Service unavailable / loss of data due to hardware failure | Cluster web / Databases | Web service and databases are hosted on a cluster of machines. The other nodes will continue to work | Low | 1 min | Recovery activities : daily backup , protective measures / controls : monitoring of the nodes |
2 | Service unavailable / loss of data due to software failure | Cluster web / Databases | Web service and databases are hosted on a cluster of machines. The other nodes will continue to work | Low | 1 min | Recovery activities : daily backup , protective measures / controls : monitoring of the nodes |
3 | Service unavailable / loss of data due to software failure | Lavoisier | The configuration of Lavoisier is stored centrally . We can spawn a new machine to replace it or we can use the pre-production instance | Medium | 15 min | Protective measures / controls : monitoring of the nodes , Recovery activities : the pre-production instance could be restarted in production mode, if it is a problem of configuration we can revert it from gitlab |
4 | service unavailable / loss of data due to human error | Lavoisier | The configuration of Lavoisier is stored centrally . We can spawn a new machine to replace it or we can use the pre-production instance | Medium | 15 min | Protective measures / controls : monitoring of the nodes , Recovery activities : the pre-production instance could be restarted in production mode, if it is a problem of configuration we can revert it from gitlab |
5 | service unavailable for network failure (Network outage with causes external of the site) | Cluster web / Databases | RENATER has redundant network connectivity | Medium | 1 working day | mutiple and redundant links to renater |
6 | Not enough people for maintaining and operating the service | Cluster web / Databases | The team is trying to take holidays with always one people at the office. Only 2 periods are not covered generally 25th-26th December and August 15th | Medium | 1 or more working days | Monitoring of the services, vpn accesses to work from home |
7 | Major disruption in the data centre. | Cluster web / Databases | The computing centre has electric backup system and fire control devices, the data-center has 2 separated machine rooms | Medium | less than 1 hour | Monitoring of the building and mutlple redundant systems (electricity and cooling systems) |
8 | Major security incident. The system is compromised by external attackers and needs to be reinstalled and restored. | Cluster web / Databases / Lavoisier | Regular upgrades of the components , check CVE and known vulnerabilities, isolation of the components | Medium | until the resolution of the security incident | Security monitoring systems |
9 | (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 | Medium | until the end of the attack | Security monitoring systems, firewall |
Countermeasures to improve
to update
The risk number 4 doesn't have countermeasures in place and needs to be handled.
The provider will try to avoid, where possible, that the people in the staff take vacations at the same time. All the staff can access remotely to the services in case of need.
Additional information
- procedures for the several countermeasures to invoke in case of risk occurrence (put a link if public) - the Availability targets don't change in case the plan is invoked. - recovery requirements: -- Maximum tolerable period of disruption (MTPoD) (the maximum amount of time that a service can be unavailable or undelivered after an event that causes disruption to operations, before its stakeholders perceive unacceptable consequences): 2 days -- Recovery time objective (RTO) (the acceptable amount of time to restore the service in order to avoid unacceptable consequences associated with a break in continuity (this has to be less than MTPoD)): 1 day -- Recovery point objective (RPO) (the acceptable latency of data that will not be recovered): 2 days - approach for the return to normal working conditions as reported in the risk assessment.
Availability and Continuity test
to update
The proposed A/C test will focus on a recovery scenario: the service has been disrupted and needs to be reinstalled from scratch.
We have made the test for the Lavoisier Component .
To simulate the disruption it was
- stopped the lavoisier service - deleted the repository with the lavoisier configuration
Then for the recovery part :
- Get the lavoisier engine - wget a zip file and unzip it - Get the local configuration - git clone - Add properties: passwords and sensitive information - stored in gitlab variables - Add the certificate - locale copy from laptop - Restart the service
- Duration : ~ 8 min
- Start : Thu Nov 8 14:10:26 CET 2018
- End : Thu Nov 8 14:18:49 CET 2018
The recovery test can be considered successful since restoring the service after a disruption to the Lavoisier component took very few time, well inside the Maximum tolerable period of disruption for this service.
Revision History
Version | Authors | Date | Comments |
---|---|---|---|
Alessandro Paolini | 2018-03-27 | first draft, discussing with the provider | |
Cyril l'Orphelin, Alessandro Paolini | 2018-11-08 | added information on the recovery test; plan finalised. | |
Alessandro Paolini | 2019-11-19 | starting the yearly review.... | |