PROC13 VO Deregistration
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 | VO Deregistration Procedure |
Document link | [1] |
Version - last modified | 0.1 |
Policy Group Acronym | OMB |
Policy Group Name | Operations Management Board |
Contact Person | operations@mailman.egi.eu |
Document Status | DRAFT |
Approved Date | N/A |
Procedure Statement | A procedure for the steps involved to decommission a Virtual Organization currently registered in the EGI infrastructure. |
VO Deregistration Procedure
A VO registers [R3] to the European Grid Infrastructure in the perspective to get access to resources supplied by the participating sites. The VO is bound by the appropriate operational and security policies [R4, R5, R6, R7] but those documents do not define how to handle situations like a VO wanting to leave the European Grid Infrastructure. This document proposes a procedure to permanently deregister a VO from the European Grid Infrastructure.
The current document is intended to the VO manager, who understands the needs of the VO users and is responsible to apply the registration and deregistration procedures, and to the VO supervisor, who coordinates the overall process and takes the VO manager role case he is unavailable, unresponsive or unable to commit to the defined procedure timelines. It is certainly also beneficial for site managers, as well as people involved in grid management aspects, especially in the fields of security and operations.
Note: a separate document will provide the guidelines to propose and agree a VO deregistration. This document contains the steps to be performed once the decision to decommission the VO is taken.
Definitions
- Resource Centre refers to the definition in the "Resource Centre OLA".
- In this document, the term "site" is deprecated, and Resource Centre has been used in its place.
- Other entities involved in this procedure are defined in the EGI Glossary.
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
The main players participating in the VO deregistration procedure are:
- The VO manager.
- The VO supervisor.
- The VO deregistration coordinator.
- The sites supporting the VO resources.
- The VO users.
The tools available to support the deregistration procedure are:
- The EGI Help-desk (GGUS) [R8].
- The Accounting Portal [R9].
- GSTAT [R10].
- The EGI Operations Portal [R1].
Contact information
- EGI Operations: operations (at) mailman.egi.eu
- EGI Resource Infrastructure Providers are listed on the EGI web site
- A list of EGI Operations Centres with their respective contact information is available from the GOCDB
- EGI CSIRT: egi-csirt-team (at) mailman.egi.eu
- The list of VO's served by a specific Resource Centre and their ID cards can be retrieved from the Operations Portal.
- The VO managers and their contact information for a specific VO can be retrieved from the Operations Portal.
Actions and responsibilities
Resource Centre Operations Manager
- A Resource Infrastructure Provider is responsible for all Resource Centres (RC's) within its respective jurisdiction (for example, an NGI is responsible for all Resource Centres in its country). For this reason, the Resource Centre Operations Manager of a Resource Centre is REQUIRED
- to contact the respective NGI if the Resource Centre is located in Europe,
- to contact the respective Resource Infrastructure Provider active in a relevant geographical area if the Resource Centre is outside Europe, about the intention of the Resource Centre to decommission operation.
- The Resource Centre Operations Manager is REQUIRED to provide the necessary Resource Centre information needed to complete the decommission process, and he/she is responsible for its accuracy and maintenance.
Resource Infrastructure Operations Manager
- A Resource Infrastructure Provider is REQUIRED to be responsible for all Resource Centres within its respective jurisdiction. For example, an NGI is responsible for all Resource Centres in its respective country.
- The Resource Infrastructure Operations Managers MUST attend Resource Centre decommissioning applications and MUST provide feedback to the requesting partners in a timely manner to accept or reject the requests received.
- The Resource Infrastructure Operations Manager MUST contact the relevant Operations Centre to start the Resource Centre decommissioning procedure.
VO's and VO managers
- give the users the relevant information about the decommissioning (deadlines, involved resources, files, how to handle it)
- follow-up and support users in their file migration procedures until the deadline
- inform Resource Centre about the status of the migration(s)
Operations Centre
- The Operations Centre is responsible for decommissioning Resource Centre.
- The Operations Centre is responsible for updating the corresponding entries in the EGI configuration repository GOCDB.
- The Operations Centre MUST keep Resource Centre information up to date and in all operations tools as needed, such as the local NAGIOS server for monitoring of certified Resource Centres, the local helpdesk (if available) for the registration of the Resource Centre support staff, etc.
Workflow
The various steps required by both the Resource Infrastructure Operations Manager and the Resource Centre Operations Manager are explained in the tables below. The procedure below covers the transition from the Certified to the Closed status. The transition from the Suspended to the Closed status can be derived analogously.
The general status flow that a Resource Centre is allowed to follow is illustrated by the following diagram. Information on Resource Centre status and on how to manipulate it is available from GOCDB Documentation.
A Resource Centre cannot be in Candidate state for more than two month, and Suspended state for longer than four months. After this period the Resource Centre SHOULD be closed.
Resource Centre decommissioning
Steps
- Actions tagged RC are the responsibility of the Resource Centre Operations Manager.
- Actions tagged RIP are the responsibility of the Resource Infrastructure Operations Manager.
- Actions tagged OC are the responsibility of the Operations Centre
# | Responsible | Action |
---|---|---|
1 | RC |
|
2 | RC |
|
3 | RC |
- except the monitoring jobs. |
3 bis | VO |
|
4 | RC |
|
5 | RIP |
|
6 | RIP |
If the Resource Centre has storage elements (SEs) :
|
7 | RIP |
|
8 | OC |
|
9 | RC |
|
10 | OC |
|
11 | OC |
|