Difference between revisions of "PROC03 Operations Centre decommission"
Jump to navigation
Jump to search
Line 7: | Line 7: | ||
!Tool | !Tool | ||
! X | ! X | ||
! | ! Prerequisities | ||
! Description | ! Description | ||
|- | |- |
Revision as of 11:17, 3 August 2010
EGEE ROC decommission procedure DRAFT
This page describes steps which should be taken to remove ROC from the infrastructure. (https://gus.fzk.de/ws/ticket_info.php?ticket=60602)
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 removed 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 other than Closed status. | GGUS ticket should be send to GOCDB SU with request to deactivated ROC in the database |