Ops Manager v3.0 Release Notes

Page last updated:

This topic contains release notes for VMware Tanzu Operations Manager (Ops Manager) v3.0.

You can jump upgrade directly from previous versions of Ops Manager to Ops Manager v3.0. For more information, see Jump Upgrading to Ops Manager v3.0.

For the feature highlights of this release, see New Features in Ops Manager v3.0 below.

Ops Manager is certified by the Cloud Foundry Foundation for 2022.

For more information about the Cloud Foundry Certified Provider Program, see How Do I Become a Certified Provider? on the Cloud Foundry website.


Releases

v3.0.0

Release Date: November 15, 2022

Ops Manager v3.0.0 uses the following component versions:

Component Version
Tanzu Ops Manager3.0.0-build.158
Stemcell (Bosh Director and Ops Manager)1.44
BBR SDK1.18.57
BOSH Director276.1.0
BOSH DNS1.34.0
System Metrics2.2.2
CredHub2.12.13
CredHub Maestro8.0.7
Syslog12.0.6
Windows Syslog1.1.11
UAA74.5.58
BPM1.1.19
OS Conf22.1.2
AWS CPI95
Azure CPI41.0.0
Google CPI45.0.0
OpenStack CPI51
vSphere CPI87
BOSH CLI7.0.1
Credhub CLI2.9.8
BBR CLI1.9.38
Telemetry2.0.1

How to Upgrade

To upgrade to Ops Manager v3.0, see Upgrading Ops Manager.

New Features in Ops Manager v3.0

Ops Manager v3.0 includes the following major features:

Jammy Jellyfish Stemcell Support

Ops Manager v3.0 uses Jammy Jellyfish, a Jammy stemcell based on Ubuntu 22.04.

The previously-supported Xenial Xerus stemcells were based on Ubuntu 16.04. These stemcells are due to reach end of general support (EOGS) and stop receiving security updates in April 2024. You can still use Xenial stemcells in conjunction with tiles installed on Ops Manager v3.0 until they reach EOGS.

Ops Manager v3.0 allows tile authors to upgrade from Xenial stemcells to Jammy Jellyfish stemcells. This ensures that Ops Manager v3.0 users can maintain access to secure stemcells.

Review Pending Changes Page Includes Applied Runtime Configurations

The Review Pending Changes page for a tile includes a list of runtime configurations to be applied to that tile.

Tiles can use runtime configurations to influence the behavior of VMs that other tiles deploy. For example, when you activate the Enable additional System Metrics checkbox in the Director Config pane of the BOSH Director tile, the BOSH Director applies a runtime configuration to the VMs that VMware Tanzu Application Service for VMs (TAS for VMs) deploys that allows the BOSH Director to collect detailed metrics from TAS for VMs VMs.

Changes to a runtime configuration can cause longer deployment times when you re-deploy a tile. By reviewing the runtime configurations that are to be applied to tiles during re-deployment, you can determine in advance which tiles may take a longer time to re-deploy.

AWS Deployments Use 5th-Generation AMD Instances

Ops Manager v3.0 uses 5th-generation AMD instances for AWS deployments. 5th-generation AMD instances are more performant and cost-effective than previous instance types. Both Jammy Jellyfish stemcells and Xenial stemcells support 5th-generation AMD instances.

New installations of Ops Manager v3.0 use 5th-generation AMD instances by default. If you upgrade to Ops Manager v3.0 from Ops Manager v2.10 or earlier, you can either keep your current VM types or convert your VMs to 5th-generation AMD instances in the AWS Config pane of the BOSH Director tile. For more information, see Step 2: AWS Config Page in Configuring BOSH Director on AWS.

If you are using a custom instance type catalog, the VM types that you can use do not change.

The 5th-generation AMD instances are closer to the recommended default size for tiles. Because of this, product tiles in Ops Manager select VM types that are smaller than the previous sizes for their jobs. For example, Diego Cells select an instance type with 2 CPUs and 16 GB of RAM. When you convert your VMs to 5th-generation AMD instances, you may need to either scale up the number of Diego Cell instances or change the selected VM type of certain jobs to a larger VM type. You can configure both the number of instances and VM type of each job in the Resource Config pane of a product tile.

For more information about AWS Linux instance types, see the AWS documentation. For more information about AWS Windows instance types, see the AWS documentation.

AWS Deployments Use GP3 Disks

Ops Manager v3.0 uses gp3 disks for AWS deployments. gp3 disks are more performant and cost-effective than gp2 disks.

New installations of Ops Manager v3.0 use gp3 disks by default. If you upgrade to Ops Manager v3.0 from Ops Manager v2.10 or earlier, you can either keep your current disk types or convert your disks to gp3 in the AWS Config pane of the BOSH Director tile. For more information, see Step 2: AWS Config Page in Configuring BOSH Director on AWS.

