Service for AAI: PERUN Availability and Continuity plan

From EGIWiki
Jump to: navigation, 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 Perun and it is the result of the risk assessment conducted for this service: a series of risks and threats has been identified and analyzed, 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 2021-02-10 Feb 2021
Av/Co plan and test 2018-07-13 --

Previous plans are collected here: https://documents.egi.eu/document/3511

Availability requirements and performances

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

  • Availability: 99%
  • Reliability 99%

Other availability requirements:

  • the service is accessible through X509 certificate
  • the service is accessible through EGI-CheckIn (we have a nagios probe which can simulate federated login)
  • the service is accessible via CLI and/or webUI (link to the probes that checks the authentication and the service in general)
  • the Perun RPC is responding, check https://perun.egi.eu/cert/rpc and expect OK as a first two letters

The service availability is regularly tested by nagios probes (eu.egi.cloud.Perun-Check and eu.egi.CertValidity): https://argo-mon.egi.eu/nagios/cgi-bin/status.cgi?servicegroup=SERVICE_egi.Perun&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, PERUN 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

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 Perun database, Perun GUI, Perun engine All components and host machines are regularly backuped on OS and application level. Host is running in redundant virtual environment. LDAP machines are replicated in different geographical locations. Medium up to 8 hours The measures already in place are considered satisfactory and the risk level is acceptable
2 Service unavailable / loss of data due to software failure Perun database, Perun GUI, Perun engine All components and host machines are regularly backuped on OS and application level. LDAP machines are replicated in different geographical locations. Medium up to 8 hours The measures already in place are considered satisfactory and the risk level is acceptable
3 service unavailable / loss of data due to human error Perun database, Perun GUI, Perun engine, LDAP All components and host machines are regularly backuped on OS and application level. Only trained and authorised personnel has an access to the machines and core database. Medium Up to 4 hours The measures already in place are considered satisfactory and the risk level is acceptable
4 service unavailable for network failure (Network outage with causes external of the site) Perun database, Perun GUI, Perun engine, LDAP Data centres has redundant network connections and LDAP servers are located in two geographically distributed data centres. Medium up to 4 hours The measures already in place are considered satisfactory and the risk level is acceptable
5 Unavailability of key technical and support staff (holidays period, sickness, ...) Perun database, Perun engine, Perun GUI At least one person from the core team (7 team members) is still available. Low 1 or more working days The measures already in place are considered satisfactory and the risk level is acceptable
6 Major disruption in the data center. Fire, flood or electric failure for example Perun database, Perun GUI, Perun engine, LDAP All components and host machines are regularly backuped on OS and application level. Machines are located in well maintained and secured data centres. LDAP servers are located in two geographically distributed data centres. Medium up to 8 hours The measures already in place are considered satisfactory and the risk level is acceptable
7 Major security incident. The system is compromised by external attackers and needs to be reinstalled and restored. Perun database, Perun GUI, Perun engine, LDAP All the components has network security monitoring in place and is undert CSIRT teams (EGI-CSIRT, CSIRT-MU and CESNET-CERTS) supervision. All the components are backuped in backup system which cannot be accessible from host machine. Perun software and its components are regularly checked by penetration testing. Medium up to 8 hours The measures already in place are considered satisfactory and the risk level is acceptable
8 (D)DOS attack. The service is unavailable because of a coordinated DDOS. Perun database, Perun GUI Network monitoring is in place and active network elements deployed at CESNET network are able to lower the risk of DDOS attacks. Medium less than 1 hour The measures already in place are considered satisfactory and the 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 is implementing internal procedures for the several countermeasures to invoke in case of risk occurrence, that will be available within the Q1/2020.
  • 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): 3 day
    • 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): 2 days
    • 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.
  • The dedicated Support Unit in the EGI Helpdesk will be used to report any incident or service request.
  • The providers 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

There were no big changes to this service after the execution of the last recovery test (2018 A&C plan), which is considered still valid, so a new test is not required.

Revision History

Version Authors Date Comments

Alessandro Paolini 2018-05-07 first draft, discussing with the provider

Alessandro Paolini 2018-08-02 Plan finalized

Valeria Ardizzone 2019-09-06 start the yearly review

Valeria Ardizzone 2019-12-06 Plan finalized

Alessandro Paolini 2021-02-10 yearly review completed