Difference between revisions of "EOSC Portal Availability and Continuity Plan"

From EGIWiki
Jump to: navigation, search
(Introduction)
(Availability and Continuity test)
 
(2 intermediate revisions by the same user not shown)
Line 27: Line 27:
  
 
= Availability requirements and performances =
 
= Availability requirements and performances =
 +
<pre style="color: blue">
 +
List the Service Level Targets as agreed in the OLA/UA
  
In the OLA it was agreed the following performances targets, on a monthly basis:
+
Other ava requirements:
*Availability: 90%
 
*Reliability 95%
 
  
Other availability requirements:
+
the service is accessible through X509 certificate and/or other authentication system
*the service is accessible through X509 certificate and Check-in
+
The service is accessible via CLI and/or webUI (link to the probes that checks the authentication and the service in general)
*the service is accessible via 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)
 
+
Look at monitoring history, in case of particular issues
The service availability is regularly tested by nagios probe org.nagiosexchange.Portal-WebCheck: https://argo-mon.egi.eu/nagios/cgi-bin/status.cgi?servicegroup=SITE_EGI-MARKETPLACE_egi.Portal&style=overview
+
</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].
 
  
 
= Risks assessment and management =
 
= Risks assessment and management =
Line 139: Line 137:
  
 
= Availability and Continuity test =
 
= Availability and Continuity test =
 
+
<pre style="color: blue">
The proposed A/C test will focus on a recovery scenario: the service is supposed to have been disrupted and needs to be reinstalled from scratch.  
+
The proposed A/C test will focus on a recovery scenario: the service is supposed to have been disrupted and needs to be reinstalled from scratch. Typically this covers the risks #,#, and #. The last backup of the data will be used for restoring the service, verifying how much information will be lost, and the time spent will be measured.
The last backup of the data will be used for restoring the service, verifying how much information will be lost, and the time spent will be measured.
 
  
 
Performing this test will be useful to spot any issue in the recovery procedures of the service.
 
Performing this test will be useful to spot any issue in the recovery procedures of the service.
 +
</pre>
  
 
== Test details and outcome ==
 
== Test details and outcome ==
Line 157: Line 155:
 
|-
 
|-
 
| <br>
 
| <br>
| Alessandro Paolini
+
|  
| 2019-07-24
+
|  
| first draft, discussing with the provider
+
|
|-
 
| <br>
 
| Alessandro Paolini
 
| 2019-08-22
 
| the provider confirmed there is no hardware HA configuration; added new content about Ava requirements (to be refined) and additional information in risk assessment section (to be refined); the provider is going to plan a recovery test.
 
|-
 
| <br>
 
| Alessandro Paolini
 
| 2019-11-28
 
| plan finalised
 
 
|-
 
|-
 
| <br>
 
| <br>

Latest revision as of 16:17, 20 May 2020

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

work in progress

Introduction

This page reports on the Availability and Continuity Plan for the EOSC Portal 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
Av/Co plan and test

Availability requirements and performances

List the Service Level Targets as agreed in the OLA/UA

Other ava requirements:

the service is accessible through X509 certificate and/or other authentication system 
The service is accessible via CLI and/or webUI (link to the probes that checks the authentication and the service in general)
(depending on the service, specific requirements can be identified. In case, for each requirement report what is the action/measure in case of failure)
Look at monitoring history, in case of particular issues

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

Outcome

Additional information

procedures for the several countermeasures to invoke in case of risk occurrence (put a link if public)

Specify if the Availability targets are different in case the plan is invoked.

Specify the recovery requirements (in general they are the outcomes of the BIA).

Specify if there is a particular approach for the return to normal working conditions if different from what already reported in the risk assessment.

The support unit ... shall 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

The proposed A/C test will focus on a recovery scenario: the service is supposed to have been disrupted and needs to be reinstalled from scratch. Typically this covers the risks #,#, and #. The last backup of the data will be used for restoring the service, verifying how much information will be lost, and the time spent will be measured.

Performing this test will be useful to spot any issue in the recovery procedures of the service.

Test details and outcome

Revision History

Version Authors Date Comments