PROC20 Support for CVMFS replication across the EGI and OSG CVMFS services

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

Title	Support for CVMFS replication across the EGI and OSG CVMFS services
Document link	https://wiki.egi.eu/wiki/PROC20
Last modified	0.1 - 13 November 2014
Policy Group Acronym	OMB
Policy Group Name	Operations Management Board
Contact Group	operations-support@mailman.egi.eu
Document Status	Draft
Approved Date	-
Procedure Statement	The document describes the process of enabling the replication of CVMFS spaces across OSG and EGI CVMFS infrastructures
Owner	Owner of procedure

Overview

The document describes the process of enabling the replication of CVMFS spaces across OSG and EGI CVMFS infrastructures. The aim of this procedure is to ensure that the CVMFS replication addresses real use cases and that the VO managing the CVMFS area is supported by resource centres both in OSG and EGI.

Definitions

Please refer to the EGI Glossary for the definitions of the terms used in this procedure.

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", “MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.

Entities involved in the procedure

• VO representative (VOR): person who is responsible for initiating the replication process.
• OSG CVMFS Manager (OSGM): person or team who is responsible for the operations of the CVMFS services for the OSG infrastructure
• EGI CVMFS Manager (EGIM): person or team who is responsible for the operations of the CVMFS services for the EGI infrastructure

Requirements

VO can ask to replicate the CVMFS areas used in one of the two infrastructures if they have sites supporting the VO in both EGI and OSG. The sites should already support CVMFS.

Steps

• Actions tagged VOR are the responsibility of the VO Representative.
• Actions tagged OSGM are the responsibility of the OSG CVMFS Manager.
• Actions tagged EGIM are the responsibility of the EGI CVMFS Manager.

	Responsible	Action	Prerequisites, if any
1	VOR	Submit CVMFS replication request The VOR opens a GGUS ticket specifying the name of the VO in EGI, and	The VO must be supported by more than one site in EGI, the sites should already support CVMFS in production.
2	EGIM	Validate the request The EGIM must validate the request, with the support of EGI Operations Support checking that the VO is supported in the EGI infrastructure. The result of the validation is reported in an answer to the ticket.
3	EGIM	Contact the OSGM to confirm the replication in the EGI Stratum0 EGIM to open a ticket in the OSG ticketing system to confirm the OSG support for the replica and exchange the technical details. <please specify the best communication channel for this>. A link to the opened ticket should be reported int he ticket opened in step #1
4	OSGM	Confirm the OSG support for the replica to EGI OSGM confirms (or rejects) the support for the replica providing the technical details.
5	EGIM	Enable the replica in the EGI Stratum0
6	EGIM	Open a ticket for every Stratum1 who should import the new VO space The EGIM opens a GGUS ticket to the EGI sites hosting a CVMFS Stratum-1 that should import the file system from the new VO.
7	EGIM	Confirm the availability of the VO file system in the CVMFS infrastructure The EGIM checks the correctness of the replica from OSG and the distribution of the files to the Stratum-1. Once the VO files are available in the Stratum-1, the EGIM reports the successful conclusion of the procedure and closes the ticket opened in Step#1. The procedure concludes here.
8	VOR	This is an additional step, needed but not part of the procedure. Open a GGUS ticket for every site supporting the VO asking to import the VO CVMFS space The VO Manager should open a GGUS ticket for every EGI site supporting the VO, asking to enable the CVMFS support for the VO in the execution environment.