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 membership e.g. storage, computing resources, virtual machines.

This procedure applies to VOs which reached PRODUCTION status as a result of PROC14 VO Registration.

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.

The tools available to support the deregistration procedure are:

The EGI Help-desk (GGUS) - link

The Accounting Portal - link

The EGI Operations Portal- link

Workflow

The VO deregistration workflow is composed by two processes:

1. The validation of the deregistration request
2. 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:

1. VO Manager
2. VO Supervisor
3. VO User
4. NGI Operations Manager
5. 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: Role of requester (from the list above) Motivation of the request Assessment of the VO activities in the past year
2	VOS	Validate the request Validate the requester identity 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 Communicate to the NGIs (Operations Managers) that a request has been submitted
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: The VO has not produced any accounting data for more than one year. Data available in the custom view of Accounting Portal The VO has not produced any data flows for more than one year. Data available in the Gstat VO view 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: 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	VOM	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. If the community still needs the VO, VO Manager should provide the motivations to reject the decommissioning
6	VOS	Record in the GGUS ticket the decision to approve or reject the request The request can be approved if: The VO Manager did not reply and he did not provide any feedback before the deadline The VO Manager agrees with the proposal The GGUS ticket can be used for the deregistration procedure The request must be rejected if: The VO Manager provided feedback and motivations to reject the decommissioning Following step can be skipped The GGUS ticket should be closed
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)	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: 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 "VO Services" support unit
2 (Optional step)	VOM	Provide a snapshot of the resources supporting the VO List of grid services List of files registered in the VO's LFCs (alternatively storage space used by DN) 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)	Send a broadcast to all the VO users, specifying: A link to the master GGUS ticket opened at point 1 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 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
3bis	VOU	Users may ask for an extension of the deregistration timeline 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.
4	VOM	After 15 days of the previous broadcast, send another broadcast to the VO users 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
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. 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 Grid Security Traceability and Logging Policy
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. 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
7	VOM (alternatively VOS)	Broadcast to site managers that the VO has been decommissioned, adding the following instructions/information: The link to the GGUS master ticket If the resource centre 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
8	VOM (alternatively VOS)	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 the VO will no more be visible in the Operations Portal A link to the master ticket 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 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.
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. 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
11	VOM (alternatively VOS)	Close the master ticket This step concludes the deregistration procedure
Additional notes		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 must be retained as requested by the "Grid Security Traceability and Logging Policy"

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