Difference between revisions of "PROC15 Resource Center renaming"
Jump to navigation
Jump to search
(→Steps) |
|||
Line 47: | Line 47: | ||
|- | |- | ||
| 3 | | 3 | ||
| Resource Center | | Resource Center | ||
| <br> | | <br> | ||
Line 60: | Line 53: | ||
* 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). | ||
|- | |- | ||
| | | 4 | ||
| Resource Center | | Resource Center | ||
| <br> | | <br> | ||
Line 67: | Line 60: | ||
* 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. | ||
|- | |- | ||
| | | 5 | ||
| Resource Center | | Resource Center | ||
| <br> | | <br> | ||
Line 73: | Line 66: | ||
| | | | ||
|- | |- | ||
| | | 6 | ||
| Resource Center | | Resource Center | ||
|Accounting Portal<br> | |Accounting Portal<br> | ||
Line 81: | Line 74: | ||
* If the NGI is running a regional instance of this service, duplicate this action to address both the global and regional instances. | * If the NGI is running a regional instance of this service, duplicate this action to address both the global and regional instances. | ||
|- | |- | ||
| | | 7 | ||
| Resource Center | | Resource Center | ||
| GGUS<br> | | GGUS<br> | ||
Line 87: | Line 80: | ||
| | | | ||
|- | |- | ||
| | | 8 | ||
| Resource Center | | Resource Center | ||
| APEL<br> | | APEL<br> | ||
Line 96: | Line 89: | ||
* 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) | ||
|- | |- | ||
| | | 9 | ||
| Resource Center | | Resource Center | ||
| <br> | | <br> | ||
Line 103: | Line 96: | ||
* The Resource Center under the new name should re-enter in the production infrastructure in full shape. | * The Resource Center under the new name should re-enter in the production infrastructure in full shape. | ||
|- | |- | ||
| | | 10 | ||
| Resource Center | | Resource Center | ||
| <br> | | <br> | ||
Line 109: | Line 102: | ||
| | | | ||
|} | |} | ||
==Note== | ==Note== | ||
* GGUS tool: Change the 'notify site' field to the new site name for every open ticket vs the site. | |||
* After the information is changed in the services and in GODCDB, for some tools like GGUS, GSTAT it can take a whole day in order to take the information about new Resources Center name. Although it only should take a maximum of three hours for Nagios tests. | * After the information is changed in the services and in GODCDB, for some tools like GGUS, GSTAT it can take a whole day in order to take the information about new Resources Center name. Although it only should take a maximum of three hours for Nagios tests. | ||
* This change should not affect the jobs running in the 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. | * This change should not affect the jobs running in the 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. | ||
= Revision history= | = Revision history= |
Revision as of 17:18, 24 October 2012
Main | EGI.eu operations services | Support | Documentation | Tools | Activities | Performance | Technology | Catch-all Services | Resource Allocation | Security |
Title | Resource Center renaming Procedure |
Document link | https://wiki.egi.eu/wiki/PROC15 |
Last modified | 4.1 - 03-May-2012 |
Policy Group Acronym | OMB |
Policy Group Name | Operations Management Board |
Contact Group | Esteban Friere |
Document Status | Draft |
Approved Date | |
Procedure Statement | A procedure for directly renaming a Resource Center. |
Owner | Owner of procedure |
Overview
The Resource Center renaming Procedure was created to define steps which have to be taken to rename a Resource Center.
Note: 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.
Steps
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 | Set up an scheduled downtime (it should be sufficient to schedule a downtime for only a few hours). |
| |
4 | 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. |
| |
5 | 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. | ||
6 | 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 |
|
7 | 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 | |
8 | 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. |
|
9 | Resource Center | Expand the downtime if, by some reason, your site is failing SAM tests. |
| |
10 | 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 |
Note
- GGUS tool: Change the 'notify site' field to the new site name for every open ticket vs the site.
- After the information is changed in the services and in GODCDB, for some tools like GGUS, GSTAT it can take a whole day in order to take the information about new Resources Center name. Although it only should take a maximum of three hours for Nagios tests.
- This change should not affect the jobs running in the 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.
Revision history
Version | Authors | Date | Comments |
---|---|---|---|