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
(22 intermediate revisions by 2 users not shown)
Line 14: Line 14:
|-
|-
! scope="row"| Risks assessment
! scope="row"| Risks assessment
|  
| 2019-06-16
|  
| 2021 Q2
|-
|-
! scope="row"| Av/Co plan and test
! scope="row"| Av/Co plan and test
|  
| 2020-04-21
|  
| 2021 Q2
|-
|-
|}
|}




<pre style="color: blue">(previous plans are collected here: https://documents.egi.eu/document/3007 https://rt.egi.eu/rt/Ticket/Display.html?id=12323)</pre>
Previous plans are collected here: https://documents.egi.eu/document/3007 https://rt.egi.eu/rt/Ticket/Display.html?id=12323
 
= Hardware HA Configuration =
<pre style="color: blue">(taken from OLA)</pre>


= Availability requirements and performances =
= Availability requirements and performances =
Line 35: Line 32:
*Reliability 99%
*Reliability 99%


<pre style="color: blue"> Other availability requirements:
Other availability requirements:
- the service is accessible through X509 certificate and/or other authentication system
- the service is accessible through X509 certificate and EGI Check-in (for the Poem service component)
- 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)


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


Over the past years, the Accounting Portal hadn't particular Av/Co issues highlighted by the performances that need to be further investigated.
Over the past years, ARGO hadn't particular Av/Co issues highlighted by the performances that need to be further investigated.


= Risks assessment and management =
= Risks assessment and management =
<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 [https://docs.google.com/spreadsheets/d/1yLsbKZJA6jT-j4ONPsnr-LmJpgaP-ARAwDzRpP9JnJM/edit#gid=331768652 google spreadsheet]. We will report here a summary of the assessment.


== Risks analysis ==
== Risks analysis ==
Line 66: Line 59:
| 1
| 1
| Service unavailable / loss of data due to hardware failure
| Service unavailable / loss of data due to hardware failure
|  
| ARGO Monitoring
|  
| Automated Deployment and Backup Procedures that allow for rapid redeployment of affected components
| style="background: green"| Low  
| style="background: green"| Low  
|  
| up to 8 hours
|
| the measures already in place are considered satisfactory and risk level is acceptable
|-
|-
| 2
| 2
| Service unavailable / loss of data due to software failure
| Service unavailable / loss of data due to software failure
|  
| ARGO Monitoring
|  
| Automated Deployment and Backup Procedures that allow for rapid redeployment of affected components
| style="background: green"| Low  
| style="background: green"| Low  
|  
| up to 8 hours
|  
| the measures already in place are considered satisfactory and risk level is acceptable
|-
|-
| 3
| 3
| service unavailable / loss of data due to human error
| service unavailable / loss of data due to human error
|  
| ARGO Monitoring
|  
| Automated Deployment and Backup Procedures that allow for rapid redeployment of affected components
| style="background: green"| Low  
| style="background: green"| Low  
|  
| up to 8 hours
|  
| the measures already in place are considered satisfactory and risk level is acceptable
|-
|-
| 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
| ARGO Monitoring
| 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.
| Automated Deployment and Backup Procedures that allow for rapid redeployment of affected components
| style="background: green"| Low  
| style="background: green"| Low  
| up to 4 hours (half working day)
| up to 8 hours
| 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
|-
|-
| 5
| 5
| Unavailability of key technical and support staff (holidays period, sickness, ...)
| Not enough people for maintaining and operating the service
| Any
| ARGO Monitoring
| 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.
| There is always one member of the team on call.  
| style="background: green"| Low  
| style="background: green"| Low  
| 1 or more working days
| up to 8 hours
| 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
|-
|-
| 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
| ARGO Monitoring
| Fire suppression systems and generator backed UPS
| Automated Deployment and Backup Procedures that allow for rapid redeployment of affected components
| style="background: green"| Low
| style="background: yellow"| Medium
| 1 or more working days
| 1 or more working days
| 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 114: Line 107:
| 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.
|  
| ARGO Monitoring
| Daily backup are executed. Backup is stored in a separate system and can be restored in another system
| Automated Deployment and Backup Procedures that allow for rapid redeployment of affected components
| style="background: green"| Low  
| style="background: green"| Low  
| up to 8 hours (1 working day)
| 1 or more working days
| 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
|-
|-
| 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
| ARGO Monitoring
| Authentication and authorisation required to send messages via the brokers and messages are additionally checked when received at the Repository
| Automated Deployment and Backup Procedures that allow for rapid redeployment of affected components
| style="background: green"| Low  
| style="background: green"| Low
| up to 8 hours (1 working day)
| up to 8 hours
| 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
|}
|}


