Difference between revisions of "PROC22"
(→Steps) |
(→Steps) |
||
Line 40: | Line 40: | ||
! Responsible | ! Responsible | ||
! Action | ! Action | ||
! | ! Notes | ||
|- valign="top" | |- valign="top" | ||
| 1 | | 1 |
Revision as of 18:39, 3 November 2015
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 | ' |
Document link | |
Last modified | |
Policy Group Acronym | OMB |
Policy Group Name | Operations Management Board |
Contact Group | operations at mailman.egi.eu |
Document Status | |
Approved Date | |
Procedure Statement | |
Owner | Owner of procedure |
Overview
The document describes the process of creating a repository within the EGI CVMFS infrastructure for an EGI VO.
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
- XX: person who...
- XXX:
Requirements
Steps
Responsible | Action | Notes | ||
---|---|---|---|---|
1 | VO manager (or VO SGM) | create the request via GGUS ticket, specifying the name of the VO in EGI to be supported within the CVMFS infrastructure. | The ticket should contain information about the initial size of the repository and, if possible, an expected growth rate.
For an initial size of 50GB+, the VO SGM might be asked for further details regarding the proposed structure of the repository. Also the ticket must include the DNs (Distinguished Names) of VO users responsible for maintaining the repository in the future (all these VO users will be referred as VO SGM in this document). A VOMS Role could be provided alternatively. |
Revision History
Version | Authors | Date | Comments |
---|---|---|---|