Difference between revisions of "PROC13 VO Deregistration"
Line 84: | Line 84: | ||
#Site Manager | #Site Manager | ||
A request submitted by the ''VO Manager'' does not require an assessment of the VO usage. | A request submitted by the ''VO Manager'' does not require an assessment of the VO usage. | ||
{| cellspacing="0" cellpadding="5" border="1" class="wikitable" | {| cellspacing="0" cellpadding="5" border="1" class="wikitable" | ||
Line 94: | Line 94: | ||
| 1 | | 1 | ||
| Requester | | Requester | ||
| | | '''Submit a GGUS ticket''', assigned to "VO Services", including the deregistration request. The ticket must contain the following information: <br> | ||
*Role of requester (from the list above) | |||
*Motivation of the request | |||
*Assessment of the VO activities in the past year | |||
|- | |- | ||
Line 104: | Line 103: | ||
| VOS | | VOS | ||
| | | | ||
#Validate the request | #'''Validate the request ''' | ||
##Validate the requester identity | ##Validate the requester identity | ||
##If the requester is the VO Manager, the request is | ##If the requester is the VO Manager, the request is accepted, and the following steps can be skipped | ||
##If the requester is another entity, the following steps must be performed | ##If the requester is another entity, the following steps must be performed | ||
#Communicate to the NGIs (Operations Managers) that a request has been submitted | #Communicate to the NGIs (Operations Managers) that a request has been submitted | ||
|- | |||
| colspan="3" | Steps below must be performed only if the requester is not the VO Manager of the VO. | |||
|- | |- | ||
| 3 | | 3 | ||
| VOS | | VOS | ||
| | | '''Assess the VO activities during the last 12 months'''. To accept the request the requirements are: <br> | ||
*The VO has not produced any accounting data for more than one year. Data available in the ''[http://accounting.egi.eu/custom.php custom view]'' of Accounting Portal | |||
*The VO has not produced any data flows for more than one year. Data available in the ''[http://gstat2.grid.sinica.edu.tw/gstat/vo/ Gstat VO view]'' | |||
If the two conditions above are not satisfied the request is | If the two conditions above are not satisfied the request is rejected, and the following steps can be skipped. | ||
|- | |- | ||
| 4 | | 4 | ||
| VOS | | VOS | ||
| | | '''Notify the VO Manager about the pending request of VO decommission: '''<br> | ||
*Open a GGUS ticket vs the VO support unit (if available). | |||
*Contact directly the VO Manager using the contact in the VO ID card. | |||
*Both GGUS ticket and the mail sent to VO Manager must contain the following information: | |||
**Details of the request | |||
**The deadline to provide feedback on the request (min 1 month). | |||
|- | |- | ||
| 5 | | 5 | ||
| VOM | | VOM | ||
| VO Manager should discuss the VO deregistration request within the community and provide a feedback | | '''VO Manager should discuss the VO deregistration request within the community and provide a feedback ''' | ||
#Discuss the deregistration request within the VO community and provide feedback in the GGUS ticket or via email, within the deadline. | #Discuss the deregistration request within the VO community and provide feedback in the GGUS ticket or via email, within the deadline. | ||
#*If the community still needs the VO, VO Manager should provide the motivations to reject the decommissioning | #*If the community still needs the VO, VO Manager should provide the motivations to reject the decommissioning | ||
Line 141: | Line 140: | ||
| 6 | | 6 | ||
| VOS | | VOS | ||
| | | '''Record in the GGUS ticket the decision''' to approve or reject the request <br> | ||
#The request can be approved if: | |||
#The request can be | |||
#*The VO Manager did not reply and he did not provide any feedback before the deadline | #*The VO Manager did not reply and he did not provide any feedback before the deadline | ||
#*The VO Manager agrees with the proposal | #*The VO Manager agrees with the proposal | ||
##The GGUS ticket can be used for the deregistration procedure | ##The GGUS ticket can be used for the deregistration procedure | ||
#The request must be | #The request must be rejected if: | ||
#*The VO Manager provided feedback and motivations to reject the decommissioning | #*The VO Manager provided feedback and motivations to reject the decommissioning | ||
#*Following step can be skipped | #*Following step can be skipped | ||
##The GGUS ticket should be closed | ##The GGUS ticket should be closed | ||
Line 155: | Line 153: | ||
| 7 | | 7 | ||
| VOM (alternatively the VOS) | | VOM (alternatively the VOS) | ||
| | | '''Start the VO Deregistration procedure '''<br> | ||
|} | |} | ||
Revision as of 10:57, 4 June 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, assigned to "VO Services", 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 | 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 |
|
Revision history
Version | Authors | Date | Comments |
---|---|---|---|
1.0 | Goncalo Borges (LIP) | 16 July 2012 | First version of the procedure |