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"
| Line 32: | Line 32: | ||
= Operations Centre decommission request validation = | = Operations Centre decommission request validation = | ||
* The Operations Centre decommission request | * The Operations Centre decommission request can be submit to COD | ||
** by Operations Centre which wants to start own decommission procedure | ** by Operations Centre which wants to start own decommission procedure | ||
** by NGI which took over all sites from the old Operations Centre | ** by NGI which took over all sites from the old Operations Centre | ||
Revision as of 16:30, 22 October 2010
Procedure for the Operations Centre decommission procedure DRAFT
The purpose of this document is to clearly describe the actions and the relative steps to be undertaken for decommission of Operations Centre.
Revision history
| Version | Authors | Date | Comments |
|---|---|---|---|
| 0.3 | Małgorzata Krakowian, Marcin Radecki | 2010-10-11 | Added step concerning removing dteam vo branch for the Operations Centre. |
| 0.2 | Małgorzata Krakowian, Marcin Radecki | 2010-09-20 | Clarification of prerequisite concerning GSTAT.
Added in Operations Centre decommission request validation section that the request can be submit by NGI which took over all sites from Operations Centre. Known issues section added. |
| 0.1 | Małgorzata Krakowian, Marcin Radecki | 2010-08-31 | First draft |
Operations Centre decommission request validation
- The Operations Centre decommission request can be submit to COD
- by Operations Centre which wants to start own decommission procedure
- by NGI which took over all sites from the old Operations Centre
- by COO in any other case
- In case when sites were distributed to different NGIs
- 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 Operations Centre starts when the Operations Centre opens a 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 Operations Centre 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 Operations Centre decommission ticket is provided here:
Subject: Decommission of Operations Centre XXX Dear COD, According to procedure https://wiki.egi.eu/wiki/Operations:EGEE_ROC_decommission we would like to start decommission procedure for Operations Centre XXX. Best regards,
Operations Centre prerequisities
Before opening an Operations Centre decommission GGUS ticket, the Operations Centre should:
| Concerns | Prerequisities |
|---|---|
| GSTAT | All sites which were moved to other Operations Centre and still publish in BDII old NGI/ROC, 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 NGI/ROC SU should be closed. |
| Operational Dashboard | All alarms and operational tickets should be closed |
| GOC DB | No sites defined in GOCDB for the Operations Centre, other than in Closed status. |
Known issues
Please be aware the fact that as a result of Operations Centre decommission the old NGI/ROC view in accounting portal will be unavailable. The problem is registered in GGUS ticket.
Operations Centre decommission process steps
The general idea is that tickets must be closed before being able to move on to the next step.
Decommission steps:
| Step | Action on | Action |
|---|---|---|
| 1 | ROC/NGI | The information that the Operations Centre started decommission process is broadcast by NGI/ROC officials.
(This broadcast should be sent to VO managers and NGI/ROC managers) See the template below for an indication of the message content. Subject: Decommission of Operations Centre XXX has started Dear All, We would like to announce that Operations Centre XXX started decommission procedure. Best regards, |
| 2 | GGUS | Request to close NGI/ROC SU. |
| 3 | GOC DB | Request to deactivated NGI/ROC in the GOC DB. |
| 4 | COD | Request to :
|
| 5 | Operational portal | Request to remove/move data related to the NGI/ROC. |
| 6 | Dteam VO manager | Request to remove the branch for NGI/ROC in Dteam VO VOMS.
How to assign the child ticket: assign the ticket to "VO support" after the selection of "dteam" in the concerned VO field |
| 7 | Nagios | Request to stop monitoring NGI/ROC Nagios instance. |
| 8 | COD | Final checks by the IPC.
(Were all steps taken and finished properly? Close the parent ticket.) |
| 9 | NGI/ROC |
The information that the Operations Centre was decommissioned is broadcast by ex-NGI/ex-ROC officials. (This broadcast should be sent to VO managers and NGI/ROC managers) See the template below for an indication of the message content. Subject: Operations Centre XXX was decommissioned Dear All, We would like to announce that NGI/ROC XXX is now closed. All references to NGI/ROC XXX were removed from operational tools. Best regards, |