In this recipe, we are looking to upgrade a cluster. This recipe works for updates as well as upgrades.
This is a simple process that I will split in 3 parts. First execute the following steps and then continue with either Minor upgrades or Major upgrades:
If you are upgrading between minor versions, such as 7.0 and 7.0.1, where no hardware change was made, then follow this step:
Upgrade the next Orchestrator server until you have upgraded the whole cluster.
If you are upgrading between major versions, such as 5.x, 6.x, or 7.0 and 7.1, where hardware changes have been made, you should follow these steps:
As clustering changed between vRO 5, 6, 7, and 7.1, you need to be a bit more careful with the upgrade. That's why you need to bring down the whole cluster. This is especially true when the hardware has been changed:
Version |
5.5 and 6 |
7.0 |
7.1 |
Memory |
3 GB |
4 GB |
6 GB |
vCPU |
2 |
2 |
2 |
Hard disk |
7 + 5 GB |
7 + 5 GB |
7 + 10 GB |
If you are just updating a minor version, such as 7.0.1 to 7.0.2, you can try to upgrade the cluster hot. However, this could be problematic and should be tested for each minor upgrade before doing it in production.
Updating Orchestrator in Chapter 1, Installing and Configuring Orchestrator.