Pivotal Container Service v1.0

Deploying BOSH and Ops Manager to vSphere

Page last updated:

This topic provides instructions for deploying Ops Manager to VMware vSphere.

Note: With vSphere 6.5 and NSX-T 2.1, when initially deploying the Operations Manager OVF, you cannot connect directly to an NSX-T logical switch. You must first connect to a vSphere Standard (vSS) or vSphere Distributed Switch (vDS). A suggested approach is to connect to a VSS or VDS when deploying the OVF, but do not power the VM on. After the OVF deployment has completed, you can then connect the network interface to the appropriate NSX-T Logical switch and power the VM on to proceed with the install.

  1. In order for Kubernetes to create load balancers and attach persistent disks to pods, you must create a service account in vCenter with sufficient permissions. You can apply the default VMware Administrator System Role to the service account to achieve the appropriate permission level.

    For a full list of the permissions that BOSH requires in order to deploy Ops Manager, see vSphere Service Account Requirements. Apply the permissions from this list if you require a service account with minimal privileges.

  2. Refer to the known issues in the PCF Ops Manager Release v2.0 Release Notes before starting.

  3. Download the Pivotal Cloud Foundry (PCF) Ops Manager .ova file at Pivotal Network. Click the Pivotal Cloud Foundry region to access the PCF product page. Use the dropdown menu to select an Ops Manager release.

    Vm ops man

  4. Log into vCenter.

  5. Select the VM and Templates view.

    Vm template view

  6. Right click on your datacenter and select New Folder.

    New folder

  7. Name the folder pivotal_cf and select it.

    Folder name

  8. Select File > Deploy OVF Template.

    Deploy ova

  9. Select the .ova file and click Next.


  10. Review the product details and click Next.

  11. Accept the license agreement and click Next.

  12. Name the virtual machine and click Next.

    Vm name

    Note: The selected folder is the one you created.

  13. Select a vSphere cluster and click Next.

    Anchovy cluster

  14. If prompted, select a resource pool and click Next.

  15. If prompted, select a host and click Next.

    Note: Hardware virtualization must be off if your vSphere host does not support VT-X/EPT. Refer to the PCF on vSphere Requirements topic for more information.


  16. Select a storage destination and click Next.


  17. Select a disk format and click Next. For information about disk formats, see Provisioning a Virtual Disk on vSphere.

    Warning: Ops Manager v2.0 requires a Director VM with at least 8 GB memory.

    Disk format

  18. Select a network from the drop down list and click Next.


  19. Enter network information and passwords for the Ops Manager VM admin user.

    Vm admin

    Note: Record this network information. The IP Address will be the location of the Ops Manager interface.

  20. In the Admin Password field, enter a default password for the ubuntu user. If you do not enter a default password, your Ops Manager will not boot up.

    Admin login

  21. Click Next.

  22. Check the Power on after deployment checkbox and click Finish. Once the VM boots, the interface is available at the IP address you specified.

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

  23. 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 in the Installing Pivotal Cloud Foundry on vSphere topic.

Note: Ops Manager security features require you to create a fully qualified domain name to access Ops Manager during the initial configuration.

Next Steps

After you complete this procedure, follow the instructions in the Configuring Ops Manager Director on vSphere topic.

Create a pull request or raise an issue on the source for this page in GitHub