Difference between revisions of "PROC15 Resource Center renaming"
Line 36: | Line 36: | ||
<br> | <br> | ||
{| border="1" | |||
|- | |||
| '''Step [#]''' | |||
| | |||
'''Max. Duration [work days]''' | |||
(time before moving to next step) | |||
| '''Resp. Unit''' | |||
| '''Escalation procedure''' | |||
| '''Content of the message''' | |||
|- | |||
|} | |||
# | # | ||
Revision as of 08:26, 4 May 2012
Title | Resource Center renaming Procedure |
Document link | [[../../../../../wiki/PROC01|https://wiki.egi.eu/wiki/PROCxx]] |
Last modified | 03-May-2012 |
Policy Group Acronym | OMB |
Policy Group Name | Operations Management Board |
Contact Person | Esteban Friere |
Document Status | DRAFT |
Approved Date | TBD |
Procedure Statement | A procedure for directly renaming a Resource Center. |
Procedure for renaming a Resource Center.
Step [#] |
Max. Duration [work days] (time before moving to next step) |
Resp. Unit | Escalation procedure | Content of the message |
Contact to your NGI managers for supporting about the procedure for site renaming.
Set up an scheduled downtime (it should be sufficient a scheduled downtime of some hours (just to prevent any Nagios failures) .
Make sure that you site do not have current open alarms in your Regional Operations Portal. All alarms in the Regional Operations Portal should be closed before performing the changes .
Go to GOCDB, https://gocdb4.esc.rl.ac.uk/portal/ , and edit the information for your site in order to change the Short Name, Official Name andGIIS URLwith the new site-name.
Change the SITE_NAME YAIM variable on the site-BDII service and reconfigure it. Then, it is necessary to change the SITE_NAME YAIM variable on the other services for your site and also reconfigure. It is convenient perform this step near the end of an hour: since the top-BDIIs update their sites list at the beginning of every hour, therefore you will reduce the absence of your site from top-BDIIs, and you will minimize also the failures.
Open a GGUS ticket to the Accounting(Responsible Unit)in order to move all the accounting data for your site under the new site-name on the EGI Accounting Portal. This operation can take two or three working days.
Open a GGUS ticket to the APEL(Responsible Unit)
Finally, it is not mandatory, but for courtesy you should submit a broadcast to the VO managers for the VOs supported at your site, in order to warning them about the site-name was changed for your site. The broadcast must be send thought the EGI BROADCAST TOOL, https://operations-portal.egi.eu/broadcast
Just to comment that after the information is changed on your services and on GODCDB, some tools like GGUS, GSTAT could take a whole day in order to take the information for your new site-name, although for Nagios tests it only should take a maximum o three hours. Also comment that this change should not affect to the jobs running in your site neither to A/R metrics. It one simply modify the site name in GOCDB while preserving the PRIMARY_KEY for the site, SAM simply renames the site-name without further impact and all availabilities (past and future) will be computed under the new site name.