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 (org.nagios.ARGOWeb-AR and org.nagios.ARGOWeb-Status): https://argo-mon.egi.eu/nagios/cgi-bin/status.cgi?host=argo.egi.eu&style=detail
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||All||All services are running on virtual machines. In case of hardware failure of the host machine, the virtual machine can be re-instantiated in another hypervisor in the private cloud. Daily backups of the service including database data.||Low||In case an instance must be instantiated from backups can take up to two-three working hours. In case the latest backups are not available some data must be re-generate from the central accounting repositories and this may take up to two 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||All||Restoring of the codebase via git repository||Low||One to two working 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||All||Restoring of the codebase via git repository, restore of backup of the virtual machine, restoring of data from SSM services.||Low||Two to Three working 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)||Web frontend||CESGA has redundant network connectivity to the NREN||Low||Close to zero, less than one hour.||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, ...)||All||More personnel have been involved in the operation of the Accounting portal, this ensures actions taken within the OLA goals every working day. There is also internal documentation with management procedures and portal architecture.||Low||Within the OLA targets for operational actions Longer periods in case of bugs or maintenance (one week) because not all the personnel can develop patches to the code.||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||All||The computing center has an electric backup system and fire control devices. In case of an occurrence despite the controls, the virtual machine can be instantiated elsewhere.||Low||1-2 weeks, the time to deploy recover operational status at CESGA or the service to another resource center partner of the NGI||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.||Frontend and DB||Daily backup is executed. Backup is stored in a separate system and can be restored in another VM||Low||1-2 work hours. In case new host certificates are required, up to 2 days.||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.||Web interface||NREN provides protection for DOS attacks, a firewall can limit the impact of the DDoS||Low||Depending on the attack, few hours maximum||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 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.
(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 ...|