Difference between revisions of "PROC15 Resource Center renaming"
Line 57: | Line 57: | ||
| <br> | | <br> | ||
| Make sure that your Resource Center does not has current open alarms in your (Regional) Operations Portal. | | Make sure that your Resource Center does not has current open alarms in your (Regional) Operations Portal. | ||
| All alarms in the (Regional) Operations Portal should be closed before performing the changes. | | | ||
* All alarms in the (Regional) Operations Portal should be closed before performing the changes. | |||
|- | |- | ||
| 3 | | 3 | ||
Line 63: | Line 64: | ||
| <br> | | <br> | ||
| Make sure that your Resource Center does not has any open GGUS ticket or any open ticket in your regional helpdesk system. | | Make sure that your Resource Center does not has any open GGUS ticket or any open ticket in your regional helpdesk system. | ||
| All tickets should be closed before performing the changes. | | | ||
* All tickets should be closed before performing the changes. | |||
|- | |- | ||
| 4 | | 4 | ||
Line 69: | Line 71: | ||
| <br> | | <br> | ||
| Set up an scheduled downtime (it should be sufficient to schedule a downtime for only a few hours).<br> | | Set up an scheduled downtime (it should be sufficient to schedule a downtime for only a few hours).<br> | ||
| This will prevent SAM failures and minimize impact in the reliability metrics. After the change in GOCDB the NGI regional SAM should be updated with the new Resource Center name 3 hours after (max). | | | ||
* This will prevent SAM failures and minimize impact in the reliability metrics. After the change in GOCDB the NGI regional SAM should be updated with the new Resource Center name 3 hours after (max). | |||
|- | |- | ||
| 5 | | 5 | ||
Line 75: | Line 78: | ||
| <br> | | <br> | ||
| Edit the information for your Resource Center in the '''GOCDB''', [https://gocdb4.esc.rl.ac.uk/portal/ https://gocdb4.esc.rl.ac.uk/portal/]. Change the '''''Short Name''''', '''''Official Name''''' and '''''GIIS URL''''' to the new Resource Center details. <br> | | Edit the information for your Resource Center in the '''GOCDB''', [https://gocdb4.esc.rl.ac.uk/portal/ https://gocdb4.esc.rl.ac.uk/portal/]. Change the '''''Short Name''''', '''''Official Name''''' and '''''GIIS URL''''' to the new Resource Center details. <br> | ||
| It is convenient to perform this step near the end of an hour as the top-BDIIs update their Resource Centers list at the beginning of every hour. This way you can reduce the absence of your Resource Center from top-BDIIs, and you will also minimize the failures. | | | ||
* It is convenient to perform this step near the end of an hour as the top-BDIIs update their Resource Centers list at the beginning of every hour. This way you can reduce the absence of your Resource Center from top-BDIIs, and you will also minimize the failures. | |||
|- | |- | ||
| 6 | | 6 | ||
Line 86: | Line 90: | ||
| Resource Center | | Resource Center | ||
|Accounting Portal<br> | |Accounting Portal<br> | ||
| Open a GGUS ticket to the '''Accounting Portal''' ''(Responsible Unit)'' '''in order to move all the accounting data for your '''Resource Center''' under the new '''Resource Center''' | |||
| | | | ||
* This operation can take two or three working days. | |||
|- | |- | ||
| 8 | | 8 | ||
| Resource Center | | Resource Center | ||
| GGUS<br> | | GGUS<br> | ||
| | | Open a GGUS ticket to the '''GGUS''' ''(Responsible Unit)'' '''in order to move all the local DB records under the old''' Resource Center name '''to the new''' Resource Center name | ||
Open a GGUS ticket to the '''GGUS''' ''(Responsible Unit)'' '''in order to move all the local DB records under the old''' Resource Center name '''to the new''' Resource Center name | |||
| | | | ||
|- | |- | ||
Line 105: | Line 108: | ||
* It is possible that after the name change, the APEL service will publish all accounting data in the service under the new Resource Center name. You should pay attention to this fact and communicate it to the APEL support unit. Mention the date when you started to publish accounting data under the new Resource Center name to the APEL support unit in order to preserve all the previous accounting data before that date under the old name. Published accounting data after that date should be under the new Resource Center-name. | * It is possible that after the name change, the APEL service will publish all accounting data in the service under the new Resource Center name. You should pay attention to this fact and communicate it to the APEL support unit. Mention the date when you started to publish accounting data under the new Resource Center name to the APEL support unit in order to preserve all the previous accounting data before that date under the old name. Published accounting data after that date should be under the new Resource Center-name. | ||
* Do not forget to change the Resource Center-name on the file /etc/glite-apel-publisher/publisher-config-yaim.xml in the APEL service (YAIM should take care of that but please re-check it) | * Do not forget to change the Resource Center-name on the file /etc/glite-apel-publisher/publisher-config-yaim.xml in the APEL service (YAIM should take care of that but please re-check it) | ||
|- | |||
| 10 | |||
| Resource Center | |||
| <br> | |||
| Expand the downtime if, by some reason, your site is failing SAM tests. | |||
| | |||
* The Resource Center under the new name should re-enter in the production infrastructure in full shape. | |||
|- | |- | ||
| | | 11 | ||
| Resource Center | | Resource Center | ||
| <br> | | <br> |
Revision as of 18:09, 4 May 2012
Title | Resource Center renaming Procedure |
Document link | 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 [#] |
Resp. Unit |
Unit to Contact | Procedure | Remarks |
1 | Resource Center | NGI Manager | Contact your NGI manager(s) to inform them and for support about the procedure for renaming the Resource center. | |
2 | Resource Center | Make sure that your Resource Center does not has current open alarms in your (Regional) Operations Portal. |
| |
3 | Resource Center | Make sure that your Resource Center does not has any open GGUS ticket or any open ticket in your regional helpdesk system. |
| |
4 | Resource Center | Set up an scheduled downtime (it should be sufficient to schedule a downtime for only a few hours). |
| |
5 | Resource Center | Edit the information for your Resource Center in the GOCDB, https://gocdb4.esc.rl.ac.uk/portal/. Change the Short Name, Official Name and GIIS URL to the new Resource Center details. |
| |
6 | Resource Center | Change the SITE_NAME YAIM variable on the site-BDII service and reconfigure it. It is also necessary to reconfigure all the services for your Resource Center that use of publish the SITE_NAME YAIM variable. | ||
7 | Resource Center | Accounting Portal |
Open a GGUS ticket to the Accounting Portal (Responsible Unit) in order to move all the accounting data for your Resource Center under the new Resource Center |
|
8 | Resource Center | GGUS |
Open a GGUS ticket to the GGUS (Responsible Unit) in order to move all the local DB records under the old Resource Center name to the new Resource Center name | |
9 | Resource Center | APEL |
Open a GGUS ticket to the APEL (Responsible Unit) in order to let them know that you are going to change the name of your Resource Center. |
|
10 | Resource Center | Expand the downtime if, by some reason, your site is failing SAM tests. |
| |
11 | Resource Center | Finally, as a courtesy, submit a broadcast to the VO managers for the VOs supported at your Resource Center, in order to warn them about that the name was changed for your Resource Center, and to inform them of the new name. 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 Resources Center name, although it only should take a maximum of three hours for Nagios tests. Also, this change should not affect the jobs running in your site nor the A/R metrics. If one simply modifies the site name in the GOCDB while preserving the PRIMARY_KEY for the site, SAM simply renames the Resource Center without further impact and all availabilities (past and future) will be computed under the new Resource Center name.
Note that this procedure is specifically aimed at Resource Centers using gLite. There should be very little difference in the procedure for Resource Centers supporting other middleware stacks.