== Outcome ==
== Outcome ==
 
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">
* An internal recover procedure is available to the staff
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:
- the Availability targets don't change in case the plan is invoked.
** 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 days
- recovery requirements:
** Recovery point objective (RPO) (the acceptable latency of data that will not be recovered): 2 days
-- 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?
* approach for the return to normal working conditions as reported in the risk assessment
-- 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.
</pre>


= Availability and Continuity test =
= Availability and Continuity test =
 
During the last major upgrade the providers did a recovery test for monitoring, poem, analytics engine, UI and everything went smoothly. During this process they also updated their ansible scripts and the corresponding Installation Guides.


= Revision History  =
= Revision History  =
Line 164: Line 151:
| first draft, discussing with the provider
| first draft, discussing with the provider
|-
|-
|
| <br>
|  
| Alessandro Paolini
|  
| 2019-09-16
|  
| risk assessment info added in the wiki
|-
| <br>
| Alessandro Paolini
| 2020-04-21
| added information about the recovery test; A&C plan finalised
|-
|-
|
|

Revision as of 15:59, 21 April 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

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 2019-06-16 2021 Q2
Av/Co plan and test 2020-04-21 2021 Q2


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

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 EGI Check-in (for the Poem service component) - The service is accessible via webUI

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

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, ARGO 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 ARGO Monitoring Automated Deployment and Backup Procedures that allow for rapid redeployment of affected components Low up to 8 hours the measures already in place are considered satisfactory and risk level is acceptable
2 Service unavailable / loss of data due to software failure ARGO Monitoring Automated Deployment and Backup Procedures that allow for rapid redeployment of affected components Low up to 8 hours the measures already in place are considered satisfactory and risk level is acceptable
3 service unavailable / loss of data due to human error ARGO Monitoring Automated Deployment and Backup Procedures that allow for rapid redeployment of affected components Low up to 8 hours 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) ARGO Monitoring Automated Deployment and Backup Procedures that allow for rapid redeployment of affected components Low up to 8 hours the measures already in place are considered satisfactory and risk level is acceptable
5 Not enough people for maintaining and operating the service ARGO Monitoring There is always one member of the team on call. Low up to 8 hours the measures already in place are considered satisfactory and risk level is acceptable
6 Major disruption in the data centre. Fire, flood or electric failure for example ARGO Monitoring Automated Deployment and Backup Procedures that allow for rapid redeployment of affected components Medium 1 or more working days 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. ARGO Monitoring Automated Deployment and Backup Procedures that allow for rapid redeployment of affected components Low 1 or more working days 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. ARGO Monitoring Automated Deployment and Backup Procedures that allow for rapid redeployment of affected components Low up to 8 hours 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

  • An internal recover procedure is available to the staff
  • 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 days
    • Recovery point objective (RPO) (the acceptable latency of data that will not be recovered): 2 days
  • approach for the return to normal working conditions as reported in the risk assessment

Availability and Continuity test

During the last major upgrade the providers did a recovery test for monitoring, poem, analytics engine, UI and everything went smoothly. During this process they also updated their ansible scripts and the corresponding Installation Guides.

Revision History

Version Authors Date Comments

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

Alessandro Paolini 2019-09-16 risk assessment info added in the wiki

Alessandro Paolini 2020-04-21 added information about the recovery test; A&C plan finalised