Page tree
Skip to end of metadata
Go to start of metadata

Document control

AreaEGI Federation Operations
Procedure status

FINAL

OwnerMatthew Viljoen 
ApproversOperations Management Board
Approval status

APPROVED

Approved version and date

v7,  

Statement

The purpose of this document is to clearly describe the actions and the relative steps to be undertaken for decommissioning an Operations Centre.

Next procedure reviewupon request

Procedure reviews

The following table is updated after every review of this procedure.

DateReview bySummary of resultsFollow-up actions / Comments

 

Alessandro Paolini copy from PROC03_Operations_Centre_decommission in EGI Wiki. Replaced GSTAT with Information system. Removed step about the NGI/ROC nagios instance




Table of contents

Overview

The purpose of this document is to clearly describe the actions and the relative steps to be undertaken for decommissioning an 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 (Chief Operations Officer) 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://confluence.egi.eu/display/EGIPP/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:

ConcernsPrerequisites
Information SystemAll sites which were moved to other Operations Centre and still publish in BDII old NGI/ROC, should be reconfigured according to the instructions at: MAN01_How_to_publish_Site_Information in EGI Wiki
GGUSAll the tickets assigned to the NGI/ROC SU should be closed or moved to a new support unit.
Operational DashboardAll 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 DBNo sites defined in GOCDB for the Operations Centre, other than in Closed status.
Dteam VOSites 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.

Steps

The general idea is that tickets must be closed before being able to move on to the next step.

StepAction onActionGGUS SU
1ROC/NGIThe information that the Operations Centre started decommission process is sent to EGI operations.

See the template below for an indication of the message content.

Subject: Decommission of Operations Centre XXX has started

Dear Operations,

We would like to announce that Operations Centre XXX started decommission procedure.

Best regards,

2GGUSRequest to close NGI/ROC SU.GGUS
3GOC DBRequest to deactivated NGI/ROC in the GOC DB and remove NGI/ROC service group.GOC DB
4Operational portalRequest to remove/move data related to the NGI/ROC.Operational portal
5Dteam VO managerRequest 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)

6OPS VO managerRequest 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)

7OperationsRequest to remove information about NGI core services from wiki pages (NGI service group, top-BDII) and update NGI managers mailing list.Operations
8OperationsFinal checks by the Operations.

(Were all steps taken and finished properly? Close the parent ticket.)

Operations
9Operations

The information that the Operations Centre has been decommissioned should be sent in Monthly broadcast and announced during OMB by EGI Operations team.

(This broadcast should be sent to VO managers (except Ops and Dteam VO) and NOC/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,