This article provides a very brief overview on upgrading existing vROps platforms to version 8.0 which is about to GA (at the time of writing). I’m not going into too much detail as there isn’t a huge amount different to any other version upgrade.
My environment that I am upgrading here is a single node 7.5 GA build which is also leverage an application remote collector. Here you can see my cluster is up and running albeit with not that many objects being collected.
This is where things deviate slightly. Normally an in-place upgrade of vROps consists of two parts. The first being the virtual appliance operating system and the second being the application itself.
With version 8.0 of vROps the operating system transitions from Suse Linux Enterprise Server to VMware Photon 3.0. Because of this there is only one in-place upgrade file, the vRealize_Operations_Manager-VA-8.0.0.xxxxxxxx.pak file.
Applying the file should never been done without first performing:
- Upgrade assessment using the appropriate version assessment pak file
- Taking snapshots of all cluster nodes
My environment is obviously not a production one so I am going to skip the assessment but I definitely have taken snapshots!
Applying the pak file should also include resetting the default content. This is really recommended so that any enhancements to thresholds and alert definitions that have been rolled into the new product version can be taken advantage of.
The upgrade will first be staged to all nodes, in my case just my single node. Note: in previous version (7.0 and prior) it was possible to stage pak files manually to nodes in advanced of an upgrade using the command line. At the time of writing there is no published process for doing this for upgrading to 8.0. If/when such a process appears I will update this article accordingly.
Applying the pak file is just a case of accepting the EULA and clicking next.
The cluster will go offline and nodes be restarted as part of the pak installation as you might expect. You should not restart anything manually during the upgrade process unless you want things to break and have to revert the snapshot(s).
Once the nodes come back online the admin page will look slightly different as there is now a “Continuous Availability” section. This can only be configured if you have an even number of cluster nodes! Check out my other article on vROps deployment architectures for more information.
You can verify the OS kernel change by running a “uname -a” on one of the vROps nodes. Here you can see my install is now running a Photon 3 based kernel.
Application Remote Collector
If you have been using the new telegraf agent functionality in vROps 7.5 provided by the “Application Remote Collector” appliance then you might think that this appliance (or appliances) has also been upgraded as part of this process. This is NOT the case.
The application remote collector will still be on version 7.5 as you can see here from my environment.
For this upgrade you need to go through a good old fashioned VAMI upgrade. Basically, log onto https://<your_appliance_fqdn>:5480 and run the upgrade from there using an update from over the wire or a mounted ISO.
Once this has finished your upgrade is complete. Remember to remove your snapshots once you are happy everything is as it should be!