This topic describes upgrading VMware Tanzu Operations Manager (Ops Manager) and VMware Tanzu Application Service for VMs (TAS for VMs) to v2.10.
Breaking Changes: Read the Ops Manager v2.10 Release Notes, VMware Tanzu Application Service for VMs v2.10 Release Notes, Isolation Segment v2.10 Release Notes, and VMware Tanzu Application Service for VMs [Windows] v2.10 Release Notes, including the Breaking Changes and Known Issues sections, before starting the upgrade process.
The procedure below describes upgrading Ops Manager, TAS for VMs, and product tiles.
The apps in your deployment continue to run during the upgrade. However, you cannot write to your deployment or make changes to apps during the upgrade.
For details about how upgrading impacts individual TAS for VMs components, see What Happens During TAS for VMs Upgrades.
VMware recommends upgrading directly to Ops Manager v2.10 from Ops Manager v2.5 through v2.9. To upgrade Ops Manager to v2.10 from Ops Manager v2.5 through v2.9, see Jump Upgrade to Ops Manager v2.10 below. To upgrade both Ops Manager and TAS for VMs, see Task 1: Prepare to Upgrade below.
Jump upgrading describes the process of skipping minor versions when upgrading Ops Manager. Jump upgrading enables you to upgrade directly to the latest version of Ops Manager, which is v2.10. For more information, see Jump Upgrading to Ops Manager v2.10.
To jump upgrade to Ops Manager v2.10:
Review the prerequisites and breaking changes described in Jump Upgrading to Ops Manager v2.10.
Complete the steps to prepare Ops Manager, the BOSH Director, and BOSH-managed add-ons for upgrading in Upgrade Preparation Checklist for Ops Manager v2.10. Do not complete the steps to prepare TAS for VMs for upgrading.
Follow the procedure in this topic to upgrade Ops Manager, starting at Task 1: Prepare to Upgrade below. Do not complete the steps to upgrade TAS for VMs.
Although you can skip minor versions when upgrading Ops Manager, you should not skip minor versions when upgrading TAS for VMs. Skipping minor versions when upgrading TAS for VMs may result in additional breaking changes. To avoid this, upgrade TAS for VMs to the minor version that directly follows your current version of TAS for VMs.
If you are upgrading TAS for VMs to the next minor release:
Locate the version of Upgrade Preparation Checklist for Ops Manager that is specific to the minor release version to which you are upgrading and complete the steps that are specific to TAS for VMs.
For more information, see the versions of Configuring TAS for VMs for Upgrades in the TAS for VMs documentation and Upgrading TAS for VMs and Other Ops Manager Products that are specific to the minor release version to which you are upgrading.
If you have not already, complete the steps in Upgrade Preparation Checklist for Ops Manager v2.10.
The following sections describe how to upgrade Ops Manager and installed products to Ops Manager v2.10:
To import your Ops Manager installation to the Ops Manager v2.10 VM:
Download the Ops Manager VM Template v2.10 from the Ops Manager download page on VMware Tanzu Network.
Record the fully qualified domain name (FQDN) address of the existing Ops Manager VM.
To avoid conflicts, power off the existing Ops Manager VM.
Deploy the new Ops Manager VM by following the steps in one of these topics:
When redirected to the Welcome to Ops Manager page, select Import Existing Installation.
When prompted, enter the Decryption Passphrase for this Ops Manager installation. You set this passphrase during your initial installation of Ops Manager.
Note: If lost, the Decryption Passphrase cannot be recovered.
Click Choose File and browse to the installation ZIP file exported in the installation export step of your upgrade preparation. For more information, see Export Your Installation in Upgrade Preparation Checklist for Ops Manager v2.10.
Note: Some browsers do not provide feedback on the status of the import process, and might appear to hang.
A Successfully imported installation message appears upon completion.
Note: Ops Manager automatically imports the Telemetry for Ops Manager tile. This tile collects product usage data, which helps improve VMware products and services.
Using Telemetry for Ops Manager is optional and the tile does not share product usage data until you add and configure it. For more information, see the documentation for the Telemetry for Ops Manager tile.
After upgrading to Ops Manager v2.10, you must upgrade your product versions.
To upgrade your product versions:
Click IMPORT A PRODUCT to upload the product file.
Under IMPORT A BUTTON, click + next to tile. This adds the tile to your staging area.
Click the newly-added tile to review and save any configurable options.
(Optional) If you use other service tiles, you can upgrade them following the same procedure. For more information, see Upgrading TAS for VMs and Other Ops Manager Products.
Caution: If the installation fails or returns errors, contact Support. Do not attempt to roll back the upgrade by restarting the previous version's Ops Manager VM.
To perform your upgrade to Ops Manager v2.10:
Navigate to the Ops Manager Installation Dashboard.
Click Review Pending Changes, then Apply Changes. This immediately imports and applies upgrades to all tiles in a single transaction.
Click each service tile, select the Status tab, and confirm that all VMs appear and are in good health.
After confirming that the new installation functions correctly, remove the previous version’s Ops Manager VM.
The following sections describe how to monitor your Ops Manager foundation during the upgrade and troubleshoot issues:
You can monitor the progress of the upgrade by checking the status of the foundation at various locations.
VMware recommends live-monitoring your upgrade with Healthwatch, which captures, calculates, stores, visualizes, and alerts on platform metrics, including:
For more information, see the Healthwatch documentation.
If you are not using Healthwatch, you can do some or all of the following to monitor upgrade progress:
Use the BOSH CLI to check the status of a task, VM, or instance. For more information, see Check Status Using BOSH CLI below.
Check app availability.
Run cf CLI commands.
Check the availability of the Ops Manager UI.
If using a network-attached storage (NAS) server, check the server’s performance.
If on vSphere, check vSphere performance.
To check the status of a task:
bosh -e ALIAS task TASK-NUMBER
ALIASis your BOSH alias.
TASK-NUMBERis the number of the upgrade task you want to check.
To check the status of a VM:
bosh -e ALIAS vms --vitals
ALIAS is your BOSH alias.
To check the status of an instance:
bosh -e ALIAS instances --ps
ALIAS is your BOSH alias.
You can use the CF Diego Operator Toolkit (cfdot) to check Diego component instance count by current state. For more information, see the cfdot repository on GitHub.
You can periodically take snapshots of storage metrics. VMware recommends this if you have a large foundation and have experienced storage issues in the past.
If you encounter problems during upgrade:
This information helps determine the cause of upgrade issues.
The following sections describe how to prepare for use of your new environment, check its health status, and clean up after upgrading:
To log in to BOSH after upgrading Ops Manager, you must re-create your alias.
To re-create your alias using BOSH:
bosh alias-env ALIAS -e DIRECTOR-IP
ALIASis the BOSH alias you are re-creating.
DIRECTOR-IPis the IP address of your BOSH Director VM.
To install the version of the Cloud Foundry Command Line Interface (cf CLI) packaged with the TAS for VMs tile on VMware Tanzu Network:
Go to the VMware Tanzu Application Service for VMs download page on VMware Tanzu Network.
Click the CF CLI download button.
Unzip the cf CLI ZIP file containing compressed binaries for the cf CLI.
Follow the procedure in Install the cf CLI Using a Compressed Binary in Installing the cf CLI in the TAS for VMs documentation.
Check the health of your deployment to ensure that all jobs and processes are running as expected.
To check the health of your deployment:
Check the health of each BOSH deployment in your installation by running:
bosh -e ALIAS -d DEPLOYMENT-NAME instances --ps bosh -e ALIAS vms --vitals bosh -e ALIAS -d DEPLOYMENT-NAME cck --report
ALIASis your BOSH alias.
DEPLOYMENT-NAMEis the name of your BOSH deployment.
Push and horizontally scale a test app to test TAS for VMs performance.
If you are running TAS for VMs MySQL as a cluster, run the
mysql-diag tool to validate health of the cluster. For more information, see the BOSH CLI v2 instructions in Running mysql-diag in the TAS for VMs documentation.
If you added custom VM Type or Persistent Disk Type options, you must ensure that these values are correctly set and were not overwritten.
To check your custom resource settings:
Go to the Installation Dashboard and click the BOSH Director tile.
Select Resource Config.
Ensure that the values for VM Type and Persistent Disk Type are correct.
To clean up old stemcells, releases, orphaned disks, and other unused resources:
bosh -e ALIAS clean-up --all
ALIAS is the BOSH alias you are re-creating.
VMware recommends telling developers to restage any apps that use buildpacks that were updated as a part of this upgrade.
For more information about how developers can restage apps, see Restage Your App in Starting, Restarting, and Restaging Apps in the TAS for VMs documentation.