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 "CVMFS Stratum-0 Availability and Continuity Plan"

From EGIWiki
Jump to navigation Jump to search
(Created page with "{{Template:Op menubar}} {{Template:Doc_menubar}} {{TOC_right}} Category:Operations Back to main page: Services Availability Continuity Plans = Introduction = This p...")
 
 
(22 intermediate revisions by 2 users not shown)
Line 5: Line 5:
= Introduction =
= Introduction =


This page reports on the Availability and Continuity Plan for the '''Service or Component name''' 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.
This page reports on the Availability and Continuity Plan for the '''CVMFS Stratum-0''' 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.


{| class="wikitable"
{| class="wikitable"
Line 14: Line 14:
|-
|-
! scope="row"| Risks assessment
! scope="row"| Risks assessment
|  
| 2021-12
|  
| 2022-12
|-
|-
! scope="row"| Av/Co plan and test
! scope="row"| Av/Co plan
|  
| 2021-12
|  
| 2022-12
|-
|-
|}
|}




previous plans are collected here: <p style="color: blue>link to document db</p>
previous plans are collected here: https://documents.egi.eu/document/3849


= Hardware HA Configuration =
= Availability requirements and performances =
<p style="color: blue>From OLA</p>


= Availability requirements and performances =
* CernVM-FS is a file system with a single source of data. This single source, the repository Stratum-0, is maintained on a dedicated release manager machine or CVMFS Uploader.
<pre style="color: blue">
* The CVMFS Uploader is hosted by a server that offers read-write access to the repository maintainers via a GSI interface.
''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:
In the OLA it was agreed the following performances targets, on a monthly basis:
*Availability:  
*Availability: 95%
*Reliability:
*Reliability: 97%


''Other availability requirements:
The service availability is regularly tested by nagios probes org.nagiosexchange.CVMFS-WebCheck: https://argo-mon.egi.eu/nagios/cgi-bin/status.cgi?servicegroup=SITE_GRIDOPS-CVMFS_ch.cern.cvmfs.stratum.0&style=overview
* 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''


''The service availability is regularly tested by nagios probes (X and Y: link to ARGO/nagios)
The performances reports in terms of Availability and Reliability are produced by [https://argo.egi.eu/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 EGI Content Distribution / CVMFS Startum-0 hadn't particular Av/Co issues highlighted by the performances that need to be further investigated.


Over the past years, the SERVICE NAME hadn't particular Av/Co issues highlighted by the performances that need to be further investigated.''
</pre>
= Risks assessment and management =
= Risks assessment and management =
For more details, please look at the (google spreadsheet link). We will report here a summary of the assessment.
For more details, please look at the [https://docs.google.com/spreadsheets/d/1-BQpLBGrleaC16ERPaDPETVl8ZLBlf1zobCm8kgerMk/edit#gid=302183497 google spreadsheet]. We will report here a summary of the assessment.


== Risks analysis ==
== Risks analysis ==
Line 65: Line 57:
| 1
| 1
| Service unavailable / loss of data due to hardware failure
| Service unavailable / loss of data due to hardware failure
|  
| Stratum-0
|  
| Given the architecture of the service, end users are not impacted, as they don't get the data from the CVMFS Stratum-0 but from the replicas (Stratum-1s).
| style="background: green"| Low  
| style="background: green"| Low  
|
| 1 or more working days, depending on repare or replacement of hardware.
| 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
|-
|-
| 2
| 2
| Service unavailable / loss of data due to software failure
| Service unavailable / loss of data due to software failure
|  
| Stratum-0
|  
| Given the architecture of the service, end users are not impacted, as they don't get the data from the CVMFS Stratum-0 but from the replicas (Stratum-1s).
| style="background: green"| Low  
| style="background: green"| Low  
|
| If data needs to be recovered, 1 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
|-
|-
| 3
| 3
| service unavailable / loss of data due to human error
| service unavailable / loss of data due to human error
|  
| Stratum-0
|  
| Reduce the impact: service configuration is in the Configuration Management System, making human error easy to roll back.
| style="background: green"| Low  
| style="background: green"| Low  
|
| If data needs to be recovered, 1 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
|-
|-
| 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)
|  
| Stratum-0
|  
| None
| style="background: green"| Low  
| style="background: green"| Low  
|
| The duration of the network outage.
| 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, ...)
| Unavailability of key technical and support staff (holidays period, sickness, ...)
|  
| Stratum-0
|  
| A cover person, capable of handling tickets and investigating problems, is assigned in the case
of short term absences. Service setup and troubleshooting recipes are documented.
| style="background: green"| Low  
| style="background: green"| Low  
|
| The length of the absence / declared downtime.
| 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
|  
| Stratum-0
|  
| Reduce the likelihood: The health of the data centre is proactivly managed by a team of experts. Reduce the impact: The CVMFS servers run on UPS, so should remain operational in the event of electrical failure. In the case of other, long lasting, data centre disruption, the failover would be engaged.
| style="background: green"| Low  
| style="background: green"| Low  
|
| Depends on the details of the incident.
| 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
|-
|-
| 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.
|  
| Stratum-0
|  
| Reduce the likelihood: Internal security audits of the CVMFS machines that (for example) ensure packages are up to date, only the necasary ports are open, vunerbalilty warnings are recieved, etc. Reduce the impact: Use of configuration management means reinstalling, restoring or deployment of a new instance of a CVMFS Stratum-0 host to a known state can be done quickly. Data can be recovered from backup.
| style="background: green"| Low  
| style="background: green"| Low  
|
| Depends on the details of the incident.
| 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.
|  
| Stratum-0
|  
| Reduce the likelihood: the web server is configured to listen to a non-standard port, 8000 instead of 443.
Reduce the impact: The number of requests over time are monitored so any abnormal increase in traffic or response time would be noticed.
| style="background: green"| Low  
| style="background: green"| Low  
|
| Depends on the details of the incident.
| 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 ==
<p style="color: blue>for example:</p>
 
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)
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).
*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):
*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)):
*Recovery point objective (RPO) (the acceptable latency of data that will not be recovered):
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 X shall be used to report any incident or service request
* The Tier-1 hosting the service has a protocol for disaster management. The administrators will follow the steps on that planning in case of risks occurrence.
* The Availability targets don't change in case the plan is invoked.
* Recovery requirements (outcomes of the Business Impact Analysis).
** 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): 1 day
* Approach for the return to normal working conditions as reported in the risk assessment.
* The support unit Software and Data Distribution (CVMFS) 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.


