Difference between revisions of "GGUS Availability and Continuity Plan"

From EGIWiki
Jump to: navigation, search
(Additional information)
(Revision History)
 
(19 intermediate revisions by 2 users not shown)
Line 14: Line 14:
 
|-
 
|-
 
! scope="row"| Risks assessment
 
! scope="row"| Risks assessment
| 2018-04-26
+
| 2021-02-18
| 2019 2nd half
+
| 2022 Feb
 
|-
 
|-
 
! scope="row"| Av/Co plan and test
 
! scope="row"| Av/Co plan and test
| 2018-11-06
+
| 2019-12-02
 
| --
 
| --
 
|-
 
|-
Line 31: Line 31:
 
*Reliability 99%
 
*Reliability 99%
  
<pre style="color: blue"> Other availability requirements:
+
- the service is accessible through either X509 certificate or EGI Check-in
- the service is accessible through X509 certificate and/or other authentication system
+
- The service is accessible via webUI
- The service is accessible via CLI and/or webUI
 
- (depending on the service, specific requirements can be identified. In case, for each requirement report what is the action/measure in case of failure)
 
  
The service availability is regularly tested by nagios probe org.nagiosexchange.Portal-WebCheck and org.nagiosexchange.RT-WebCheck: https://argo-mon.egi.eu/nagios/cgi-bin/status.cgi?servicegroup=SITE_GRIDOPS-CTOOLS_egi.Portal&style=overview https://argo-mon.egi.eu/nagios/cgi-bin/status.cgi?servicegroup=SITE_GRIDOPS-CTOOLS_eu.egi.rt&style=overview
+
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
</pre>
 
  
 
