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"
(Created page with "{| border="1" |- | '''Title''' | ''a synthetic name identifying the subject of the procedure document'' |- | '''Document link''' | ''the URL to the wiki page'' |- | '''Last mod...") |
|||
| Line 2: | Line 2: | ||
|- | |- | ||
| '''Title''' | | '''Title''' | ||
| | | Resource Center renaming Procedure<br> | ||
|- | |- | ||
| '''Document link''' | | '''Document link''' | ||
| | | [[../../../../../wiki/PROC01|https://wiki.egi.eu/wiki/PROCxx]] | ||
|- | |- | ||
| '''Last modified''' | | '''Last modified''' | ||
| | | 03-May-2012 | ||
|- | |- | ||
| '''Policy Group Acronym''' | | '''Policy Group Acronym''' | ||
| | | OMB | ||
|- | |- | ||
| '''Policy Group Name''' | | '''Policy Group Name''' | ||
| | | Operations Management Board<br> | ||
|- | |- | ||
| '''Contact Person''' | | '''Contact Person''' | ||
| | | Esteban Friere<br> | ||
|- | |- | ||
| '''Document Status''' | | '''Document Status''' | ||
| | | DRAFT | ||
|- | |- | ||
| '''Approved Date''' | | '''Approved Date''' | ||
| | | TBD | ||
|- | |- | ||
| '''Procedure Statement''' | | '''Procedure Statement''' | ||
| | | A procedure for directly renaming a Resource Center.<br> | ||
|} | |} | ||
---- | ---- | ||
<br> | |||
<style type="text/css"><!-- @page { margin: 0.79in } P { margin-bottom: 0.08in } A:link { so-language: zxx } --> </style><font size="4"><u>'''Procedure for renaming a Resoruce Center.'''</u></font><br> | |||
<br> | |||
# | |||
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/ 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'''''<span style="font-style: normal"><span style="font-weight: normal">with | |||
the new site-name.</span></span> | |||
# | |||
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 <span style="font-style: normal">'''Accounting | |||
Portal '''</span>'''''(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 ''<span style="font-style: normal">'''APEL | |||
'''</span>'''''(Responsible Unit)'''''<span style="font-style: normal">'''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.'''</span> | |||
# | |||
<span style="font-style: normal"><span style="font-weight: normal">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]</span></span> | |||
<br> | <br> | ||
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. | |||
<br> | |||
Revision as of 22:49, 3 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. |
<style type="text/css"><!-- @page { margin: 0.79in } P { margin-bottom: 0.08in } A:link { so-language: zxx } --> </style>Procedure for renaming a Resoruce Center.
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 Portal (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)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.
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.