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 |
Document link | https://wiki.egi.eu/wiki/PROC13 |
Last modified | 1.0 - 19 August 2014 |
Policy Group Acronym | OMB |
Policy Group Name | Operations Management Board |
Contact Group | operations-support@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
The document describes the process of permanent deregistration of Virtual Organisation (VO) from the European Grid Infrastructure (EGI).
The focus of this document is on the tasks that VO representatives and the EGI staff have to accomplish in order to deregister given VO. The purpose of this page is to capture the VO deregistration workflow.
As a result of this procedure members of the VO will not be able to access EGI resources through given VO e.g. storage, computing resources, virtual machines.
This procedure applies to VOs which reached PRODUCTION status as a result of PROC14 VO Registration.
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.
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:
- VO manager (VM): person who is responsible for initiating the registration process.
- VO supervisor (VS): person delegated from the EGI Operation team to handle the process on behalf of EGI project and is responsible for the approval of VO registration requests.
- VO users (VU): members of VO
- Resource Centres (RC): The resource centres supporting the VO resources.
- NGI Operations Manager: person in charge of National Infrastructure
The tools available to support the deregistration procedure are:
Steps
Request validation
The following entities can submit a deregistration request for a VO through a GGUS ticket:
- VO Manager (VM)
- VO Supervisor (VS)
- VO User (VU)
- NGI Operations Manager
# | Responsible | Action |
---|---|---|
1 | Requester |
Submit a GGUS ticket, specify in body of the ticket: "Please assign to the Operations Support Unit", including the deregistration request. The ticket must contain the following information:
|
2 | VS |
|
3 | VS |
Assess the VO activities during the last 12 months. To accept the request the requirements are:
|
4 | VS | Notify the VO Manager about the pending request of VO decommission:
|
5 | VM | VO Manager should discuss the VO deregistration request within the community and provide a feedback n the GGUS ticket or via email, within the deadline.
|
6 | VS | Record in the GGUS ticket the decision to approve or reject the request
|
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 |
M. Krakowian | 19 August 2014 | Change contact group -> Operations support |