Difference between revisions of "PROC13 VO Deregistration"
Line 217: | Line 217: | ||
#* The timeline for the deregistration (minimum one month from the broadcast) | #* The timeline for the deregistration (minimum one month from the broadcast) | ||
#* The VOMS server is being decommissioned in one month (minimum), after the decommission users will not be able to request a proxy to access the grid services | #* The VOMS server is being decommissioned in one month (minimum), after the decommission users will not be able to request a proxy to access the grid services | ||
# If there are other VOs accessing the VO data (and only if | # If there are other VOs accessing the VO data (and only if VO Manager provides this information): | ||
#* Send a broadcast to the VO Managers of the affected VOs containing the same set of information, asking them to directly coordinate with the | #* Send a broadcast to the VO Managers of the affected VOs containing the same set of information, asking them to directly coordinate with the VO Manager to retrieve the relevant data | ||
|- valign="top" | |- valign="top" | ||
Line 232: | Line 232: | ||
| | | | ||
#After 15 days of the previous broadcast, send another broadcast to the VO users | #After 15 days of the previous broadcast, send another broadcast to the VO users | ||
#*If users '''did not ask''' for an extension, send a broadcast as a reminder (with the same information as in ''step 3'' | #*If users '''did not ask''' for an extension, send a broadcast as a reminder (with the same information as in ''step 3'') | ||
#*If users '''asked''' for an extension, send a broadcast with the new timeline | #*If users '''asked''' for an extension, send a broadcast with the new timeline | ||
|- valign="top" | |- valign="top" | ||
Line 270: | Line 270: | ||
| VOM (alternatively VOS) | | VOM (alternatively VOS) | ||
| | | | ||
# Open a ticket vs the "GGUS" support unit in the EGI | # Open a ticket vs the "GGUS" support unit in the EGI Helpdesk system, requesting the decommissioning of the VO support unit, if this support unit is available. This ticket must be a child ticket of the master ticket | ||
#* The decommissionin of a VO support unit differs from a regular support unit in GGUS, and the technical actions have not been yet defined by the GGUS team. | #* The decommissionin of a VO support unit differs from a regular support unit in GGUS, and the technical actions have not been yet defined by the GGUS team. | ||
|- valign="top" | |- valign="top" |
Revision as of 09:17, 3 August 2012
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 | 1.0 - 16 July 2012 |
Policy Group Acronym | OMB |
Policy Group Name | Operations Management Board |
Contact Person | operations@mailman.egi.eu |
Document Status | Approved by OMB |
Approved Date | 17 July 2012 |
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] with the European Grid Infrastructure to get access to resources supplied by the participating resource centres. 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 contains a procedure to permanently deregister a VO from the European Grid Infrastructure.
The current document is intended for 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 in case they are 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.
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 (VOM).
- The VO Supervisor (VOS). For unresponsive VOs, the VOS drives the deregistration process Important: for regional VOs with unresponsive VOM, the OC staff should act as
- The resource centres supporting the VO resources.
- The VO users (VOU).
The tools available to support the deregistration procedure are:
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
- 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
VO Supervisor (COO)
- Manage the VO statuses
- Overview the VO decommissioning procedure if the VO Manager is not responsive, performing the main steps
VO manager
- Carry out the procedure steps
- 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
VO Users
- Promptly report to VO Manager any request to modify the VO decommissioning timeline
Workflow
The VO deregistration workflow is composed by two processes:
- The validation of the deregistration request
- The actual deregistration
The second part is performed only if the deregistration request is accepted, if the request is rejected te VO status is not modified by this procedure.
- Actions tagged VOM are the responsibility of the VO Manager of the VO being decommissioned.
- Actions tagged VOS are the responsibility of the VO Supervisor (Currently COO). For regional team this role will be carried by the Operations Centre Team.
- Actions tagged VOU are the responsibility of the single VO users
Request validation
The following entities can submit a deregistration request for a VO through a GGUS ticket:
- VO Manager
- VO Supervisor
- VO User
- NGI Operations Manager
- Site Manager
A request submitted by the VO Manager does not require an assessment of the VO usage. Steps from 3 and beyond must be performed only if the requester is not the VO Manager of the VO.
# | Responsible | Action |
---|---|---|
1 | Requester |
|
2 | VOS |
|
3 | VOS |
If the two conditions above are not satisfied the request is rejected, and the following steps can be skipped. |
4 | VOS |
|
5 | VOM | VO Manager should discuss the VO deregistration request within the community and provide a feedback
|
6 | VOS |
|
7 | VOM (alternatively the VOS) |
|
VO Deregistration procedure
This procedure is performed only if the request is validated.
# | Responsible | Action |
---|---|---|
1 | VOM (alternatively VOS) |
|
2 | VOM |
(Optional step)
VO Manager can retrieve these information by himself, or ask support to the LFC service administrator. If it is no possible to retrieve the information, or if VOM considers this step unnecessary, it can be skipped. |
3 | VOM (alternatively VOS) |
|
3bis | VOU |
|
4 | VOM |
|
5 | VOM (alternatively VOS) |
|
6 | VOM (alternatively VOS) |
|
7 | VOM (alternatively VOS) |
|
8 | VOM (alternatively VOS) |
|
9 | VOM (alternatively VOS) |
|
10 | VOM (alternatively VOS) |
|
11 | VOM (alternatively VOS) |
|
Additional notes |
|
Acknowledgements
The first version of this procedure has been edited by Goncalo Borges (LIP).