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 Procedure
Document link	[1]
Version - last modified	0.1
Policy Group Acronym	OMB
Policy Group Name	Operations Management Board
Contact Person	operations@mailman.egi.eu
Document Status	DRAFT
Approved Date	N/A
Procedure Statement	A procedure for the steps involved to decommission a Virtual Organization currently registered in the EGI infrastructure.

VO Deregistration Procedure

A VO registers [R3] to the European Grid Infrastructure in the perspective to get access to resources supplied by the participating resource centres. The VO is bound by the appropriate operational and security policies [R4, R5, R6, R7] but those documents do not define how to handle situations like a VO wanting to leave the European Grid Infrastructure. This document proposes a procedure to permanently deregister a VO from the European Grid Infrastructure.

The current document is intended to the VO manager, who understands the needs of the VO users and is responsible to apply the registration and deregistration procedures, and to the VO supervisor, who coordinates the overall process and takes the VO manager role case he is unavailable, unresponsive or unable to commit to the defined procedure timelines. It is certainly also beneficial for site managers, as well as people involved in grid management aspects, especially in the fields of security and operations.

Note: a separate policy document will provide the guidelines to propose and agree a VO deregistration. This document contains the steps to be performed once the decision to decommission the VO is taken.

Definitions

• Resource Centre refers to the definition in the "Resource Centre OLA".

In this document, the term "site" is deprecated, and Resource Centre has been used in its place.

• Other entities involved in this procedure are defined in the EGI Glossary.

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.
• The VO supervisor.
• The resource centres supporting the VO resources.
• The VO users.

The tools available to support the deregistration procedure are:

• The EGI Help-desk (GGUS), link.
• The Accounting Portal, link.
• The EGI Operations Portal, link.

Contact information

• EGI Operations: operations (at) mailman.egi.eu
• EGI Resource Infrastructure Providers are listed on the EGI web site
• A list of EGI Operations Centres with their respective contact information is available from the GOCDB
• The list of VO's served by a specific Resource Centre and their ID cards can be retrieved from the Operations Portal.
• The VO managers and their contact information for a specific VO can be retrieved from the Operations Portal.

Actions and responsibilities

VO's and VO managers

1. give the users the relevant information about the decommissioning (deadlines, involved resources, files, how to handle it)
2. follow-up and support users in their file migration procedures until the deadline
3. inform Resource Centre about the status of the migration(s)

Workflow

Steps

• 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).
• Actions tagges VOU are the responsibility of the single VO users

#	Responsible	Action
1	VOM (alternatively VOS)	Open a GGUS ticket to begin the deregistration process. 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 server decommission Expected date for the Helpdesk support unit decommission
2-a	VOM	(Optional step) Provide a snapshot of the resources supporting List of grid services List of files registered in the VO's LFCs
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 server is being decommissioned in one month (minimum), after the decommission 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 VOM 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 VOM 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 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 (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.
5	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
6	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
7	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
8	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
9	VOM (alternatively VOS)	Close the master ticket
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 was providing 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"