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 @

Service for AAI: PERUN Availability and Continuity plan

From EGIWiki
Jump to navigation Jump to search
Main 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


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 2018-05-05 May 2019
Av/Co plan and test 2018-07-13 July 2019

Previous plans are collected here:

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 and expect OK as a first two letters

The service availability is regularly tested by nagios probes (org.nagios.ARGOWeb-AR and org.nagios.ARGOWeb-Status):

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

(to review)

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 Low
2 Service unavailable / loss of data due to software failure Low
3 service unavailable / loss of data due to human error Low
4 service unavailable for network failure (Network outage with causes external of the site) Low
5 Unavailability of key technical and support staff (holidays period, sickness, ...) Low
6 Major disruption in the data centre. Fire, flood or electric failure for example Low
7 Major security incident. The system is compromised by external attackers and needs to be reinstalled and restored. Low
8 (D)DOS attack. The service is unavailable because of a coordinated DDOS. Low


Additional information

- procedures for the several countermeasures to invoke in case of risk occurrence (put a link if public)
-- the procedures are not yet developed. We have internal plan to have such procedures ready in 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): 1 working 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 (this has to be less than MTPoD)): 2 working days
-- Recovery point objective (RPO) (the acceptable latency of data that will not be recovered): 2 working days

- approach for the return to normal working conditions as reported in the risk assessment.

- The GGUS Support Unit "ARGO/SAM EGI Support" 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.

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.

Test details

(to do a new test)

Test outcome

The test can be considered successful: even if it takes longer to restore the service, the other components of the infrastructure can use the last data available before the downtime; managing users and groups is not an hourly or daily activity, it is performed when needed, so even if the service is unavailable for few hours or a day, this can be acceptable.

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 starting the yearly review ...