Installing Ops Manager on vSphere

Page last updated:

This guide describes how to install Ops Manager on vSphere.

If you experience a problem while following the steps below, see Diagnosing Deployment Problems or the Known Issues sections of the following topics:

• Ops Manager v2.9 Release Notes in the Ops Manager documentation

• VMware Tanzu Application Service for VMs v2.9 Release Notes in the TAS for VMs documentation

• Isolation Segment v2.9 Release Notes in the TAS for VMs documentation

• VMware Tanzu Application Service for VMs [Windows] v2.9 Release Notes in the TAS for VMs [Windows] documentation

• Release Notes in the TKGI documentation

Requirements

This section describes the resource requirements for installing Ops Manager.

Note: If you are using the Cisco Nexus 1000v Switch, see the Using the Cisco Nexus 1000v Switch with Ops Manager for more information.

Note: When installing Ops Manager on a vSphere environment with multiple ESXi hosts, you must use network-attached or shared storage devices. Local storage devices do not support sharing across multiple ESXi hosts.

Resource Requirements

You can install Ops Manager with one of two runtimes. For more information about the requirements for each runtime, see the following:

• VMware Tanzu Application Service for VMs (TAS for VMs): TAS for VMs on vSphere Requirements. For information requirements when deploying with NSX-T, see the Requirements section of Deploying TAS for VMs with NSX-T Networking.
• VMware Tanzu Kubernetes Grid Integrated Edition (TKGI):
  • Without NSX-T: vSphere Prerequisites and Resource Requirements
  • With NSX-T: See the Preparing to Install TKGI on vSphere with NSX-T section of Installing TKGI on vSphere with NSX-T Data Center.

vSphere Service Account Requirements

Ops Manager requires read/write permissions to the data center level of the vSphere Inventory Hierarchy to successfully install. VMware recommends defining a custom role for the service account that has all privileges for all objects in the data center, including propagating privileges to children.

Since Ops Manager passes all required credentials through to BOSH, you only need one service account with the required vSphere privileges to complete the installation. Setting up separate service accounts for Ops Manager and BOSH is not necessary or recommended.

For more information about service account requirements, see the following topics:

• TAS for VMs: vSphere Service Account Requirements
• TKGI: Create the BOSH/Ops Manager Service Account in Preparing vSphere Before Deploying TKGI

Note: You can also apply the default VMware Administrator System Role to the service account to achieve the appropriate permission level.

vSphere Security Documents

• vSphere Security guide (PDF)
  This guide contains best practices for securing and managing a vSphere installation.

Procedure

This section describes the steps for installing Ops Manager.

Step 1: Install Ops Manager

Complete the following procedures to install Ops Manager on vSphere:

1. Deploying Ops Manager to vSphere

2. Configuring BOSH Director on vSphere

Additional Configuration

See the following topics for additional configuration options:

• Provisioning a Virtual Disk in vSphere
• Using the BOSH Resurrector
• Availability Zones in vSphere

Next Steps

After completing the procedures above, configure a runtime.

For information about installing and configuring a runtime, see the following:

• TAS for VMs:
  • Without NSX-T: Configuring TAS for VMs
  • With NSX-T: Deploying TAS for VMs with NSX-T Networking

    Note: You must install the NSX-T tile before you install or Upgrade the TAS for VMs tile.

• TKGI:
  • Without NSX-T: Installing TKGI
  • With NSX-T: Deploying NSX-T for TKGI
• Installing and Configuring TAS for VMs on Windows
• Installing Small Footprint TAS for VMs