The providers can contact EGI Operations via ticket or email in case the continuity plan is invoked, or to discuss any change to it.
</pre>
= 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. Typically this covers the risks 1,2, and 7.
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.</pre>
Considering the outcome of the Business Impact Analysis and of the Risk Assessment, there is no need of an A&C test: the service can be restored within the expected timeline in case of disruptions.
 
 
== Test details ==
 
== Test outcome ==


= Revision History  =
= Revision History  =
Line 170: Line 151:
! Comments
! Comments
|-
|-
|
| <br>
|  
| Renato Santana
|  
| 2021-10-28
|  
| first draft
|-
| <br>
| Renato Santana
| 2021-12-01
| risk analysis edition
|-
|-
|
| <br>
|  
| Alessandro Paolini
|  
| 2021-12-03
|  
| plan finalised, no need of A/C test
|}
|}

Latest revision as of 10:31, 3 December 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 CVMFS Stratum-0 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-12 2022-12
Av/Co plan 2021-12 2022-12


previous plans are collected here: https://documents.egi.eu/document/3849

Availability requirements and performances

  • CernVM-FS is a file system with a single source of data. This single source, the repository Stratum-0, is maintained on a dedicated release manager machine or CVMFS Uploader.
  • The CVMFS Uploader is hosted by a server that offers read-write access to the repository maintainers via a GSI interface.

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

  • Availability: 95%
  • Reliability: 97%

The service availability is regularly tested by nagios probes org.nagiosexchange.CVMFS-WebCheck: https://argo-mon.egi.eu/nagios/cgi-bin/status.cgi?servicegroup=SITE_GRIDOPS-CVMFS_ch.cern.cvmfs.stratum.0&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 EGI Content Distribution / CVMFS Startum-0 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 Stratum-0 Given the architecture of the service, end users are not impacted, as they don't get the data from the CVMFS Stratum-0 but from the replicas (Stratum-1s). Low 1 or more working days, depending on repare or replacement of hardware. the measures already in place are considered satisfactory and risk level is acceptable
2 Service unavailable / loss of data due to software failure Stratum-0 Given the architecture of the service, end users are not impacted, as they don't get the data from the CVMFS Stratum-0 but from the replicas (Stratum-1s). Low If data needs to be recovered, 1 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 Stratum-0 Reduce the impact: service configuration is in the Configuration Management System, making human error easy to roll back. Low If data needs to be recovered, 1 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) Stratum-0 None Low The duration of the network outage. the measures already in place are considered satisfactory and risk level is acceptable
5 Unavailability of key technical and support staff (holidays period, sickness, ...) Stratum-0 A cover person, capable of handling tickets and investigating problems, is assigned in the case

of short term absences. Service setup and troubleshooting recipes are documented.

Low The length of the absence / declared downtime. 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 Stratum-0 Reduce the likelihood: The health of the data centre is proactivly managed by a team of experts. Reduce the impact: The CVMFS servers run on UPS, so should remain operational in the event of electrical failure. In the case of other, long lasting, data centre disruption, the failover would be engaged. Low Depends on the details of the incident. 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. Stratum-0 Reduce the likelihood: Internal security audits of the CVMFS machines that (for example) ensure packages are up to date, only the necasary ports are open, vunerbalilty warnings are recieved, etc. Reduce the impact: Use of configuration management means reinstalling, restoring or deployment of a new instance of a CVMFS Stratum-0 host to a known state can be done quickly. Data can be recovered from backup. Low Depends on the details of the incident. 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. Stratum-0 Reduce the likelihood: the web server is configured to listen to a non-standard port, 8000 instead of 443.

Reduce the impact: The number of requests over time are monitored so any abnormal increase in traffic or response time would be noticed.

Low Depends on the details of the incident. 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

  • The Tier-1 hosting the service has a protocol for disaster management. The administrators will follow the steps on that planning in case of risks occurrence.
  • The Availability targets don't change in case the plan is invoked.
  • Recovery requirements (outcomes of the Business Impact Analysis).
    • 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): 1 day
  • Approach for the return to normal working conditions as reported in the risk assessment.
  • The support unit Software and Data Distribution (CVMFS) 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

Considering the outcome of the Business Impact Analysis and of the Risk Assessment, there is no need of an A&C test: the service can be restored within the expected timeline in case of disruptions.

Revision History

Version Authors Date Comments

Renato Santana 2021-10-28 first draft

Renato Santana 2021-12-01 risk analysis edition

Alessandro Paolini 2021-12-03 plan finalised, no need of A/C test