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.
Difference between revisions of "ARGOMS Availability and Continuity Plan"
Jump to navigation
Jump to search
| Line 48: | Line 48: | ||
| Service unavailable / loss of data due to hardware failure | | Service unavailable / loss of data due to hardware failure | ||
| Argo Messaging Service | | Argo Messaging Service | ||
| | | Automated Deployment and Backup Procedures that allow for rapid redeployment of affected components | ||
| style="background: green"| Low | | style="background: green"| Low | ||
| Restore service from the backups on the new hosts which are not affected by the failure. | | Restore service from the backups on the new hosts which are not affected by the failure. | ||
| Line 57: | Line 56: | ||
| Service unavailable / loss of data due to software failure | | Service unavailable / loss of data due to software failure | ||
| Argo Messaging Service | | Argo Messaging Service | ||
| | | Automated Deployment and Backup Procedures that allow for rapid redeployment of affected components | ||
| style="background: yellow"| Medium | | style="background: yellow"| Medium | ||
| Restore service from the backups, log data analysis in order to find a reason of the software failure. | | Restore service from the backups, log data analysis in order to find a reason of the software failure. | ||
| Line 66: | Line 64: | ||
| service unavailable / loss of data due to human error | | service unavailable / loss of data due to human error | ||
| Argo Messaging Service | | Argo Messaging Service | ||
| | | Automated Deployment and Backup Procedures that allow for rapid redeployment of affected components | ||
| style="background: yellow"| Medium | | style="background: yellow"| Medium | ||
| Restore service/data from backups. Revise actions done which led to the failure and modification of the processes in order to not allow the same error again. | | Restore service/data from backups. Revise actions done which led to the failure and modification of the processes in order to not allow the same error again. | ||
| Line 75: | Line 72: | ||
| 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) | ||
| Argo Messaging Service | | Argo Messaging Service | ||
| | | Automated Deployment and Backup Procedures that allow for rapid redeployment of affected components | ||
| style="background: green"| Low | | style="background: green"| Low | ||
| Standard mitigation and recovery procedures made by network operators. | | Standard mitigation and recovery procedures made by network operators. | ||
| Line 83: | Line 80: | ||
| Unavailability of key technical and support staff (holidays period, sickness, ...) | | Unavailability of key technical and support staff (holidays period, sickness, ...) | ||
| Argo Messaging Service | | Argo Messaging Service | ||
| | | There is always one member of the team on call. | ||
| style="background: green"| Low | | style="background: green"| Low | ||
| | | | ||
| Line 91: | Line 88: | ||
| 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 | ||
| Argo Messaging Service | | Argo Messaging Service | ||
| | | Automated Deployment and Backup Procedures that allow for rapid redeployment of affected components | ||
| style="background: green"| Low | | style="background: green"| Low | ||
| Restore service from the backups on the new hosts which are not affected by the failure. | | Restore service from the backups on the new hosts which are not affected by the failure. | ||
| Line 99: | Line 96: | ||
| 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. | ||
| Argo Messaging Service | | Argo Messaging Service | ||
| | | Automated Deployment and Backup Procedures that allow for rapid redeployment of affected components | ||
| style="background: green"| Low | | style="background: green"| Low | ||
| Restore service from backups on a new hosts. | | Restore service from backups on a new hosts. | ||
| Line 107: | Line 104: | ||
| (D)DOS attack. The service is unavailable because of a coordinated DDOS. | | (D)DOS attack. The service is unavailable because of a coordinated DDOS. | ||
| Argo Messaging Service | | Argo Messaging Service | ||
| | | Automated Deployment and Backup Procedures that allow for rapid redeployment of affected components | ||
| style="background: green"| Low | | style="background: green"| Low | ||
| Utilization of DDOS protection on the network level provided by GRNET. | | Utilization of DDOS protection on the network level provided by GRNET. | ||
Revision as of 17:35, 25 February 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 ARGO Messaging Service and it is the result of the risk assessment conducted for this service: a series of risks and threats 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 | |
|---|---|---|
| Risk assessment | 2019-02-25 | - |
| Av/Co plan and test | - | - |
Performances
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. In the OLA it was agreed the following performances targets, on a monthly basis:
- Availability: 98%
- Reliability 98%
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 | Treatment | Expected duration of downtime / time for recovery |
|---|---|---|---|---|---|---|
| 1 | Service unavailable / loss of data due to hardware failure | Argo Messaging Service | Automated Deployment and Backup Procedures that allow for rapid redeployment of affected components | Low | Restore service from the backups on the new hosts which are not affected by the failure. | Almost Zero |
| 2 | Service unavailable / loss of data due to software failure | Argo Messaging Service | Automated Deployment and Backup Procedures that allow for rapid redeployment of affected components | Medium | Restore service from the backups, log data analysis in order to find a reason of the software failure. | Zero for the case of partial failure. 3-4 work hours if a new virtual machine need to be spawned. |
| 3 | service unavailable / loss of data due to human error | Argo Messaging Service | Automated Deployment and Backup Procedures that allow for rapid redeployment of affected components | Medium | Restore service/data from backups. Revise actions done which led to the failure and modification of the processes in order to not allow the same error again. | Up to 8 hours |
| 4 | service unavailable for network failure (Network outage with causes external of the site) | Argo Messaging Service | Automated Deployment and Backup Procedures that allow for rapid redeployment of affected components | Low | Standard mitigation and recovery procedures made by network operators. | Almost Zero. 3-4 working hours in case of maintenance |
| 5 | Unavailability of key technical and support staff (holidays period, sickness, ...) | Argo Messaging Service | There is always one member of the team on call. | Low | 1 or more working days | |
| 6 | Major disruption in the data centre. Fire, flood or electric failure for example | Argo Messaging Service | Automated Deployment and Backup Procedures that allow for rapid redeployment of affected components | Low | Restore service from the backups on the new hosts which are not affected by the failure. | 1 or more working days |
| 7 | Major security incident. The system is compromised by external attackers and needs to be reinstalled and restored. | Argo Messaging Service | Automated Deployment and Backup Procedures that allow for rapid redeployment of affected components | Low | Restore service from backups on a new hosts. | 3-4 work hours. In case new host certificates are required, up to 1 day. |
| 8 | (D)DOS attack. The service is unavailable because of a coordinated DDOS. | Argo Messaging Service | Automated Deployment and Backup Procedures that allow for rapid redeployment of affected components | Low | Utilization of DDOS protection on the network level provided by GRNET. | Depending on the attack, few hours maximum |
Outcome
The level of all the identified risks is acceptable and the countermeasures already adopted are considered satisfactory
Availability and Continuity test
The proposed A/C test will focus on a recovery scenario: the service has been disrupted and needs to be reinstalled from scratch. The time spent for restoring the service will be measured, using the last backup of the data stored in it and evaluating any eventual loss of information Performing this test will be useful to spot any issue in the recovery procedures of the service.
to do
Revision History
| Version | Authors | Date | Comments |
|---|---|---|---|
| Alessandro Paolini | 2019-02-25 | first draft | |