This chapter describes how to perform maintenance on ZStack management nodes (MNs).
ZStack provides high availability (HA) for multiple management nodes (MNs, also known as hosts) by using separate HA suites. When any one of the MNs is disconnected, the HA will be triggered in seconds to ensure the business continuity.
HA mechanism: In a multi-MN model, each MN runs a zsha2 HA process. This process monitors the key services, including the MN service, UI service, and database service, in each MN in real time. When any key service is down, the system immediately triggers virtual IP (VIP) migration through Keepalived, and then attempts to restore the downtime service.
This topic provides an example of a dual-MN HA scenario to describe the procedures for installation, deployment, and upgrade. This topic also provides some considerations for using multi-MN HA. For more information, see the Multi-MN HA Tutorial.
After you obtain the new version of the HA suite, you can use it to upgrade the current zsha2 service.
[root@localhost ~]# ./zsha2 upgrade-ha
In the dual-MN HA scenario, you need to upgrade the HA suite before you can upgrade a MN.
[root@localhost ~]# zsha2 upgrade-mn -peerpass password ./ZStack-installer-3.10.0.bin
[root@localhost ~]# zsha2 upgrade-mn -peerpass password ./ZStack-x86_64-DVD-3.10.0-c76.iso
-peerpass
parameter is optional. You can set a password for SSH login to the peer MN.Back to Top
Email Us
contact@zstack.ioEmail Us
contact@zstack.ioEmail Us
contact@zstack.ioThe download link is sent to your email address.
If you don't see it, check your spam folder, subscription folder, or AD folder. After receiving the email, click the URL to download the documentation.Thank you for using ZStack products and services.
Submit successfully.
We'll connect soon.Thank you for using ZStack products and services.