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

TODO: The procedure should take the form of procedures of NGI creation.

Tool	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
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"	nothing to do
Gridview	nothing to do	nothing to do
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