Service for AAI: PERUN Availability and Continuity plan
|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
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.
|Risk assessment||2018-05-05||May 2019|
|Av/Co plan and test||2018-07-13||July 2019|
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
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.
|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||database, GUI, provisioning engine||All components and host machines are regularly backuped on OS and application level. The host is running in a redundant virtual environment.||Low||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||database, GUI, provisioning engine||All components and host machines are regularly backuped on OS and application level.||Low||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||database, GUI, provisioning engine, LDAP||All components and host machines are regularly backuped on OS and application level. Only trained personel has an access to the machines.||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)||GUI, LDAP||Data centers has redundant network connections and LDAP servers are located in two different data centers.||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, ...)||database, GUI, provisioning engine, LDAP||At least one person from the core team (5 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||database, GUI, provisioning engine||All components and host machines are regularly backuped on OS and application level. Machines are located in well maintained and secured data centers. LDAP is located in two different data centers.||Low||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.||database, GUI, engine, LDAP||All the components has network security monitoring in place and is undert CSIRT team 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.||Low||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.||GUI, LDAP||Network monitoring is in place and active network elemetns 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|
- 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 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.
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 a new test)
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.
|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 ...|