Alert.png 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.

Applications on Demand EC3 Availability and Continuity Plan

From EGIWiki
Jump to navigation Jump to search
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 EC3 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 2021-10-05
Av/Co plan and test


previous plans are collected here: https://documents.egi.eu/document/3859

Availability requirements and performances

In the OLA it was agreed the following performances targets, on a monthly basis:

  • Availability: 95%
  • Reliability: 95%

Other availability requirements:

  • The service is accessible via CLI and webUI
    • To access the web UI, EGI-Chekin credentials (and memberhip to vo.access.egi.eu VO) are required.
    • The client only needs to set the EGI-Chekin credentials to access EGI Cloud Compute sites.

Look at monitoring history, in case of particular issues

The service availability is regularly tested by nagios probes (org.nagiosexchange.Portal-WebCheck and eu.egi.CertValidity): https://argo-mon.egi.eu/nagios/cgi-bin/status.cgi?servicegroup=SITE_GRIDOPS-EC3_es.upv.grycap.ec3&style=overview

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 EC3 service 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 link). 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 all There are daily backups of the whole VM. In case of error it can be migrated to another cloud provider Low up to 4 hours the measures already in place are considered satisfactory and risk level is acceptable
2 Service unavailable / loss of data due to software failure all There are daily backups of the whole VM. In case of error it can be migrated to another cloud provider. The software, the SO and availability of them is regularly checked using nagios Low up to 4 hours the measures already in place are considered satisfactory and risk level is acceptable
3 service unavailable / loss of data due to human error all All the changes in the code are stored in github. So it can be restored to a previous commit. Low up to 4 hours the measures already in place are considered satisfactory and risk level is acceptable
4 service unavailable for network failure (Network outage with causes external of the site) all Network managed centrally at UPV with established measures to mitigate issues. The availability of the service is regularly checked using external ARGO and an internal nagios Medium up to 4 hours the measures already in place are considered satisfactory and risk level is acceptable
5 Unavailability of key technical and support staff (holidays period, sickness, ...) all The technical staff is available on a best effort basis, during holidays, and it is possible to access using VPN.

Some other technical staff is available to address urgent issues (such as power interruption or similar)

Medium 1 or more working days the measures already in place are considered satisfactory and risk level is acceptable
6 Major disruption in the data centre. Fire, flood or electric failure for example all We have spare parts to replace hardware damages.

We have hardware shared with other projects that can be used temporary In case of major distruption, the service can be migrated to another cloud provider

Medium 1 or more working days the measures already in place are considered satisfactory and risk level is acceptable
7 Major security incident. The system is compromised by external attackers and needs to be reinstalled and restored. all Security updates are applied regularly.

Full daily backup of the VM.

Low up to 4 hours the measures already in place are considered satisfactory and risk level is acceptable
8 (D)DOS attack. The service is unavailable because of a coordinated DDOS. all Network is monitorised

The firewall helps to prevent this kind of attacks

Low up to 8 hours the measures already in place are considered satisfactory and risk level is acceptable

Outcome

The level of all the identified risks is acceptable and the countermeasures already adopted are considered satisfactory

Additional information

  • The provider has procedures for the several countermeasures to invoke in case of risks occurrence (put a link if public).
  • The Availability targets do not 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): 5 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)): 2 days
    • Recovery point objective (RPO) (the acceptable latency of data that will not be recovered): 1 day
  • Approach for the return to normal working conditions as reported in the risk assessment.
  • The support unit Applications on Demand (EC3) shall be used to report any incident or service request
  • The provider 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 1,2, and 7. 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

Test outcome

The whole system can be recovered from the VMs backup in less than 4 hours.

Revision History

Version Authors Date Comments