GGUS 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 the GGUS 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.
|Risks assessment||2021-02-18||2022 Feb|
|Av/Co plan and test||2019-12-02||--|
Previous plans are collected here: https://documents.egi.eu/secure/ShowDocument?docid=3542
In the OLA it was agreed the following performances targets, on a monthly basis:
- Availability 99%
- Reliability 99%
- the service is accessible through either X509 certificate or EGI Check-in - The service is accessible via webUI
The service availability is regularly tested by nagios probe org.nagiosexchange.GGUS-WebCheck and eu.egi.CertValidity: https://argo-mon.egi.eu/nagios/cgi-bin/status.cgi?host=ggus.eu&style=detail
Over the past years, the GGUS helpdesk system 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||Web GUI, Webservices, Databases||fail save architecture, virtualization solution||Low||up to 4 hours (half working day)||the measures already in place are considered satisfactory and risk level is acceptable|
|2||Service unavailable / loss of data due to software failure||Web GUI, Webservices, Databases||fail save architecture||Low||up to 4 hours (half working day)||the measures already in place are considered satisfactory and risk level is acceptable|
|3||service unavailable / loss of data due to human error||Web GUI, Webservices, Databases||periodical training of on call service staff||Low||up to 4 hours (half working 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)||Web GUI, Webservices, Databases||two independent network provider||Low||up to 4 hours (half working day)||the measures already in place are considered satisfactory and risk level is acceptable|
|5||Not enough people for maintaining and operating the service||Web GUI, Webservices, Databases||integration in 24/7 on call service||Low||1 or more working day||the measures already in place are considered satisfactory and risk level is acceptable|
|6||Major disruption in the data centre.||Web GUI, Webservices, Databases||well organised computing center, power supply (USV), fire alarm system, tape backup at different location||Medium||1 or more 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.||Web GUI, Webservices, Databases||server configuration according to best practices, most recent patch installation of OS, virus protection, firewall||Medium||1 or more 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.||Web GUI, Webservices, Databases||preconnected load balancer, fail to ban, firewall, apache mod_security application firewall||Low||1 or more working day||the measures already in place are considered satisfactory and risk level is acceptable|
The level of all the identified risks is acceptable and the countermeasures already adopted are considered satisfactory
- procedures for the several countermeasures to invoke in case of risk occurrence are available to the supplier
- the Availability and Reliability 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): 2 days
- 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)): 1 day
- Recovery point objective (RPO) (the acceptable latency of data that will not be recovered): 1 day
- approach for the return to normal working conditions as reported in the risk assessment.
- The dedicated GGUS Support Unit 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, which is considered still valid, so a new test is not required.
The proposed A/C test focused on a recovery scenario:
- database was corrupted and a backup version has to be imported;
- result: after importing the backup the system was up and running again without any further problems;
- the import of the backup took ~30 minutes;
- in such a scenario the data gathered between backup and database crash may be lost. In worst case this may be data of 1 day (24 hours).
The test can be considered successful: restoring the service took relatively few time (while GGUS is unavailable, the Operations Portal Dashboard will be in read-only mode, and the regional helpdesk systems interfaced to GGUS will only miss the connection with it), and even if 1 day data at most are lost, new tickets can be opened again after restoring the service, and replies to tickets can be posted again.
|Alessandro Paolini||2018-04-26||first draft, discussing with the provider.|
|Alessandro Paolini||2018-11-06||added the information about the test; plan finalised.|
|Alessandro Paolini||2019-11-25||starting the yearly review....|
|Alessandro Paolini||2019-12-02||review concluded, a new recovery test is not required|
|Alessandro Paolini||2021-02-10||starting the yearly review....|
|Alessandro Paolini||2021-02-18||yearly review completed|