Difference between revisions of "PROC15 Resource Center renaming"
Jump to navigation
Jump to search
Line 15: | Line 15: | ||
= Overview = | = Overview = | ||
The Resource Center renaming | 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. | '''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 = | = Steps = |
Revision as of 12:01, 16 November 2012
Main | EGI.eu operations services | Support | Documentation | Tools | Activities | Performance | Technology | Catch-all Services | Resource Allocation | Security |
Documentation menu: | Home • | Manuals • | Procedures • | Training • | Other • | Contact ► | For: | VO managers • | Administrators |
Title | Resource Center renaming |
Document link | https://wiki.egi.eu/wiki/PROC15 |
Last modified | 4.1 - 30.10.2012 |
Policy Group Acronym | OMB |
Policy Group Name | Operations Management Board |
Contact Group | Esteban Friere |
Document Status | Approved |
Approved Date | 30.10.2012 |
Procedure Statement | A procedure for changing name of 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 to ask for support about the procedure for renaming the Resource Center. | |
2 | Resource Center | Make sure that your Resource Center does not have 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, gocdb.egi.eu. 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 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 to 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 to your Resource Center name. |
|
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 the name was change for your Resource Center, and to inform them of the new name. The broadcast must be sent through 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 |
---|---|---|---|