Difference between revisions of "PROC13 VO Deregistration"
Line 181: | Line 181: | ||
|- valign="top" | |- valign="top" | ||
| | | | ||
2 | 2 | ||
(Optional step) | (Optional step) | ||
| VOM | | VOM | ||
Line 201: | Line 201: | ||
#*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 | #*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 | ||
#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 | ||
Line 208: | Line 208: | ||
| 3bis | | 3bis | ||
| VOU | | VOU | ||
| '''Users may ask for an extension of the deregistration timeline ''' <br> | | '''Users may ask for an extension of the deregistration timeline ''' <br> | ||
*The request MUST be submitted within 10 days from the broadcast, answering the main ticket. | *The request MUST be submitted within 10 days from the broadcast, answering the main ticket. | ||
*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. | *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. | ||
Line 215: | Line 215: | ||
| 4 | | 4 | ||
| VOM | | VOM | ||
| '''After 15 days of the previous broadcast, send another broadcast to the VO users ''' <br> | | '''After 15 days of the previous broadcast, send another 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 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 | ||
Line 222: | Line 222: | ||
| 5 | | 5 | ||
| VOM (alternatively VOS) | | 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. '''<br> | | '''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. '''<br> | ||
*''Note for the resource centre: if the RC decides to decommission the VOMS server the following procedure must be used: [[PROC12]], and this task needs to take into account the [https://documents.egi.eu/document/81 Grid Security Traceability and Logging Policy]'' | *''Note for the resource centre: if the RC decides to decommission the VOMS server the following procedure must be used: [[PROC12]], and this task needs to take into account the [https://documents.egi.eu/document/81 Grid Security Traceability and Logging Policy]'' | ||
Line 228: | Line 228: | ||
| 6 | | 6 | ||
| VOM (alternatively VOS) | | 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. <br> | | '''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. <br> | ||
*If this step is carried out directly by the VOS there is no need to open an additional ticket, but the action must be recorded in the master ticket | *If this step is carried out directly by the VOS there is no need to open an additional ticket, but the action must be recorded in the master ticket | ||
Line 234: | Line 234: | ||
| 7 | | 7 | ||
| VOM (alternatively VOS) | | VOM (alternatively VOS) | ||
| '''Broadcast to site managers that the VO has been decommissioned''', adding the following instructions/information: <br> | | '''Broadcast to site managers that the VO has been decommissioned''', adding the following instructions/information: <br> | ||
*The link to the GGUS master ticket | *The link to the GGUS master ticket | ||
*If the resource centre is supporting the VO, it could be disabled in the services' configuration | *If the resource centre is supporting the VO, it could be disabled in the services' configuration | ||
Line 242: | Line 242: | ||
| 8 | | 8 | ||
| VOM (alternatively VOS) | | VOM (alternatively VOS) | ||
| '''Broadcast to VO users that the VO has been decommissioned''', adding the following information: <br> | | '''Broadcast to VO users that the VO has been decommissioned''', adding the following information: <br> | ||
*The VO status will be set to "deleted" in 2 weeks, after this operation the VO will no more be visible in the Operations Portal | *The VO status will be set to "deleted" in 2 weeks, after this operation the VO will no more be visible in the Operations Portal | ||
*A link to the master ticket | *A link to the master ticket | ||
Link the broadcast text in the master ticket <br> | |||
Link the broadcast text in the master ticket <br> | |||
|- valign="top" | |- valign="top" | ||
| 9 | | 9 | ||
| VOM (alternatively VOS) | | 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 <br> | | '''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 <br> | ||
*The decommissioning 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 decommissioning 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. | ||
Line 255: | Line 257: | ||
| 10 | | 10 | ||
| VOM (alternatively VOS) | | 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. <br> | | '''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. <br> | ||
*If this step is carried out directly by the VOS there is no need to open an additional ticket, but the action must be recorded in the master ticket | *If this step is carried out directly by the VOS there is no need to open an additional ticket, but the action must be recorded in the master ticket | ||
Line 261: | Line 263: | ||
| 11 | | 11 | ||
| VOM (alternatively VOS) | | VOM (alternatively VOS) | ||
| '''Close the master ticket''' <br> | | '''Close the master ticket''' <br> | ||
*This step concludes the deregistration procedure | *This step concludes the deregistration procedure | ||
Revision as of 17:34, 30 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 |