PROC13 VO Deregistration

From EGIWiki
(Redirected from PROC13)
Jump to: navigation, search
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


Contents


Title VO Deregistration
Document link https://wiki.egi.eu/wiki/PROC13
Last modified Aug 18th, 2017
Policy Group Acronym OMB
Policy Group Name Operations Management Board
Contact Group operations@egi.eu
Document Status Approved by OMB
Approved Date 17 July 2012 (1.0)
Procedure Statement A procedure for the steps involved to decommission a Virtual Organization currently registered in the EGI infrastructure.
Owner Vincenzo Spinoso



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 currently registered in the EGI infrastructure.


The procedure workflow is composed by two processes:

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

Steps

Request validation

The following entities can submit a deregistration request for a VO through a GGUS ticket:

  1. VO Manager (VM)
  2. VO Supervisor (VS)
  3. VO User (VU)
  4. 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:

  • Role of requester (from the list above)
  • Motivation of the request
  • Assessment of the VO activities in the past year: A request submitted by the VO Manager does not require an assessment of the VO usage
2 VS
  1. Validate the request
    1. Validate the requester identity
    2. If the requester is the VO Manager, the request is accepted, and next steps of Request Validation can be skipped
    3. If the requester is another entity, the following steps must be performed
  2. Communicate to the National Initiatives managers that a request has been submitted
3 VS

Assess the VO activities during the last 12 months.

To accept the request the requirements are:

  • The VO has not produced accounting data for more than one year. Data available on the Accounting Portal (HTC and Cloud views)
4 VS 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 VM VO Manager should discuss the VO deregistration request within the community and provide a 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 VS Record in the GGUS ticket the decision to approve or reject the request
  1. The request can be approved if:
    • The VO Manager did not reply and s/he did not provide any feedback before the deadline
    • The VO Manager agrees with the proposal
    1. The GGUS ticket can be used for the deregistration procedure
  2. The request must be rejected if:
    • The VO Manager provided feedback and motivations to reject the decommissioning

VO Deregistration procedure

This procedure is performed only if the request is accepted.


# Responsible Action
1

VM (or 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:
  • 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

2

VM (or VS)

  1. 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
    • 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.
  2. 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
3

VM (or VS)

After 2 weeks resend 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 2)
  • If users asked for an extension, send a broadcast with the new timeline
4

VM (or 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 (or VS)

Broadcast to RC that the VO is going to be decommissioned

Adding the following instructions/information:

  • The link to the GGUS master ticket
  • If the RC is supporting the VO are free to decommission any allocated resources and stop any VO-specific activity  
  • Logs have to be maintained as long as requested by the traceability policy

6

VM (or VS)

Open a GGUS ticket  to "GGUS" support unit requesting the decommissioning of the VO support unit if this support unit is available

7 VM (or VS) Open a GGUS ticket  to "Perun" support unit requesting end of support for the VO if Vo has been support by Perun (Cloud VOs)
8 VM (or VS) Open a GGUS ticket  to "AppDB" support unit requesting end of support for the VO if Vo has been a using cloud resources
9

VM (or 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
10 VS Change VO status to "DELETED"
11

VM (or VS)

Close the main ticket
  • This step concludes the deregistration procedure
Additional notes
  1. 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
  2. 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
M. Krakowian, Paul Millar 27 August 2014 Making procedure more readable.
Alessandro Paolini 2016-06-08 Changed contact group -> Operations
2.0 Alessandro Paolini 2017-08-18 Request validation, step 3: corrected the link to the accounting portal. VO Deregistration procedure section: the VO status "suspended" doesn't exist any more, so it was removed the old steps 5 and 6 mentioning it; as consequence, it is no more necessary to send a broadcast to the users notifying them about the "suspended" status: removed the old step 8.
Personal tools
Namespaces
Variants
Actions
Navigation
Toolbox
Print/export