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
(→Steps) |
|||
| Line 1: | Line 1: | ||
{{Template:Op menubar}} | {{Template:Op menubar}} {{Template:Doc_menubar}} | ||
{{Template:Doc_menubar}} | |||
{{TOC_right}} | {{TOC_right}} {{Ops_procedures | ||
{{Ops_procedures | |||
|Doc_title = Operations Centre decommission | |Doc_title = Operations Centre decommission | ||
|Doc_link = [[PROC03|https://wiki.egi.eu/wiki/PROC03]] | |Doc_link = [[PROC03|https://wiki.egi.eu/wiki/PROC03]] | ||
| Line 14: | Line 11: | ||
|Approval_date = 26.10.2010 | |Approval_date = 26.10.2010 | ||
|Procedure_statement = The purpose of this document is to clearly describe the actions and the relative steps to be undertaken for decommission of Operations Centre. | |Procedure_statement = The purpose of this document is to clearly describe the actions and the relative steps to be undertaken for decommission of Operations Centre. | ||
}} | }} | ||
= Overview = | = Overview = | ||
The purpose of this document is to clearly describe the actions and the relative steps to be undertaken for decommission of Operations Centre. | The purpose of this document is to clearly describe the actions and the relative steps to be undertaken for decommission of Operations Centre. | ||
= 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. | ||
= Operations Centre decommission request validation = | = Operations Centre decommission request validation = | ||
* An Operations Centre decommission request can be submitted to | *An Operations Centre decommission request can be submitted to ''Operations'' | ||
** 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 | ||
** by COO in any other case (in this case all actions assigned to ROC/NGI in the procedure will be assigned to | **by COO in any other case (in this case all actions assigned to ROC/NGI in the procedure will be assigned to ''Operations'') | ||
* In case when sites were distributed to different NGIs | *In case when sites were distributed to different NGIs | ||
* | *EGI Operations 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 = | = How to start the decommission process = | ||
* The decommission of an Operations Centre starts when the Operations Centre manager opens a decommission ticket to | *The decommission of an Operations Centre starts when the Operations Centre manager opens a decommission ticket to ''Operations ''(via GGUS). | ||
* Once the ticket is filed, | *Once the ticket is filed, ''Operations ''can start the validation of the request. | ||
* When | *When ''Operations ''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: | |||
<pre>Subject: Decommission of Operations Centre XXX | <pre>Subject: Decommission of Operations Centre XXX | ||
Dear | Dear ''Operations'', | ||
According to procedure https://wiki.egi.eu/wiki/PROC03_Operations_Centre_decommission we would like to start decommission process for Operations Centre XXX. | According to procedure https://wiki.egi.eu/wiki/PROC03_Operations_Centre_decommission we would like to start decommission process for Operations Centre XXX. | ||
Best regards, | Best regards, | ||
</pre> | </pre> | ||
<br> | |||
== Operations Centre prerequisites == | |||
Before opening an Operations Centre decommission GGUS ticket, the Operations Centre should: | |||
{| class="wikitable" | |||
{| | |- | ||
! Concerns | ! Concerns | ||
! Prerequisites | ! Prerequisites | ||
|- | |- | ||
| GGUS | | 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 | |||
|- | |||
| GGUS | |||
| All the tickets assigned to the NGI/ROC SU should be closed or moved to a new support unit. | | All the tickets assigned to the NGI/ROC SU should be closed or moved to a new support unit. | ||
|- | |- | ||
| Operational Dashboard | | Operational Dashboard | ||
| All alarms should be closed. Operational tickets should be closed or moved to a new support unit in GGUS if the sites were moved to other Operations Centre. | | All alarms should be closed. Operational tickets should be closed or moved to a new support unit in GGUS if the sites were moved to other Operations Centre. | ||
|- | |- | ||
| GOC DB | | GOC DB | ||
| No sites defined in GOCDB for the Operations Centre, other than in Closed status. | | No sites defined in GOCDB for the Operations Centre, other than in Closed status. | ||
|- | |- | ||
| Dteam VO | | Dteam VO | ||
| Sites administrators from sites which belonged to the Operations Centre should be informed about the decommission process. Especially that they will be removed from Operations Centre's branch in Dteam VO VOMS and they should submit a request to be registered to the branch relevant to the new Operations Centre they joined. | | Sites administrators from sites which belonged to the Operations Centre should be informed about the decommission process. Especially that they will be removed from Operations Centre's branch in Dteam VO VOMS and they should submit a request to be registered to the branch relevant to the new Operations Centre they joined. | ||
|} | |} | ||
== Known issues == | == 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 [https://gus.fzk.de/ws/ticket_info.php?ticket=62256 GGUS ticket]. | 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 [https://gus.fzk.de/ws/ticket_info.php?ticket=62256 GGUS ticket]. | ||
= Steps = | = Steps = | ||
| Line 133: | Line 130: | ||
VO support | VO support | ||
(concerned VO = dteam) | (concerned VO = dteam) | ||
|- | |- | ||
| Line 144: | Line 141: | ||
| | | | ||
VO support <br> | VO support <br> | ||
(concerned VO = ops) | (concerned VO = ops) | ||
|- | |- | ||
| 7 | | 7 | ||
| SAM EGI support | | SAM EGI support | ||
| Request to stop monitoring NGI/ROC Nagios instance. | | Request to stop monitoring NGI/ROC Nagios instance. | ||
| ARGO/SAM EGI support | | ARGO/SAM EGI support | ||
| Line 181: | Line 178: | ||
|} | |} | ||
= Revision history = | = Revision history = | ||
{| | |||
! Version | {| class="wikitable" | ||
|- | |||
! Version | |||
! Authors | |||
! Date | |||
! Comments | |||
|- | |- | ||
| | | | ||
| Line 190: | Line 192: | ||
| | | | ||
|} | |} | ||
[[Category:Operations_Procedures]] | |||
Revision as of 15:38, 4 August 2014
| 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 | Operations Centre decommission |
| Document link | https://wiki.egi.eu/wiki/PROC03 |
| Last modified | 1.0 - 22.10.2010 |
| Policy Group Acronym | Grid Operations Oversight/Central Operator on Duty |
| Policy Group Name | Operations Management Board |
| Contact Group | manager-central-operator-on-duty@mailman.egi.eu |
| Document Status | Approved |
| Approved Date | 26.10.2010 |
| Procedure Statement | The purpose of this document is to clearly describe the actions and the relative steps to be undertaken for decommission of Operations Centre. |
| Owner | Owner of procedure |
Overview
The purpose of this document is to clearly describe the actions and the relative steps to be undertaken for decommission of Operations Centre.
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.
Operations Centre decommission request validation
- An Operations Centre decommission request can be submitted to Operations
- 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 this case all actions assigned to ROC/NGI in the procedure will be assigned to Operations)
- In case when sites were distributed to different NGIs
- EGI Operations 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 manager opens a decommission ticket to Operations (via GGUS).
- Once the ticket is filed, Operations can start the validation of the request.
- When Operations 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 ''Operations'', According to procedure https://wiki.egi.eu/wiki/PROC03_Operations_Centre_decommission we would like to start decommission process for Operations Centre XXX. Best regards,
Operations Centre prerequisites
Before opening an Operations Centre decommission GGUS ticket, the Operations Centre should:
| Concerns | Prerequisites |
|---|---|
| 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 |
| GGUS | All the tickets assigned to the NGI/ROC SU should be closed or moved to a new support unit. |
| Operational Dashboard | All alarms should be closed. Operational tickets should be closed or moved to a new support unit in GGUS if the sites were moved to other Operations Centre. |
| GOC DB | No sites defined in GOCDB for the Operations Centre, other than in Closed status. |
| Dteam VO | Sites administrators from sites which belonged to the Operations Centre should be informed about the decommission process. Especially that they will be removed from Operations Centre's branch in Dteam VO VOMS and they should submit a request to be registered to the branch relevant to the new Operations Centre they joined. |
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.
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 | GGUS SU |
|---|---|---|---|
| 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. | GGUS |
| 3 | GOC DB | Request to deactivated NGI/ROC in the GOC DB. | GOC DB |
| 4 | Operational portal | Request to remove/move data related to the NGI/ROC. | Operational portal |
| 5 | 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 |
VO support (concerned VO = dteam) |
| 6 | OPS VO manager | Request to remove NGI/ROC representative membership in OPS VO VOMS.
How to assign the child ticket: assign the ticket to "VO support" after the selection of "ops" in the concerned VO field Note: The removal will not impact on membership as a representative from other NGI/ROC. Representative is only removed from proper branch,so there is no danger to remove someone who needs the membership as representative from other NGI/ROC |
VO support (concerned VO = ops) |
| 7 | SAM EGI support | Request to stop monitoring NGI/ROC Nagios instance. | ARGO/SAM EGI support |
| 8 | Operations | Final checks by the Operations.
(Were all steps taken and finished properly? Close the parent ticket.) |
Operations |
| 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, |
Revision history
| Version | Authors | Date | Comments |
|---|---|---|---|