Difference between revisions of "ARGOMS Availability and Continuity Plan"

From EGIWiki
Jump to: navigation, search
(Risks analysis)
(Risks analysis)
Line 80: 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
| Automated Deployment and Backup Procedures that allow for rapid redeployment of affected components
+
| There is always one member of the team on call.
 
| style="background: green"| Low  
 
| style="background: green"| Low  
 
| Redirect DNS to poin to one the 3 instances runinng behind the HA/LB Service while we reinstall/migrate the Service in a new VM and update DNS
 
| Redirect DNS to poin to one the 3 instances runinng behind the HA/LB Service while we reinstall/migrate the Service in a new VM and update DNS

Revision as of 16:39, 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 Redirect DNS to poin to one the 3 instances runinng behind the HA/LB Service while we reinstall/migrate the Service in a new VM and update DNS 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 Low Redirect DNS to poin to one the 3 instances runinng behind the HA/LB Service while we reinstall/migrate the Service in a new VM and update DNS 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 Low Redirect DNS to poin to one the 3 instances runinng behind the HA/LB Service while we reinstall/migrate the Service in a new VM and update DNS 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 Redirect DNS to poin to one the 3 instances runinng behind the HA/LB Service while we reinstall/migrate the Service in a new VM and update DNS 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 Redirect DNS to poin to one the 3 instances runinng behind the HA/LB Service while we reinstall/migrate the Service in a new VM and update DNS 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 Medium Redirect DNS to poin to one the 3 instances runinng behind the HA/LB Service while we reinstall/migrate the Service in a new VM and update DNS 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 Redirect DNS to poin to one the 3 instances runinng behind the HA/LB Service while we reinstall/migrate the Service in a new VM and update DNS 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 Redirect DNS to poin to one the 3 instances runinng behind the HA/LB Service while we reinstall/migrate the Service in a new VM and update DNS 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