GCP Deployments Use E2 Series Instances

Ops Manager v3.0 uses E2 Series instances for GCP deployments. E2 Series instances are more performant and cost-effective than previous instance types. Both Jammy Jellyfish stemcells and Xenial stemcells support 5th-generation AMD instances.

New installations of Ops Manager v3.0 use E2 Series instances by default. If you upgrade to Ops Manager v3.0 from Ops Manager v2.10 or earlier, you can either keep your current VM types or convert your VMs to E2 Series instances in the Google Config pane of the BOSH Director tile. For more information, see Step 2: Configure GCP Tile in Configuring BOSH Director on GCP.

If you are using a custom instance type catalog, the VM types that you can use do not change.

The E2 Series instances are closer to the recommended default size for tiles. Because of this, product tiles in Ops Manager select VM types that are smaller than the previous sizes for their jobs. For example, Diego Cells select an instance type with 2 CPUs and 16 GB of RAM. When you convert your VMs to E2 Series instances, you may need to either scale up the number of Diego Cell instances or change the selected VM type of certain jobs to a larger VM type. You can configure both the number of instances and VM type of each job in the Resource Config pane of a product tile.

For more information about GCP instance types, see the GCP documentation.

GCP Deployments Allow Machine Types in Custom VM Type Catalogs

Ops Manager v3.0 allows you to include machine types in your custom VM type catalogs for GCP deployments. When you configure VMs to use a specific machine type as their VM type, the BOSH Director creates VMs using that machine type, rather than creating a custom VM that matches the CPU and RAM specifications. This allows you to use specialized VM types that are not in the default Ops Manager VM type catalog.

If you do not specify a machine type as a custom VM type, the BOSH Director continues to create VMs that match the CPU and RAM specifications.

For more information, see the Ops Manager API documentation.

Breaking Changes in Ops Manager v3.0

Ops Manager v3.0 includes the following breaking changes:

BOSH System Metrics Server is Removed

The BOSH System Metrics Server is removed from Ops Manager v3.0.

If you upgrade to Ops Manager v3.0 from Ops Manager v2.10 or earlier, and you had previously configured the BOSH Director to activate the BOSH System Metrics Server, you must deactivate the Enable deprecated BOSH System Metrics Server checkbox and activate the Enable additional System Metrics checkbox in the Director Config pane of the BOSH Director tile before you begin upgrading. The Enable deprecated BOSH System Metrics Server checkbox is removed from the BOSH Director tile.

NSX-V Networking is Removed

NSX-V networking reached EOGS in January 2022. Because of this, you cannot configure NSX-V networking in Ops Manager v3.0.

You can still configure NSX-T networking for compatible vSphere deployments. For more information, see Resource Requirements in Installing Ops Manager on vSphere.

Keystone v2 Authentication is Removed

In OpenStack deployments, Keystone v2 is removed and replaced by Keystone v3 for user authentication.

If you upgrade to Ops Manager v3.0 from Ops Manager v2.10 or earlier, and you had previously used Keystone v2 to authenticate users, you must re-configure your OpenStack deployment to use Keystone v3 before you begin upgrading.

Multi-Network Configuration for the BOSH Director VM is Removed

Ops Manager v2.10 and earlier included an undocumented API endpoint that allowed you to configure a second network on the BOSH Director VM. In Ops Manager v3.0, this API endpoint is removed, and you can no longer configure a second network on the BOSH Director VM.

Azure Germany and Azure Stack Support is Removed

Microsoft ceased operating the Azure Germany cloud platform in 2021. Because of this, you cannot configure an Azure Germany environment in Ops Manager v3.0. However, you can still use Germany-based regions in the global Azure Commercial Cloud environment.

You also cannot configure an Azure Stack environment in Ops Manager v3.0.

Invalid Custom Syslog Rules Cause Errors

Iin Ops Manager v3.0, invalid custom syslog rules cause Ops Manager deployments to fail with a relevant error message. In Ops Manager v2.10 and earlier, invalid custom syslog rules only cause Ops Manager to log errors and discard the invalid rules.

To avoid deployment failure, validate your custom syslog configuration in one of the following ways:

  • As your syslog server is pre-starting, look for a Custom rule configuration invalid error message. This error message indicates that one or more of your custom syslog rules are invalid. You can then edit these custom rules accordingly in the Custom rsyslog Configuration field in the Syslog pane of the BOSH Director tile.

  • In a terminal window, run rsyslogd -N1 in a local environment.

Known Issues

There are no known issues for Ops Manager v3.0.