Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.

Difference between revisions of "PROC15 Resource Center renaming"

From EGIWiki
Jump to navigation Jump to search
m
Line 55: Line 55:
| 2  
| 2  
| Resource Center  
| Resource Center  
| <br>
| <br>  
| Set up an scheduled downtime (it should be sufficient a scheduled 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>  
| To prevent any Nagios failures.
| To prevent any Nagios failures.
|-
|-
| 3  
| 3  
| Resource Center  
| Resource Center  
| <br>
| <br>  
| Make sure that you site do not have current open alarms in your Regional Operations Portal.  
| Make sure that your Resource Center does not have 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.
|-
|-
| 4  
| 4  
| Resource Center  
| Resource Center  
| <br>
| <br>  
| Go to '''GOCDB''', [https://gocdb4.esc.rl.ac.uk/portal/ https://gocdb4.esc.rl.ac.uk/portal/] , and edit the information for your site in order to change the '''''Short Name''''', '''''Official Name''''' and '''''GIIS URL'''''with the new site-name.  
| 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-name details.  
| <br>
| <br>
|-
|-
| 5  
| 5  
| Resource Center  
| Resource Center  
| <br>
| <br>  
| 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.  
| 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 Resource Center 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.
| 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.&nbsp; This way you can reduce the absence of your Resource Center from top-BDIIs, and you will also minimize&nbsp; the failures.
|-
|-
| 6  
| 6  
| <br>
| Resource Center
| <br>
| <br>  
|  
|  
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 '''Accounting''' ''(Responsible Unit) '''''in order to move all the accounting data for your ''''''Resource Center''''''under the new '''Resource '''Center


| <br>
| '''''This operation can take two or three working days.'''''
|-
|-
| 7  
| 7  
| <br>
| Resource Center
| <br>
| <br>  
| ''Open a GGUS ticket to the '''APEL''' ''(Responsible Unit) in order to let them know that you are going to performance this change, because your site could fail the org.apel.APEL-Sync Nagios test due to the accounting published is not being assigned to the new site-name. It is possible that after the change, the APEL service will publish all the accounting data in the service under new site-name, so you should be aware of it and comment it to the APEL support unit if it happens. On the other hand, you should mention the date of when you publish the accounting data under the new site-name to the APEL support unit in order to preserve under the old name all the previous accounting data before that date, and the published accounting data after that date should be under the new site-name. Do not forget to change the site-name on the file /etc/glite-apel-publisher/publisher-config-yaim.xml in the APEL service.
| ''Open a GGUS ticket to the '''APEL''' ''(Responsible Unit) in order to let them know that you are going to performance this change, because your site could fail the org.apel.APEL-Sync Nagios test due to the accounting published is not being assigned to the new Resource Center-name. It is possible that after the change, the APEL service will publish all the accounting data in the service under new site-name, so you should be aware of it and comment it to the APEL support unit if it happens. On the other hand, you should mention the date of when you publish the accounting data under the new site-name to the APEL support unit in order to preserve under the old name all the previous accounting data before that date, and the published accounting data after that date should be under the new site-name. Do not forget to change the site-name on the file /etc/glite-apel-publisher/publisher-config-yaim.xml in the APEL service.  
| <br>
| <br>
|-
|-
| 8  
| 8  
| <br>
| Resource Center
| <br>
| <br>  
| 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 https://operations-portal.egi.eu/broadcast]  
| Finally, it is not mandatory, but for courtesy you should submit a broadcast to the VO managers for the VOs supported at your Resource Center, 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 https://operations-portal.egi.eu/broadcast]  
| <br>
| <br>
|}
|}

Revision as of 08:08, 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 [#]

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
Set up an scheduled downtime (it should be sufficient to schedule a downtime for only a few hours).
To prevent any Nagios failures.
3 Resource Center
Make sure that your Resource Center does not have current open alarms in your (Regional) Operations Portal. All alarms in the (Regional) Operations Portal should be closed before performing the changes.
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-name details.
5 Resource Center
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 Resource Center and also reconfigure. 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 Resource Center

Open a GGUS ticket to the Accounting (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.
7 Resource Center
Open a GGUS ticket to the APEL (Responsible Unit) in order to let them know that you are going to performance this change, because your site could fail the org.apel.APEL-Sync Nagios test due to the accounting published is not being assigned to the new Resource Center-name. It is possible that after the change, the APEL service will publish all the accounting data in the service under new site-name, so you should be aware of it and comment it to the APEL support unit if it happens. On the other hand, you should mention the date of when you publish the accounting data under the new site-name to the APEL support unit in order to preserve under the old name all the previous accounting data before that date, and the published accounting data after that date should be under the new site-name. Do not forget to change the site-name on the file /etc/glite-apel-publisher/publisher-config-yaim.xml in the APEL service.
8 Resource Center
Finally, it is not mandatory, but for courtesy you should submit a broadcast to the VO managers for the VOs supported at your Resource Center, 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.