Difference between revisions of "PROC13 VO Deregistration"
Line 134: | Line 134: | ||
== VO Deregistration procedure == | == VO Deregistration procedure == | ||
This procedure is performed only if the request is | This procedure is performed only if the request is accepted. | ||
<br> | <br> | ||
Line 145: | Line 145: | ||
|- valign="top" | |- valign="top" | ||
| 1 | | 1 | ||
| | | | ||
VM | |||
| | (alternatively VS) | ||
| '''Open a GGUS ticket to begin the deregistration process '''(or answer to the ticket used for the request validation). <br>The ticket SHOULD contain the following information: <br> | |||
*The date of the decision of the VO decommissioning (prior to the begin of the procedure) | |||
**If available the link to the GGUS ticket that contains such decision | |||
*The proposed timeline for the decommission procedure: | |||
**Expected date for the VOMS support decommission | |||
**Expected date for the Helpdesk support unit decommission | |||
| | Ticket SHOULD be assigned to the "Operations" support unit in GGUS<br> | ||
|- valign="top" | |||
| 2 | |||
| | | | ||
VM | |||
(alternatively VS) | |||
| | | | ||
#'''Send a broadcast to all the VO users''', specifying: | #'''Send a broadcast to all the VO users''', specifying: | ||
#*A link to the master GGUS ticket opened at point 1 | #*A link to the master GGUS ticket opened at point 1 | ||
#*The timeline for the deregistration (minimum one month from the broadcast) | #*The timeline for the deregistration (minimum one month from the broadcast) | ||
#*The VOMS support is being stopped in one month (minimum), after end of support users will not be able to request a proxy to access the grid services | #*The VOMS support is being stopped in '''one month''' (minimum), after end of support users will not be able to request a proxy to access the grid services | ||
#*VO Users may ask for an extension of he deregistration timeline within '''one month'''. The request SHOULD be supported by technical reasons (e.g. the amount of data stored in the SEs is too big to be moved within the end of the procedure. | |||
#If there are other VOs accessing the VO data (and only if VO Manager provides this information): | #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 VO Manager to retrieve the relevant data | #*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 | ||
|- | |- | ||
| | | 3 | ||
| | | | ||
VM | |||
(alternatively VS) | |||
| '''After 2 weeks resend broadcast to the VO users ''' <br> | |||
*If users did not ask for an extension, send a broadcast as a reminder (with the same information as in ''step 2'') | |||
| '''After | |||
*If users did not ask for an extension, send a broadcast as a reminder (with the same information as in ''step | |||
*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" | ||
| | | 4 | ||
| | | | ||
| ''' | VM | ||
(alternatively VS) | |||
| '''After one month period (or longer period, if extended) create a GGUS ticket and assigned to the RC hosting the VOMS server that supports the VO, in order to request to disable the VO. ''' | |||
Information about RC hosting VOMS server for VO can be obained from VO ID card in Operations Portal. | |||
|- valign="top" | |- valign="top" | ||
| | | 5 | ||
| | | | ||
| '''Open a GGUS ticket to " | VM | ||
<br> | |||
| | |||
'''Open a GGUS ticket to "Operations" requesting the status change of the VO to "SUSPENDED"''' | |||
*If this step is carried out directly by the VS there is no need for this step<br> | |||
|- valign="top" | |||
| 6 | |||
| VS | |||
| '''Change VO status to "Suspended"''' | |||
|- valign="top" | |- valign="top" | ||
| 7 | | 7 | ||
| | | | ||
| '''Broadcast to | VM | ||
(alternatively VS) | |||
| | |||
'''Broadcast to RC that the VO has been decommissioned''' | |||
Adding the following instructions/information: | |||
*The link to the GGUS master ticket | *The link to the GGUS master ticket | ||
*If the | *If the RC is supporting the VO, it could be disabled in the services' configuration | ||
*Logs have to be maintained as long as requested by the traceability policy | *Logs have to be maintained as long as requested by the traceability policy | ||
|- valign="top" | |- valign="top" | ||
| 8 | | 8 | ||
| | | | ||
VM | |||
(alternatively VS) | |||
| | |||
'''Broadcast to VO Users that the VO has been decommissioned''' | |||
Adding the following information: | |||
*The VO status will be set to "DELETED" in 2 weeks, after this operation members of the VO will not be able to access EGI resources through given VO e.g. storage, computing resources, virtual machines. | |||
*A link to the master ticket<br> | |||
|- valign="top" | |- valign="top" | ||
| 9 | | | ||
| | 9 | ||
| '''Open a ticket | |||
| | |||
VM | |||
(alternatively VS) | |||
| | |||
'''Open a GGUS ticket to "GGUS" support unit requesting the decommissioning of the VO support unit''' | |||
''if this support unit is available''<br> | |||
|- valign="top" | |- valign="top" | ||
| 10 | | 10 | ||
| | | | ||
| '''Open a GGUS ticket to " | VM | ||
(alternatively VS) | |||
| | |||
'''Open a GGUS ticket to "Operations" Support unit requesting the status change of the VO to "DELETED"''' | |||
*If this step is carried out directly by the VS there is no need for this step | |||
|- valign="top" | |||
| 11 | |||
| VS | |||
| '''Change VO status to "DELETED"''' | |||
|- valign="top" | |- valign="top" | ||
| | | 12 | ||
| | | | ||
| '''Close the | VM | ||
(alternatively VS) | |||
| '''Close the main ticket''' <br> | |||
*This step concludes the deregistration procedure | *This step concludes the deregistration procedure | ||
Line 246: | Line 290: | ||
| | | | ||
| | | | ||
#VO Manager and VO users | #VO Manager and VO users MUST manage their tools (such as mailing lists, monitoring tools, portals) separately, and they are out of the scope of this procedure | ||
#If the VO provides tools for the users access to the grid resources (for example science portals or user interfaces), logs | #If the VO provides tools for the users access to the grid resources (for example science portals or user interfaces), logs MUST be retained as requested by the [https://documents.egi.eu/document/81 "Grid Security Traceability and Logging Policy"] | ||
|} | |} |
Revision as of 15:54, 27 August 2014
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 accepted.
# | Responsible | Action |
---|---|---|
1 |
VM (alternatively VS) |
Open a GGUS ticket to begin the deregistration process (or answer to the ticket used for the request validation). The ticket SHOULD contain the following information:
|
2 |
VM (alternatively VS) |
|
3 |
VM (alternatively VS) |
After 2 weeks resend broadcast to the VO users
|
4 |
VM (alternatively VS) |
After one month period (or longer period, if extended) create a GGUS ticket and assigned to the RC hosting the VOMS server that supports the VO, in order to request to disable the VO.
Information about RC hosting VOMS server for VO can be obained from VO ID card in Operations Portal. |
5 |
VM
|
Open a GGUS ticket to "Operations" requesting the status change of the VO to "SUSPENDED"
|
6 | VS | Change VO status to "Suspended" |
7 |
VM (alternatively VS) |
Broadcast to RC that the VO has been decommissioned Adding the following instructions/information:
|
8 |
VM (alternatively VS) |
Broadcast to VO Users that the VO has been decommissioned Adding the following information:
|
9
|
VM (alternatively VS) |
Open a GGUS ticket to "GGUS" support unit requesting the decommissioning of the VO support unit
if this support unit is available |
10 |
VM (alternatively VS) |
Open a GGUS ticket to "Operations" Support unit requesting the status change of the VO to "DELETED"
|
11 | VS | Change VO status to "DELETED" |
12 |
VM (alternatively VS) |
Close the main 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 |