Difference between revisions of "PROC13 VO Deregistration"
Line 94: | Line 94: | ||
| 1 | | 1 | ||
| Requester | | Requester | ||
| '''Submit a GGUS ticket''', | | '''Submit a GGUS ticket''', specify in body of the ticket: "Please assign to the VO Services Support Unit", including the deregistration request. The ticket must contain the following information: <br> | ||
*Role of requester (from the list above) | *Role of requester (from the list above) | ||
*Motivation of the request | *Motivation of the request |
Revision as of 08:22, 9 September 2013
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 |
Document link | https://wiki.egi.eu/wiki/PROC13 |
Last modified | 1.0 - 16 July 2012 |
Policy Group Acronym | OMB |
Policy Group Name | Operations Management Board |
Contact Group | 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. |
Owner | Owner of procedure |
Overview
A VO registers with the European Grid Infrastructure to get access to resources supplied by the participating resource centres. This document contains a procedure to permanently deregister a VO from the European Grid Infrastructure.
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
The main players participating in the VO deregistration procedure are:
- The VO Manager (VOM)
- The VO managers and their contact information for a specific VO can be retrieved from the Operations Portal.
- 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:
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 the 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
Steps
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.
# | Responsible | Action |
---|---|---|
1 | Requester | Submit a GGUS ticket, specify in body of the ticket: "Please assign to the VO Services Support Unit", including the deregistration request. The ticket must contain the following information:
|
2 | VOS |
|
Steps below must be performed only if the requester is not the VO Manager of the VO. | ||
3 | VOS | Assess the VO activities during the last 12 months. To accept the request the requirements are:
If the two conditions above are not satisfied the request is rejected, and the following steps can be skipped. |
4 | VOS | Notify the VO Manager about the pending request of VO decommission:
|
5 | VOM | VO Manager should discuss the VO deregistration request within the community and provide a feedback
|
6 | VOS | Record in the GGUS ticket the decision to approve or reject the request
|
7 | VOM (alternatively the VOS) | Start the VO Deregistration procedure |
VO Deregistration procedure
This procedure is performed only if the request is validated.
# | Responsible | Action |
---|---|---|
1 | VOM (alternatively VOS) |
|
2 (Optional step) |
VOM |
Provide a snapshot of the resources supporting the VO
VO Manager can retrieve these information by himself from GSTAT (gstat.egi.eu/gstat), 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 | Users may ask for an extension of the deregistration timeline
|
4 | VOM | After 15 days of the previous broadcast, send another broadcast to the VO users
|
5 | VOM (alternatively VOS) | At the end of the one month period (or longer period, if extended at point 3bis) a child ticket of the master ticket should be opened and assigned to the resource centre hosting the VOMS server that supports the VO, in order to request to disable the VO.
|
6 | VOM (alternatively VOS) | Open a GGUS ticket to "VO Services" requesting the status change of the VO to "suspended", the ticket must be a child ticket of the master ticket.
|
7 | VOM (alternatively VOS) | Broadcast to site managers that the VO has been decommissioned, adding the following instructions/information:
|
8 | VOM (alternatively VOS) | Broadcast to VO users that the VO has been decommissioned, adding the following information:
Link the broadcast text in the master ticket |
9 | VOM (alternatively VOS) | 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
|
10 | VOM (alternatively VOS) | Open a GGUS ticket to "VO Services" requesting the status change of the VO to "deleted", the ticket must be a child ticket of the master ticket.
|
11 | VOM (alternatively VOS) | Close the master ticket
|
Additional notes |
|
Revision history
Version | Authors | Date | Comments |
---|---|---|---|
1.0 | Goncalo Borges (LIP) | 16 July 2012 | First version of the procedure |