RUCIO Availability and Continuity Plan

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 RUCIO and it is the result of the risks assessment conducted for this service: a series of risks and treats has been identified and analyzed, 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-11	2022-11
Av/Co plan and test

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

Hardware HA Configuration

• Rucio Servers behind an HA Proxy Service,
• Multiple Rucio Auth and Daemon nodes
• A test infrastructure to verify interoperability and the impact of software upgrades on depending systems

Availability requirements and performances

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

• Availability: 98%
• Reliability: 98%

Other availability requirements:

• the service is accessible through X509 certificate (the integration with EGI Check-in and IRIS IAM is ongoing).
• The service is accessible via CLI; the work to provide a webUI for the Rucio multi-VO instances is proceeding.

Look at monitoring history, in case of particular issues

The service availability is regularly tested by nagios probes ch.cern.rucio-WebCheck and eu.egi.CertValidity: https://argo-mon.egi.eu/nagios/cgi-bin/status.cgi?servicegroup=SERVICE_ch.cern.rucio&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 Data Management Service Rucio 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	All components, UI, Auth servers, database and webUI	Reduce Impact: Rucio DB is backed up daily to an off-site repository and can be easily recovered and restored if failures take place. Reduce Impact: The Service is also run in a containerized environment and when components are unavailable, will be rebooted.	Low	0.5 days	the measures already in place are considered satisfactory and risk level is acceptable
2	Service unavailable / loss of data due to software failure	All components, UI, Auth servers, database and webUI	Reduce Impact: The software being run in containers allows for quick redeployment of the containerized software. Reduce Impact: Rucio DB is backed up daily to an off-site repository and can be easily recovered and restored if failures take place.	Low	0.5 days	the measures already in place are considered satisfactory and risk level is acceptable
3	service unavailable / loss of data due to human error	All components, UI, Auth servers, database and webUI	Preventive: Access to production systems is limited, documentation regarding the system is stored internally. System management training is required for those running the system. Reduce impact: Have a test instance to run changes on before moving those changes to production. Aditionally backups and snapshots should be taken before changes and after successful changes.	Low	0.5 days	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)	All components, UI, Auth servers, database and webUI	Preventative: Load Balancers are in a highly available pair on separate VMWare hypervisors. Site has redundant external network links with geographically different paths. Reduce the impact: Load Balancers are under configuration management, making some errors easier to roll back.	Low	1 day	the measures already in place are considered satisfactory and risk level is acceptable
5	Unavailability of key technical and support staff (holidays period, sickness, ...)	All components, UI, Auth servers, database and webUI	Preventative: GOCDB technical / support staff try not to be on leave at the same time for a prolonged period. A cover person, capable of handling tickets and investigating minor problems, is assigned in the case of short term absences or an 'At Risk' is declared.	Low	1 day	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	All components, UI, Auth servers, database and webUI	Preventative: Follow normal site and machine room emergency procedures Reduce Impact: Once it is safe to do so, make hardware secure as soon as possible Reduce Impact: Make preliminary assessment, estimate when safe to (partially) restart, Reduce Impact: Notify affected parties with indication of problem (& scale) Reduce Impact: If situation allows, restart nationally and globally critical systems	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.	All components, UI, Auth servers, database and webUI	Preventative: The majority of the Rucio components are not publicly available. Reduce the impact: Rucio's components are hosted on the STFC openstack cloud system, and run in containers, and can therefore quickly be redeployed once the cloud system is back online if it was effected. Very little personal information is stored on the Rucio DB, therefore there is not valuable personal data at risk. The data within the Rucio DB points to where data is, not stores it, therefore experimental data is not likely to be lost as it is stored in a different location.	Low	1 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.	All components, UI, Auth servers, database and webUI	Preventative: Running Fail2Ban on all the publicly facing servers which tracks attempted access	Low	1 day or more	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 (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): 4 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)): 3 days
• Recovery point objective (RPO) (the acceptable latency of data that will not be recovered): 3 days
• Approach for the return to normal working conditions as reported in the risk assessment.
• The support unit Rucio 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 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.

Revision History

Version	Authors	Date	Comments
	Renato Santana	2021-10-28	first draft
	Renato Santana	2021-12-01	risk analysis entered
	Alessandro Paolini	2021-12-07	filling in other information. Agreed with the provider that a recovery test will be done.