The performances reports in terms of Availability and Reliability are produced by [http://egi.ui.argo.grnet.gr/egi/OPS-MONITOR-Critical ARGO] on an almost real time basis and they are also periodically collected into the [https://documents.egi.eu/public/ShowDocument?docid=2324 Documentation Database].
 
The performances reports in terms of Availability and Reliability are produced by [http://egi.ui.argo.grnet.gr/egi/OPS-MONITOR-Critical ARGO] on an almost real time basis and they are also periodically collected into the [https://documents.egi.eu/public/ShowDocument?docid=2324 Documentation Database].
Line 45: Line 42:
 
= Risks assessment and management =
 
= Risks assessment and management =
  
For more details, please look at the [https://docs.google.com/spreadsheets/d/1tWQ16L3eoiCvVzdzVeDQ6rLgtNAN2_EfXutBMw9jBeo/edit#gid=837150168 google spreadsheet]. We will report here a summary of the assessment.
+
For more details, please look at the [https://docs.google.com/spreadsheets/d/1tWQ16L3eoiCvVzdzVeDQ6rLgtNAN2_EfXutBMw9jBeo/edit#gid=2019351297 google spreadsheet]. We will report here a summary of the assessment.
  
 
== Risks analysis ==
 
== Risks analysis ==
 
<pre style="color: blue"> to update </pre>
 
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 63: Line 58:
 
| Service unavailable / loss of data due to hardware failure
 
| Service unavailable / loss of data due to hardware failure
 
| Web GUI, Webservices, Databases
 
| Web GUI, Webservices, Databases
| fail save architecture, virtualisation solution, integration in on call service
+
| fail save architecture, virtualization solution
| style="background: yellow"| Medium
+
| style="background: green"| Low
 
| up to 4 hours (half working day)
 
| up to 4 hours (half working day)
 
| the measures already in place are considered satisfactory and risk level is acceptable
 
| the measures already in place are considered satisfactory and risk level is acceptable
Line 71: Line 66:
 
| Service unavailable / loss of data due to software failure
 
| Service unavailable / loss of data due to software failure
 
| Web GUI, Webservices, Databases
 
| Web GUI, Webservices, Databases
| fail save architecture, software in version control, integration in on call service
+
| fail save architecture
| style="background: yellow"| Medium
+
| style="background: green"| Low
 
| up to 4 hours (half working day)
 
| up to 4 hours (half working day)
 
| the measures already in place are considered satisfactory and risk level is acceptable
 
| the measures already in place are considered satisfactory and risk level is acceptable
Line 79: Line 74:
 
| service unavailable / loss of data due to human error
 
| service unavailable / loss of data due to human error
 
| Web GUI, Webservices, Databases
 
| Web GUI, Webservices, Databases
| periodical training of on call service staff; system with very restricted access, only accessible by service owner and the team of the on call service
+
| periodical training of on call service staff
| style="background: yellow"| Medium
+
| style="background: green"| Low
 
| up to 4 hours (half working day)
 
| up to 4 hours (half working day)
 
| the measures already in place are considered satisfactory and risk level is acceptable
 
| the measures already in place are considered satisfactory and risk level is acceptable
Line 87: Line 82:
 
| service unavailable for network failure (Network outage with causes external of the site)
 
| service unavailable for network failure (Network outage with causes external of the site)
 
| Web GUI, Webservices, Databases
 
| Web GUI, Webservices, Databases
| two independant network provider
+
| two independent network provider
 
| style="background: green"| Low  
 
| style="background: green"| Low  
 
| up to 4 hours (half working day)
 
| up to 4 hours (half working day)
Line 93: Line 88:
 
|-
 
|-
 
| 5
 
| 5
| Unavailability of key technical and support staff (holidays period, sickness, ...)
+
| Not enough people for maintaining and operating the service
 
| Web GUI, Webservices, Databases
 
| Web GUI, Webservices, Databases
 
| integration in 24/7 on call service
 
| integration in 24/7 on call service
Line 101: Line 96:
 
|-
 
|-
 
| 6
 
| 6
| Major disruption in the data centre. Fire, flood  or electric failure for example
+
| Major disruption in the data centre.
 
| Web GUI, Webservices, Databases
 
| Web GUI, Webservices, Databases
| well organized computing center, power supply (USV), fire alarm system, tape backup at different location
+
| well organised computing center, power supply (USV), fire alarm system, tape backup at different location
 
| style="background: yellow"| Medium  
 
| style="background: yellow"| Medium  
 
| 1 or more working day
 
| 1 or more working day
Line 119: Line 114:
 
| (D)DOS attack. The service is unavailable because of a coordinated DDOS.
 
| (D)DOS attack. The service is unavailable because of a coordinated DDOS.
 
| Web GUI, Webservices, Databases
 
| Web GUI, Webservices, Databases
| preconnected load balancer, fail to ban, firewall
+
| preconnected load balancer, fail to ban, firewall, apache mod_security application firewall
| style="background: yellow"| Medium
+
| style="background: green"| Low
 
| 1 or more working day
 
| 1 or more working day
 
| the measures already in place are considered satisfactory and risk level is acceptable
 
| the measures already in place are considered satisfactory and risk level is acceptable
Line 126: Line 121:
  
 
== Outcome ==
 
== Outcome ==
 
<pre style="color: blue"> to update </pre>
 
  
 
The level of all the identified risks is acceptable and the countermeasures already adopted are considered satisfactory
 
The level of all the identified risks is acceptable and the countermeasures already adopted are considered satisfactory
  
 
== Additional information ==
 
== Additional information ==
<pre style="color: blue">
 
- procedures for the several countermeasures to invoke in case of risk occurrence (put a link if public)
 
 
- 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): 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.
+
* procedures for the several countermeasures to invoke in case of risk occurrence are available to the supplier
</pre>
+
* 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 =
 
= Availability and Continuity test =
  
<pre style="color: blue"> to update </pre>
+
'''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:
 
The proposed A/C test focused on a recovery scenario:
Line 181: Line 172:
 
| 2019-11-25
 
| 2019-11-25
 
| starting the yearly review....
 
| starting the yearly review....
 +
|-
 +
| <br>
 +
| Alessandro Paolini
 +
| 2019-12-02
 +
| review concluded, a new recovery test is not required
 +
|-
 +
| <br>
 +
| Alessandro Paolini
 +
| 2021-02-10
 +
| starting the yearly review....
 +
|-
 +
| <br>
 +
| Alessandro Paolini
 +
| 2021-02-18
 +
| yearly review completed
 
|-
 
|-
 
|
 
|

Latest revision as of 14:48, 18 February 2021

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 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.

Last Next
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

Performances

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

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, 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.

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 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

Outcome

The level of all the identified risks is acceptable and the countermeasures already adopted are considered satisfactory

Additional information

  • 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.

Revision History

Version Authors Date Comments

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