Date: Thu, 28 Mar 2024 18:25:45 +0100 (CET) Message-ID: <90955090.217.1711646745649@czmuims01.ops.egi.eu> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_216_993461284.1711646745648" ------=_Part_216_993461284.1711646745648 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The following table is updated after every review of this procedure.
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 t= he 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 term= s used in this procedure.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHO= ULD", "SHOULD NOT", "RECOMMENDED", =E2=80=9CMAY", and "OPTIONAL" in this do= cument are to be interpreted as described in RFC 2119.
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 al= ready 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 V= OR is not the VO Manager, the VO Manager should be notified by involving hi= m in the ticket.=20 The ticket must specify the name of the repository hosted by the OSG CVM= FS infrastructure that the VO wants to be replicated in EGI. |
The VO must be supported by more than one site i=
n EGI, the sites should already support CVMFS in production.=20
- ticket assigned to Operations |
2 | Operations | Validate the request The EGI Operations team will verify that the request satisfy the prerequis= ites:=20
The outcome of the validation must be reported in the ticket opened in S=
tep#1. If the request is valid the GGUS ticket must be assigned to |
|
3 | EGIM | Open a ticket for every Stratum1 who sho=
uld import the new VO space The EGIM opens a GGUS ticket to the EGI sites hosting a CVMFS Stratum-1 th= at should import the file system from the new VO.=20 If the contact is done by email, EGIM must record in the ticket opened o= n 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 distributi= on of the files to the Stratum-1. Once the VO files are available in the St= ratum-1, the EGIM reports the successful conclusion of the procedure and cl= oses the ticket opened in Step#1. The procedure concludes here. |
|
5 | VOR |
This is an additional step, to be applied only when needed.= em>
|