Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.

Difference between revisions of "ARGO Monitoring Availability and Continuity Plan"

From EGIWiki
Jump to navigation Jump to search
Line 51: Line 51:
<pre style="color: blue">(to review)</pre>
<pre style="color: blue">(to review)</pre>


For more details, please look at the [https://docs.google.com/spreadsheets/d/1rB6JSywfxVZ9GIIHWo1askSRz8oRMC9DzkW9LLVJ898/edit#gid=1565906040 google spreadsheet]. We will report here a summary of the assessment.
For more details, please look at the google spreadsheet. We will report here a summary of the assessment.


== Risks analysis ==
== Risks analysis ==
Line 90: Line 90:
| 4
| 4
| 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)
| APEL-SSM receiver and sender
|  
| Up to three days worth of accounting messages can be cached on the EGI message brokers which can then be retrieved once service is restored.
|  
| style="background: green"| Low  
| style="background: green"| Low  
| up to 4 hours (half working day)
|  
| the measures already in place are considered satisfactory and risk level is acceptable
|  
|-
|-
| 5
| 5
| Unavailability of key technical and support staff (holidays period, sickness, ...)
| Unavailability of key technical and support staff (holidays period, sickness, ...)
| Any
|  
| As well as having two staff in the APEL team, administration of the service can also be covered by GOCDB staff and, to a limited extent, other staff within the department.
|  
| style="background: green"| Low  
| style="background: green"| Low  
| 1 or more working days
|  
| the measures already in place are considered satisfactory and risk level is acceptable
|  
|-
|-
| 6
| 6
| Major disruption in the data centre. Fire, flood  or electric failure for example
| Major disruption in the data centre. Fire, flood  or electric failure for example
| All
|  
| Fire suppression systems and generator backed UPS
|  
| style="background: green"| Low  
| style="background: green"| Low  
| 1 or more working days
|  
| the measures already in place are considered satisfactory and risk level is acceptable
|  
|-
|-
| 7
| 7
| Major security incident. The system is compromised by external attackers and needs to be reinstalled and restored.
| Major security incident. The system is compromised by external attackers and needs to be reinstalled and restored.
|  
|  
| Daily backup are executed. Backup is stored in a separate system and can be restored in another system
|  
| style="background: green"| Low  
| style="background: green"| Low  
| up to 8 hours (1 working day)
|  
| the measures already in place are considered satisfactory and risk level is acceptable
|  
|-
|-
| 8
| 8
| (D)DOS attack. The service is unavailable because of a coordinated DDOS.
| (D)DOS attack. The service is unavailable because of a coordinated DDOS.
| APEL-SSM receiver
|  
| Authentication and authorisation required to send messages via the brokers and messages are additionally checked when received at the Repository
|  
| style="background: green"| Low
|  
| up to 8 hours (1 working day)
|  
| the measures already in place are considered satisfactory and risk level is acceptable
|  
|}
|}



Revision as of 11:22, 21 August 2019

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


(previous plans are collected here: https://documents.egi.eu/document/3007 https://rt.egi.eu/rt/Ticket/Display.html?id=12323)

Hardware HA Configuration

(taken from OLA)

Availability requirements and performances

In the OLA it was agreed the following performances targets, on a monthly basis:

  • Availability: 99%
  • Reliability 99%
 Other availability 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)

The service availability is regularly tested by nagios probe org.activemq.OpenWireSSL: https://argo-mon.egi.eu/nagios/cgi-bin/status.cgi?servicegroup=SERVICE_egi.APELRepository&style=overview

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 Accounting Portal hadn't particular Av/Co issues highlighted by the performances that need to be further investigated.

Risks assessment and management

(to review)

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 Low
2 Service unavailable / loss of data due to software failure Low
3 service unavailable / loss of data due to human error Low
4 service unavailable for network failure (Network outage with causes external of the site) Low
5 Unavailability of key technical and support staff (holidays period, sickness, ...) Low
6 Major disruption in the data centre. Fire, flood or electric failure for example Low
7 Major security incident. The system is compromised by external attackers and needs to be reinstalled and restored. Low
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): risks 1-2-3-7 (re-installation, backup restoring), risk 5 (general documentation and procedures)

- 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 week?
-- 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)): 5 days?
-- Recovery point objective (RPO) (the acceptable latency of data that will not be recovered): n.a. (data can be republished)

- approach for the return to normal working conditions as reported in the risk assessment.

Availability and Continuity test

Revision History

Version Authors Date Comments

Alessandro Paolini 2019-08-21 first draft, discussing with the provider