38
edits
Rebooting Offsite: Difference between revisions
Jump to navigation
Jump to search
no edit summary
(Created page with "= Pre-flight checks = * Access to the Web GUI * Access to the terminal through SSH * Zulip and Gitlab are running on it, so needed to communicate first on Organisational channel, to make sure everyone has read and agreed on it. = Rebooting = # Make sure all the pre flight checks are done # Make an schedule for doing the rebootng. # Create a maintenance period on Zabbix with all the vms are running on Offsite and Offsite itself # Update the packages through terminal `ap...") |
No edit summary |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 9: | Line 9: | ||
# Make an schedule for doing the rebootng. | # Make an schedule for doing the rebootng. | ||
# Create a maintenance period on Zabbix with all the vms are running on Offsite and Offsite itself | # Create a maintenance period on Zabbix with all the vms are running on Offsite and Offsite itself | ||
# Make sure the maintenance is active (yellow icon) | |||
# Update the packages through terminal `apt update` and `apt upgrade` | # Update the packages through terminal `apt update` and `apt upgrade` | ||
# Make sure that the packages are removed, upgraded and installed correctly and check them | # Make sure that the packages are removed, upgraded and installed correctly and check them | ||
# Click the reboot button for | # Click the reboot button for Offsite in the web GUI | ||
# | # Make sure offsite is actually shutting down | ||
# Wait till it comes online again | # Wait till it comes online again | ||
# On Zabbix, go to 'Configuration' -> 'all the vms', and click on 'items' for the rebooted vms. | # On Zabbix, go to 'Configuration' -> 'all the vms', and click on 'items' for the rebooted vms. | ||