Deploying Ops Manager on vSphere

This topic provides instructions for deploying VMware Tanzu Operations Manager (Ops Manager) to VMware vSphere.

The instructions in this topic are based on vSphere 6.5 using the vSphere Client (HTML5) interface.

Runtime Considerations

For security purposes, VMware requires a dedicated instance of Ops Manager for use with VMware Tanzu Kubernetes Grid Integrated Edition (TKGI).

Important: If you are installing TKGI on vSphere with NSX-T integration, follow the instructions in Deploying Ops Manager with NSX-T for TKGI instead of performing the steps described in this topic.

Prepare vSphere

1. Log into vCenter using the vSphere Client (HTML5).

2. Select the vSphere Datacenter where you are deploying Ops Manager.

3. Create one or more vSphere clusters. A vSphere cluster is a collection of ESXi hosts and associated virtual machines (VMs) with shared resources and a shared management interface. Follow the steps below to create a vSphere cluster:

   Note: For highly available, production-ready environments, you must create more than one cluster. For more information, see Compute and HA Considerations and Scaling and Capacity Management in _vSphere Reference Architecture_.

   1. Right-click the vSphere Datacenter object.

   2. Select New Cluster.

   3. Name the Cluster. For example, Cluster1.

   4. Select Turn ON vSphere DRS to enable DRS. Set DRS Automation to Partially Automated or Full Automated.

   5. Select Turn ON vSphere HA to enable vSphere HA.

4. If you created more than one vSphere cluster, configure shared storage for the clusters. You can allocate shared storage to the clusters using one of two common approaches: horizontal or vertical. For more information about configuring shared storage for clusters, see Storage Design in vSphere Reference Architecture.

   Caution: Failure to properly configure shared storage for vSphere clusters could result in downtime and unrecoverable loss of data.

5. Create a resource pool for the management components in your deployment. Resource pools are vSphere objects used to organize resources.

   Note: The management resource pool separates non-HA components such as BOSH Director. For example, if you deploy Ops Manager for use with TKGI, the TKGI management plane includes Ops Manager, BOSH Director, the TKGI control plane, and Harbor (optional).

   Follow the steps below to create a vSphere resource pool:

   1. Right-click the vSphere cluster object that you created.

   2. Select New Resource Pool.

   3. Name the resource pool. For example, RP-MGMT.

   4. Review the default CPU and Memory settings and adjust if necessary. This is not commonly needed.

   5. Click OK.

6. (Optional) If desired, create host groups within the clusters. For information about using host groups in vSphere, see Host Groups in vSphere.

   1. Select the Cluster where you want to create a host group.

   2. Select the Configure tab.

   3. Under Configuration, select VM/Host Groups.

   4. Click Add and configure the host group as follows:

      • Name: Enter a name for the host group.
      • Type: Select Host Group from the drop down.
      • Click Add and select the ESXi host(s) to include in the host group.
      • Click OK.

Deploy Ops Manager

Ops Manager for vSphere is provided as an OVA file. An OVA file is a template for a VM. To deploy Ops Manager on vSphere, you import the OVA file into your vSphere environment.

1. Download the Ops Manager for vSphere OVA file from VMware Tanzu Network. Use the Releases dropdown menu to select an Ops Manager release.

2. Right-click the management resource pool that you created and select Deploy OVF Template. Alternatively, from the vCenter menu, select Actions > Deploy OVF Template.

3. On the Select an OVF template screen, click Browse.

4. Select the Ops Manager OVA file that you downloaded and click Open.

5. Review the template selection and click Next.

6. On the Select a name and folder screen:

   • Enter a name for the Ops Manager virtual machine, or use the default name.
   • Select the object labeled Datacenter.
   • Click Next.

   

7. On the Select a compute resource screen, select the compute resource where the Ops Manager VM will run, and click Next. Select the Resource Pool for the management components.

   

   Note: Hardware virtualization must be turned off if your vSphere host does not support VT-X/EPT. Refer to vSphere Requirements in Ops Manager on vSphere Requirements for more information.

8. On the Review Details screen, confirm the configuration up to this point, and click Next.

9. At the Select Storage screen, select the virtual disk format.

   1. Choose a Datastore.

      • If you use vSAN, select the vSAN datastore and apply the default storage policy.
      • If you use a dedicated disk, select the appropriate disk format for your deployment needs. The default type is Thin Provision, but you can choose to use a thick provisioned disk such as Thick Provisioned Lazy Zeroed. For more information, see vSphere Virtual Disk Types.

   2. Click Next.

      Caution: Ops Manager requires a VM with at least 8 GB memory.

      

10. On the Select Networks screen, either select the default VM Network, or ideally, create an Infrastructure Network, and click Next.

    

11. On the Customize template screen, enter the following information, and click Next.

    • IP Address: The IP address of the Ops Manager network interface. For example, 10.0.0.2.
    • Netmask: The network mask for Ops Manager. For example, 255.255.255.0.
    • Default Gateway: The default gateway for Ops Manager to use. For example, 10.0.0.1.
    • DNS: One or more DNS servers for the Ops Manager VM to use. For example, 10.20.20.1.
    • NTP Servers: The IP address of one or more NTP servers for Ops Manager. For example, 10.113.60.176.
    • Public SSH Key: Enter pre-existing public SSH key value to allow SSH access to the Ops Manager VM. Enter the full key in the ssh-rsa AAA... format.

      Important: You cannot deploy Ops Manager successfully without adding a public key. If you do not add a key, Ops Manager shuts down automatically because it cannot find a key and may enter a reboot loop.

    • Custom hostname: The hostname for the Ops Manager VM. For example, ops-manager.

12. On the Ready to complete screen, review the configuration settings and click Finish.

    This action begins the OVA import and deployment process.

13. Use the Recent Tasks panel at the bottom of the vCenter dashboard to check the progress of the OVA import and deployment.
    
    If the import or deployment is unsuccessful, check the configuration for errors. Fix any errors and restart the deployment process.

Start Ops Manager

1. Create a DNS entry for the IP address that you used for Ops Manager. You must use this fully qualified domain name when you log into Ops Manager.

   Note: Ops Manager security features require you to create a fully qualified domain name to access Ops Manager during the initial configuration. For more information, see Ops Manager on vSphere Requirements.

2. Select the Ops Manager VM and click Actions > Power > Power On.

   Once the VM boots, the Ops Manager web interface is available at the IP address that you specified.

   Note: It is normal to experience a brief delay before the interface is accessible while the web server and VM start.

3. Navigate to the fully qualified domain of your Ops Manager in a web browser.

Next Steps

After you complete this procedure, follow the instructions in Configuring BOSH Director on vSphere.