Difference between revisions of "PROC13 VO Deregistration"
Line 1: | Line 1: | ||
{{Template:Op menubar}} | {{Template:Op menubar}} {{Template:Doc_menubar}} {{TOC_right}} | ||
{{Template:Doc_menubar}} | |||
{{TOC_right}} | |||
{{Ops_procedures | {{Ops_procedures | ||
Line 15: | Line 11: | ||
|Approval_date = 17 July 2012 | |Approval_date = 17 July 2012 | ||
|Procedure_statement = A procedure for the steps involved to decommission a Virtual Organization currently registered in the EGI infrastructure. | |Procedure_statement = A procedure for the steps involved to decommission a Virtual Organization currently registered in the EGI infrastructure. | ||
}} | }} | ||
<br> | |||
= Overview = | = Overview = | ||
A VO registers | 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 = | = Definitions = | ||
Please refer to the [[Glossary|EGI Glossary]] for the definitions of the terms used in this procedure. | |||
Please refer to the [[Glossary|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. | 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. | ||
Line 38: | Line 27: | ||
= Entities involved in the procedure = | = Entities involved in the procedure = | ||
The main players participating in the VO deregistration procedure are: | |||
*The VO Manager (VOM). | |||
*The VO Manager (VOM). | |||
*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 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 resource centres supporting the VO resources. | ||
*The VO users (VOU). | *The VO users (VOU). | ||
The tools available to support the deregistration procedure are: | The tools available to support the deregistration procedure are: | ||
*The EGI Help-desk (GGUS), [https://helpdesk.egi.eu link]. | *The EGI Help-desk (GGUS), [https://helpdesk.egi.eu link]. | ||
*The Accounting Portal, [https://acconting.egi.eu link]. | *The Accounting Portal, [https://acconting.egi.eu link]. | ||
*The EGI Operations Portal, [https://operations-portal.egi.eu link]. | *The EGI Operations Portal, [https://operations-portal.egi.eu link]. | ||
Line 63: | Line 51: | ||
== VO Supervisor (COO) == | == 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 | #Carry out the procedure steps | ||
#Give the users the relevant information about the decommissioning (deadlines, involved resources, files, how to handle it) | #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 | #Follow-up and support users in their file migration procedures until the deadline | ||
== VO Users == | == VO Users == | ||
# Promptly report to VO Manager any request to modify the VO decommissioning timeline | #Promptly report to VO Manager any request to modify the VO decommissioning timeline | ||
= Workflow = | = Workflow = | ||
The VO deregistration workflow is composed by two processes: | The VO deregistration workflow is composed by two processes: | ||
# The validation of the deregistration request | |||
# The actual deregistration | #The validation of the deregistration request | ||
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. | #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 '''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 '''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 | *Actions tagged '''VOU''' are the responsibility of the single VO users | ||
== Request validation == | == Request validation == | ||
The following entities can submit a deregistration request for a VO through a GGUS ticket: | |||
#VO Manager | |||
# VO Manager | #VO Supervisor | ||
# VO Supervisor | #VO User | ||
# VO User | #NGI Operations Manager | ||
# NGI Operations Manager | #Site Manager | ||
# Site Manager | |||
A request submitted by the ''VO Manager'' does not require an assessment of the VO usage. Steps from ''3'' and beyond must be performed only if the requester is not the VO Manager of the VO. | A request submitted by the ''VO Manager'' does not require an assessment of the VO usage. Steps from ''3'' and beyond must be performed only if the requester is not the VO Manager of the VO. | ||
{| cellspacing="0" cellpadding="5" border="1" class="wikitable" | {| cellspacing="0" cellpadding="5" border="1" class="wikitable" | ||
Line 104: | Line 96: | ||
! Action | ! Action | ||
|- valign="top" | |- valign="top" | ||
|1 | | 1 | ||
|Requester | | Requester | ||
| | | | ||
# Submit a GGUS ticket, assigned to "VO Services", including the deregistration request. The ticket must contain the following information: | #Submit a GGUS ticket, assigned to "VO Services", including the deregistration request. The ticket must contain the following information: | ||
#* Role of requester (from the list above) | #*Role of requester (from the list above) | ||
#* Motivation of the request | #*Motivation of the request | ||
#* Assessment of the VO activities in the past year | #*Assessment of the VO activities in the past year | ||
|- | |- | ||
|2 | | 2 | ||
|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 '''accepted''', and the following steps can be skipped | ##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 | ||
|- | |- | ||
|3 | | 3 | ||
|VOS | | VOS | ||
| | | | ||
#Assess the VO activities during the last 12 months. To accept the request the requirements are: | #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 ''[http://accounting.egi.eu/custom.php custom view]'' of Accounting Portal | #*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]'' | #*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 '''rejected''', and the following steps can be skipped. | |||
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: | #Notify the VO Manager about the pending request of VO decommission: | ||
#* Open a GGUS ticket vs the VO support unit (if available). | #*Open a GGUS ticket vs the VO support unit (if available). | ||
#* Contact directly the VO Manager using the contact in the VO ID card. | #*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: | #*Both GGUS ticket and the mail sent to VO Manager must contain the following information: | ||
#** Details of the request | #**Details of the request | ||
#** The deadline to provide feedback on the request (min 1 month). | #**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 | ||
|- | |- | ||
|6 | | 6 | ||
|VOS | | VOS | ||
| | | | ||
# Record in the GGUS ticket the decision to '''approve''' or '''reject''' the request | #Record in the GGUS ticket the decision to '''approve''' or '''reject''' the request | ||
#The request can be '''approved''' if: | #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 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 '''rejected''' if: | #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 | ||
|- | |- | ||
|7 | | 7 | ||
|VOM (alternatively the VOS) | | VOM (alternatively the VOS) | ||
| | | | ||
# Start the VO Deregistration procedure | #Start the VO Deregistration procedure | ||
|} | |} | ||
== VO Deregistration procedure == | == VO Deregistration procedure == | ||
This procedure is performed only if the request is validated. | This procedure is performed only if the request is validated. | ||
<br> | |||
{| cellspacing="0" cellpadding="5" border="1" class="wikitable" | {| cellspacing="0" cellpadding="5" border="1" class="wikitable" | ||
Line 176: | Line 177: | ||
|- valign="top" | |- valign="top" | ||
| 1 | | 1 | ||
| VOM (alternatively VOS) | | 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: | #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) | #*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 | #**If available the link to the GGUS ticket that contains such decision | ||
#* The proposed timeline for the decommission procedure: | #*The proposed timeline for the decommission procedure: | ||
#** Expected date for the VOMS support decommission | #**Expected date for the VOMS support decommission | ||
#** Expected date for the Helpdesk support unit decommission | #**Expected date for the Helpdesk support unit decommission | ||
# Ticket should be assigned to the "VO Services" support unit | #Ticket should be assigned to the "VO Services" support unit | ||
|- valign="top" | |- valign="top" | ||
Line 190: | Line 191: | ||
| VOM | | VOM | ||
| | | | ||
(Optional step) | (Optional step) | ||
# Provide a snapshot of the resources supporting the VO | |||
#* List of grid services | #Provide a snapshot of the resources supporting the VO | ||
#* List of files registered in the VO's LFCs (alternatively storage space used by DN) | #*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, 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. | 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. | ||
|- valign="top" | |- valign="top" | ||
| 3 | | 3 | ||
| VOM (alternatively VOS) | | VOM (alternatively VOS) | ||
| | | | ||
#Send a broadcast to all the VO users, specifying: | #Send a broadcast to all the VO users, specifying: | ||
#* 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 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 | #*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 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 | ||
|- valign="top" | |- valign="top" | ||
|3bis | | 3bis | ||
| VOU | | VOU | ||
| | | | ||
# Users may ask for an extension of the deregistration timeline | #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 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. | ||
|- | |- | ||
|4 | | 4 | ||
|VOM | | VOM | ||
| | | | ||
#After 15 days of the previous broadcast, send another broadcast to the VO users | #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 '''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 | ||
|- valign="top" | |- valign="top" | ||
| 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. | #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 [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]'' | ||
|- valign="top" | |- valign="top" | ||
| 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. | #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 | #*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 | ||
|- valign="top" | |- valign="top" | ||
| 7 | | 7 | ||
| VOM (alternatively VOS) | | VOM (alternatively VOS) | ||
| | | | ||
# Broadcast to site managers that the VO has been decommissioned, adding the following instructions/information: | #Broadcast to site managers that the VO has been decommissioned, adding the following instructions/information: | ||
#* 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 | ||
#* Logs have to be maintained as long as requested by the traceability policy | #*Logs have to be maintained as long as requested by the traceability policy | ||
|- valign="top" | |- valign="top" | ||
| 8 | | 8 | ||
|VOM (alternatively VOS) | | VOM (alternatively VOS) | ||
| | | | ||
# Broadcast to VO users that the VO has been decommissioned, adding the following information: | #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 | #*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 | #Link the broadcast text in the master ticket | ||
|- 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 | #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. | #*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. | ||
|- valign="top" | |- valign="top" | ||
| 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. | #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 | #*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 | ||
|- valign="top" | |- valign="top" | ||
| 11 | | 11 | ||
| VOM (alternatively VOS) | | VOM (alternatively VOS) | ||
| | | | ||
# Close the master ticket | #Close the master ticket | ||
#* This step concludes the deregistration procedure | #*This step concludes the deregistration procedure | ||
|- valign="top" | |- valign="top" | ||
| Additional notes | | 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 | #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 [https://documents.egi.eu/document/81 "Grid Security Traceability and Logging Policy"] | #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 [https://documents.egi.eu/document/81 "Grid Security Traceability and Logging Policy"] | ||
|} | |} | ||
= Revision history= | = Revision history = | ||
{| class="wikitable" | {| class="wikitable" | ||
|- | |- | ||
! Version | ! Version | ||
! Authors | |||
! Date | |||
! Comments | |||
|- | |- | ||
| 1.0 | | 1.0 | ||
| Goncalo Borges (LIP) | | Goncalo Borges (LIP) | ||
| 16 July 2012 | | 16 July 2012 | ||
| First version of the procedure | | First version of the procedure | ||
|} | |} | ||
[[Category:Operations_Procedures]] |
Revision as of 10:48, 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 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:
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 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
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. Steps from 3 and beyond must be performed only if the requester is not the VO Manager of the VO.
# | Responsible | Action |
---|---|---|
1 | Requester |
|
2 | VOS |
|
3 | VOS |
If the two conditions above are not satisfied the request is rejected, and the following steps can be skipped. |
4 | VOS |
|
5 | VOM | VO Manager should discuss the VO deregistration request within the community and provide a feedback
|
6 | VOS |
|
7 | VOM (alternatively the VOS) |
|
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 |