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

From EGIWiki
Jump to: navigation, search
Main 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
Last modified 0.1 - 8 June 2016
Policy Group Acronym OMB
Policy Group Name Operations Management Board
Contact Group
Document Status Approved
Approved Date 29 January 2015
Procedure Statement The document describes the process of enabling the replication of CVMFS spaces across OSG and EGI CVMFS infrastructures
Owner Baptiste Grenier


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.

This procedure defines the steps for the replication of a VO space from OSG to EGI.


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


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, if the VOR is not the VO Manager, the VO Manager should be notified by involving him in the ticket.

The ticket must specify the name of the repository hosted by the OSG CVMFS infrastructure that the VO wants to be replicated in EGI.

The VO must be supported by more than one site in EGI, the sites should already support CVMFS in production.

- ticket assigned to Operations

2 Operations Validate the request
The EGI Operations team will verify that the request satisfy the prerequisites:
  • VO is in production
  • VO Manager has been correctly involved in the ticket
  • VO is supported by more than one EGI production Resource Centres

The outcome of the validation must be reported in the ticket opened in Step#1. If the request is valid the GGUS ticket must be assigned to CVMFS

3 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.

If the contact is done by email, EGIM must record in the ticket opened on Step 1 that the emails have been sent (and to which sites they have been sent), and also record that sites replied.

4 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.


This is an additional step, to be applied only when needed.

If the sites supporting the VO have not been configured with standard cvmfs installations that support automounting all repositories (i.e. cvmfs-2.1.19 with cvmfs-keys-1.5, or later cvmfs release) then they may not be able to access the new repository. The VO should test the sites and submit GGUS tickets for those that cannot access the repository.

Revision history

Version Authors Date Comments
1.0 Peter Solagna, Catalin Condurache, Dave Dykstra 24 Sep 2015
Alessandro Paolini 2016-06-08 "EGI Operations Support" was decommissioned, changed all the references to "Operations"
Alessandro Paolini 2017-05-04 in step 2, changed the mailing list with the GGUS SU CVMFS, since it handles these kind of requests
Personal tools