The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.
Difference between revisions of "PROC03 Operations Centre decommission"
Jump to navigation
Jump to search
| Line 44: | Line 44: | ||
Before opening an ROC decommission GGUS ticket, the EGEE should: | Before opening an ROC decommission GGUS ticket, the EGEE should: | ||
{| border="1" cellspacing="0" cellpadding="5" align="center" | |||
!Tool | |||
! Prerequisities | |||
|- | |||
| GSTAT | |||
| All sites should be reconfigured according to the instructions at: http://goc.grid.sinica.edu.tw/gocwiki/How_to_publish_my_site_information | |||
<pre> | |||
change the old information from: | |||
SITE_OTHER_EGEE_ROC="XX" | |||
SITE_OTHER_GRID="EGEE" | |||
to: | |||
SITE_OTHER_EGI_NGI="NGI_XXX" | |||
SITE_OTHER_GRID="EGEE|EGI" | |||
</pre> | |||
|- | |||
| GGUS | |||
| All the tickets assigned to the ROC SU should be closed. | |||
|- | |||
| COD | |||
| All alarms and operational tickets should be closed | |||
|- | |||
| GOC DB | |||
| No sites defined in GOCDB for the ROC, other than in Closed status. | |||
|- | |||
|} | |||
= EGEE ROC decommission process steps = | = EGEE ROC decommission process steps = | ||
| Line 76: | Line 102: | ||
remove ROD mailing list from all-operator-on-duty@mailman.egi.eu mailing list | remove ROD mailing list from all-operator-on-duty@mailman.egi.eu mailing list | ||
remove ROD mailing list from operational manual | remove ROD mailing list from operational manual | ||
|- | |- | ||
| GOC DB | | GOC DB | ||
Revision as of 13:10, 31 August 2010
Procedure for the EGEE ROC decommission procedure DRAFT
This page describes (unranked) steps which should be taken to remove ROC from the infrastructure. (https://gus.fzk.de/ws/ticket_info.php?ticket=60602)
The purpose of this document is to clearly describe the actions and the relative steps to be undertaken for decommission of EGEE ROC.
Revision history
| Version | Authors | Date | Comments |
|---|---|---|---|
| 0.1 | Małgorzata Krakowian, Marcin Radecki | 2010-08-31 | First draft |
EGEE ROC decommission request validation
- The EGEE ROC decommission request should be submit to COD by EGEE ROC which wants to start decommission procedure.
- The Central Operator on Duty team - in charge of EGI oversight - is responsible of performing validation of the request and final check of the process.
How to start the decommission process
- The decommission of an EGEE ROC starts when the ROC opens a ROC decommission ticket to COD (via GGUS).
- Once the ticket is filed, COD can start the validation of the request.
- When COD validate the request, in order to trigger the actions described in this document the ROC creates a set of new child tickets that are assigned to the individual partners that are responsible for the various steps. Thereby, the integration process should be as transparent as possible to all parties involved. The required actions are described below.
An example/template for the EGEE ROC decommission ticket is provided here:
Subject: Decommission of EGEE ROC XXX
EGEE ROC prerequisities
Before opening an ROC decommission GGUS ticket, the EGEE should:
| Tool | Prerequisities |
|---|---|
| GSTAT | All sites should be reconfigured according to the instructions at: http://goc.grid.sinica.edu.tw/gocwiki/How_to_publish_my_site_information
change the old information from: SITE_OTHER_EGEE_ROC="XX" SITE_OTHER_GRID="EGEE" to: SITE_OTHER_EGI_NGI="NGI_XXX" SITE_OTHER_GRID="EGEE|EGI" |
| GGUS | All the tickets assigned to the ROC SU should be closed. |
| COD | All alarms and operational tickets should be closed |
| GOC DB | No sites defined in GOCDB for the ROC, other than in Closed status. |
EGEE ROC decommission process steps
TODO: The procedure should take the form of procedures of NGI creation.
| Tool | X | Prerequisities | Description |
|---|---|---|---|
| GGUS | The ROC SU should contain no tickets. | GGUS ticket should be send to GGUS SU with request to close ROC SU | |
| Operational portal | ROC deactivated from GOC DB | GGUS ticket should be send to dashboard SU with request to remove/move data | |
| Nagios | no sites defined in GOCDB | GGUS ticket should be send to Nagios SU with request to stop monitoring Nagios | |
| COD | all alarms and operational tickets should be closed | GGUS ticket should be send to COD SU with request :
remove ROD mailing list from all-operator-on-duty@mailman.egi.eu mailing list remove ROD mailing list from operational manual | |
| GOC DB | No sites defined in GOCDB for the ROC, other than in Closed status. | GGUS ticket should be send to GOCDB SU with request to deactivated ROC in the database |