Difference between revisions of "Update 5.2"
(6 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
+ | == Generic information == | ||
+ | |||
+ | The whole update with restart usually takes less than 7 minutes. But it can take 10 to 15 minutes or even more, depending on the amount of data in your system, the network connection and the system i/o speed. We suggest to plan for that. | ||
+ | |||
== Starting the upgrade == | == Starting the upgrade == | ||
+ | |||
+ | === 1) Enable maintenance mode === | ||
+ | |||
+ | Please log-in to your web-administration and go to "Provider maintenance". Enable maintenance mode by clicking "Enable maintenance mode" on the upper left. | ||
+ | |||
+ | === 2) Do the update === | ||
+ | |||
To update your regify provider appliance, please log in via SSH (or PuTTY). | To update your regify provider appliance, please log in via SSH (or PuTTY). | ||
Line 10: | Line 21: | ||
Now select the first menu item "Check for updates". There is a huge list of packages. Use TAB to switch focus to "Yes" and press Enter to start the update. '''The update process can take 10 to 15 minutes or even more''', depending on the amount of data in your system and the speed of your machines. | Now select the first menu item "Check for updates". There is a huge list of packages. Use TAB to switch focus to "Yes" and press Enter to start the update. '''The update process can take 10 to 15 minutes or even more''', depending on the amount of data in your system and the speed of your machines. | ||
− | === Master-Slave-Replication === | + | ==== Notes about Cross-Master-Replication ==== |
+ | If you are running a redundant system in cross-master-replication, '''start with the appliance that is the currently active system''' (working the traffic). Upgrade the second appliance directly after you upgraded the active system. | ||
+ | |||
+ | ==== Notes about Master-Slave-Replication ==== | ||
If you are running a redundant system in master-slave-replication, '''start with the master system'''. Upgrade the slave directly after the master appliance. | If you are running a redundant system in master-slave-replication, '''start with the master system'''. Upgrade the slave directly after the master appliance. | ||
− | === | + | === 3) Disable maintenance mode === |
− | + | ||
+ | Now, please re-login to your web-administration and go to "Provider maintenance". Disable maintenance mode by clicking "Remove maintenance mode" on the upper left. | ||
== Finish with restart== | == Finish with restart== | ||
Line 24: | Line 39: | ||
shutdown -r now | shutdown -r now | ||
+ | |||
+ | '''NOTE:''' The shutdown can take a minute or even more. Please do not power off the machine during restart manually. | ||
== ToDo after upgrading == | == ToDo after upgrading == | ||
=== System in maintenance mode? === | === System in maintenance mode? === | ||
− | If you turned on maintenance mode before upgrade, the system will come up in maintenance mode after update. Please enter Administration and use "Provider maintenance" | + | If you turned on maintenance mode before upgrade, the system will come up in maintenance mode after update. Please enter Administration and use "Provider maintenance" dialog to restore operation. |
=== CSS modifications === | === CSS modifications === |
Latest revision as of 15:08, 25 March 2022
Contents
Generic information
The whole update with restart usually takes less than 7 minutes. But it can take 10 to 15 minutes or even more, depending on the amount of data in your system, the network connection and the system i/o speed. We suggest to plan for that.
Starting the upgrade
1) Enable maintenance mode
Please log-in to your web-administration and go to "Provider maintenance". Enable maintenance mode by clicking "Enable maintenance mode" on the upper left.
2) Do the update
To update your regify provider appliance, please log in via SSH (or PuTTY).
In case you log in with root account, you have to enter
providerConfig
to run the appliance menu.
Now select the first menu item "Check for updates". There is a huge list of packages. Use TAB to switch focus to "Yes" and press Enter to start the update. The update process can take 10 to 15 minutes or even more, depending on the amount of data in your system and the speed of your machines.
Notes about Cross-Master-Replication
If you are running a redundant system in cross-master-replication, start with the appliance that is the currently active system (working the traffic). Upgrade the second appliance directly after you upgraded the active system.
Notes about Master-Slave-Replication
If you are running a redundant system in master-slave-replication, start with the master system. Upgrade the slave directly after the master appliance.
3) Disable maintenance mode
Now, please re-login to your web-administration and go to "Provider maintenance". Disable maintenance mode by clicking "Remove maintenance mode" on the upper left.
Finish with restart
The update also updates the kernel of the system, so you need to make a restart after the update has finished. The upate will ask you for a restart and you should answer with YES.
NOTE: Logged in using SSH (PuTTY), you can restart the appliance using the appliance menu "Appliance..." -> "Other Settings..." -> "Reboot the appliance".
In case you log in with root account, you can also enter
shutdown -r now
NOTE: The shutdown can take a minute or even more. Please do not power off the machine during restart manually.
ToDo after upgrading
System in maintenance mode?
If you turned on maintenance mode before upgrade, the system will come up in maintenance mode after update. Please enter Administration and use "Provider maintenance" dialog to restore operation.
CSS modifications
Size and scaling
In order to respect the growing number of huge screens and better screen resolutions, we modified the CSS structure and especially the used sizing-units of the regify provider CSS. All units are now given in rem. Rem means relative to the root html element font size. By this, switching the font size for the html element will switch the whole scaling of all the dialogs and elements (more information).
As a side effect, you can simply zoom your pages by defining a different font size for the html element using _customized.css.
Thus, we recommend you to edit your CSS in _customized.css, especially for the logo, to also use rem or em units for sizing and positioning. Scale your webbrowser and make sure the logo scales correctly with the border elements.
Branding and Corporate Identity
If you changed the colors in general (eg all button colors), we recommend you to re-do using the current CSS template from the Provider Customization page. This is the fastest way to cover all elements and icons for a quick branding.
Images
We replaced most of the used icons and symbols by fonticons. Due to this, it is more easy to change colors and also it is good in all scalings. Please verify any images you changed by using _customized.css.
BubbleHelp
If you changed the BubbleHelp class, you very likely have to re-do your styling because the CSS has changed very much. Or remove your BubbleHelp modifications and stay with the default :-)
Check
Please log in to your web administration now and check for any problems or error messages.