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.

Difference between revisions of "EGI Notebooks Availability and Continuity Plan"

From EGIWiki
Jump to navigation Jump to search
Line 129: Line 129:
== Test details ==
== Test details ==


The proposed A/C test checks if the recovery from a disruption can be performed by installing from scratch all the service. The last user data will be backed up and time spent will be measure.  
The proposed A/C test checks if the recovery from a disruption can be performed by installing from scratch all the service. The last user data will be backed up and time spent will be measured.  


Performing this test will be useful to spot any issue in the recovery procedures of the service.
Performing this test will be useful to spot any issue in the recovery procedures of the service.

Revision as of 07:22, 3 June 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 EGI Notebooks 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 2019-05-28 2020-05-28
Av/Co plan and test 2019-05-28 2020-05-28

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: 90%
  • Reliability 90%

So far Notebooks didn't have any 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

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 the service components Service configuration and deployment on Kubernetes and managed as code in git repositories.

(Daily) Backup of user storage

Medium up to 1 day the measures already in place are considered satisfactory and risk level is acceptable
2 Service unavailable / loss of data due to software failure All the service components Service configuration and deployment on Kubernetes and managed as code in git repositories.

(Daily) Backup of user storage

Low up to 1 day the measures already in place are considered satisfactory and risk level is acceptable
3 service unavailable / loss of data due to human error All the service components Service configuration and deployment on Kubernetes and managed as code in git repositories.

(Daily) Backup of user storage

Medium up to 1 day 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 the service components Service configuration and deployment on Kubernetes and managed as code in git repositories.

(Daily) Backup of user storage

Low up to 1 day 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 service components None High 1 or more working days Documentation and training needed to increase the staff capable of managing the service.
6 Major disruption in the data centre. Fire, flood or electric failure for example All the service components Service configuration and deployment on Kubernetes and managed as code in git repositories.

(Daily) Backup of user storage

Low up to 1 working day 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 the service components Service configuration and deployment on Kubernetes and managed as code in git repositories.

(Daily) Backup of user storage

Low up to 1 working day 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 the service components Service configuration and deployment on Kubernetes and managed as code in git repositories.

(Daily) Backup of user storage

Low up to 1 working day 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

Availability and Continuity test

Test details

The proposed A/C test checks if the recovery from a disruption can be performed by installing from scratch all the service. The last user data will be backed up and time spent will be measured.

Performing this test will be useful to spot any issue in the recovery procedures of the service.

Test outcome

Revision History

Version Authors Date Comments