|
|
| (43 intermediate revisions by 7 users not shown) |
| Line 1: |
Line 1: |
| {| border="1" | | {{Template:Op menubar}} {{Template:Doc_menubar}} |
| |- | | [[Category:Deprecated]] |
| | '''Title''' | | {| style="border:1px solid black; background-color:lightgrey; color: black; padding:5px; font-size:140%; width: 90%; margin: auto;" |
| | Resource Center renaming Procedure<br>
| | | style="padding-right: 15px; padding-left: 15px;" | |
| |-
| | |[[File:Alert.png]] This page is '''Deprecated'''; the content has been moved to https://confluence.egi.eu/display/EGIPP/PROC15+Resource+Center+renaming |
| | '''Document link''' | |
| | https://wiki.egi.eu/wiki/PROCxx
| |
| |-
| |
| | '''Last modified'''
| |
| | 03-May-2012
| |
| |-
| |
| | '''Policy Group Acronym'''
| |
| | OMB
| |
| |-
| |
| | '''Policy Group Name'''
| |
| | Operations Management Board<br>
| |
| |-
| |
| | '''Contact Person'''
| |
| | Esteban Friere<br>
| |
| |-
| |
| | '''Document Status'''
| |
| | DRAFT
| |
| |-
| |
| | '''Approved Date'''
| |
| | TBD
| |
| |-
| |
| | '''Procedure Statement'''
| |
| | A procedure for directly renaming a Resource Center.<br>
| |
| |} | | |} |
|
| |
| ----
| |
|
| |
| <br>
| |
|
| |
| <font size="4"><u>'''Procedure for renaming a Resource Center.'''</u></font>
| |
|
| |
| <br>
| |
|
| |
| {| border="1"
| |
| |-
| |
| | '''Step [#]'''
| |
| |
| |
| '''Resp. Unit'''<br>
| |
|
| |
| | '''Unit to Contact'''
| |
| | '''Procedure'''
| |
| | width="35%" | '''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.
| |
| | <br>
| |
| |-
| |
| | 2
| |
| | Resource Center
| |
| | <br>
| |
| | 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.
| |
| |-
| |
| | 3
| |
| | Resource Center
| |
| | <br>
| |
| | 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.
| |
| |-
| |
| | 4
| |
| | Resource Center
| |
| | <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).
| |
| |-
| |
| | 5
| |
| | Resource Center
| |
| | <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.
| |
| |-
| |
| | 6
| |
| | Resource Center
| |
| | <br>
| |
| | 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<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.'''''
| |
| |-
| |
| | 6
| |
| | Resource Center
| |
| | 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
| |
|
| |
| | '''''This operation can take two or three working days.'''''
| |
| |-
| |
| | 7
| |
| | Resource Center
| |
| | APEL<br>
| |
| | ''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.
| |
| | If the published accounting is not assigned to the new Resource Center-name, your Resource Center could fail the org.apel.APEL-Sync Nagios test.
| |
| |-
| |
| |
| |
| |
| |
| |
| |
| | It is possible that after the name change, the APEL service will publish all accounting data in the service under new Resource Center-name. If this happens, you should be aware of this and make a comment about it to the APEL support unit.
| |
| Do not forget to change the Resource Center-name on the file /etc/glite-apel-publisher/publisher-config-yaim.xml in the APEL service.
| |
|
| |
| | Mention the date when you will start 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.
| |
| |-
| |
| | 8
| |
| | Resource Center
| |
| | <br>
| |
| | 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 https://operations-portal.egi.eu/broadcast]
| |
| |
| |
| |}
| |
|
| |
| <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 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.
| |
The wiki is deprecated and due to be decommissioned by the end of September 2022.