TAS for VMs on vSphere Requirements

Page last updated:

This topic describes requirements for installing VMware Tanzu Application Service for VMs (TAS for VMs) on vSphere.

General Requirements

The general requirements for deploying and managing a Ops Manager deployment with Ops Manager and VMware Tanzu Application Service for VMs (TAS for VMs) are:

  • A wildcard DNS record that points to your Gorouter or load balancer. Alternatively, you can use a service such as xip.io. For example, 203.0.113.0.xip.io.

    • TAS for VMs gives each app its own hostname in your app domain.
    • With a wildcard DNS record, every hostname in your domain resolves to the IP address of your Gorouter or load balancer, and you do not need to configure an A record for each app hostname. For example, if you create a DNS record *.example.com pointing to your load balancer or Gorouter, every app deployed to the example.com domain resolves to the IP address of your Gorouter.
  • At least one wildcard TLS certificate that matches the DNS record you set up above, *.example.com.

  • Sufficient IP allocation:

    • One static IP address for either HAProxy or one of your Gorouters.
    • One static IP address for each job in the Ops Manager tile. For a full list, see the Resource Config pane for each tile.
    • One static IP address for each job listed below:
      • Consul
      • NATS
      • File Storage
      • MySQL Proxy
      • MySQL Server
      • Backup Restore Node
      • HAProxy
      • Router
      • MySQL Monitor
      • Diego Brain
      • TCP Router
    • One IP for each VM instance created by the service.
    • An additional IP address for each compilation worker. The formula for total IPs needed is IPs needed = static IPs + VM instances + compilation workers.

      Note: VMware recommends that you allocate at least 36 dynamic IP addresses when deploying Ops Manager and TAS for VMs. BOSH requires additional dynamic IP addresses during installation to compile and deploy VMs, install TAS for VMs, and connect to services.

  • One or more NTP servers if not already provided by your IaaS.

  • (Recommended) A network without DHCP available for deploying the TAS for VMs VMs.

    Note: If you have DHCP, see Troubleshooting Guide for guidance on avoiding issues with your installation.

  • (Optional) External storage. When you deploy TAS for VMs, you can select internal file storage or external file storage, either network-accessible or IaaS-provided, as an option in the TAS for VMs tile. VMware recommends using external storage whenever possible. For more information about how file storage location affects platform performance and stability during upgrades, see Configure File Storage.

  • (Optional) External databases. When you deploy TAS for VMs, you can select internal or external databases for the BOSH Director and for TAS for VMs. VMware recommends using external databases in production deployments. An external database must be configured to use the UTC timezone.

  • (Optional) External user stores. When you deploy TAS for VMs, you can select a SAML user store for Ops Manager or a SAML or LDAP user store for TAS for VMs, to integrate existing user accounts.

  • The most recent version of the Cloud Foundry Command Line Interface (cf CLI).

 

vSphere Requirements

The following are requirements for installing TAS for VMs that are specific to vSphere.

Minimum Resource Requirements for Ops Manager Deployment with TAS for VMs

The following are the minimum resource requirements for maintaining a Ops Manager deployment with TAS for VMs on vSphere:

  • vSphere v7.0, v6.7, or v6.5
  • Disk space: 2 TB recommended
  • Memory: 120 GB
  • Two public IP addresses: One for TAS for VMs and one for Ops Manager
  • vCPU cores: 82
  • Overall CPU: 28 GHz
  • vSphere editions: Enterprise Plus or Platinum. These editions include Distributed Resource Scheduler (DRS), which is required by TAS for VMs.
  • Ops Manager must have HTTPS access to vCenter and ESX hosts on TCP port 443.
  • A configured vSphere cluster:
    • If you enable vSphere DRS (Distributed Resource Scheduler) for the cluster, you must set the Automation level to Partially automated or Fully automated. If you set the Automation level to Manual, the BOSH automated installation will fail with a power_on_vm error when BOSH attempts to create virtual machines (VMs).
    • Disable hardware virtualization if your vSphere hosts do not support VT-X/EPT. If you are unsure whether the VM hosts support VT-x/EPT, you should disable this setting. If you leave this setting enabled and the VM hosts do not support VT-x/EPT, then each VM requires manual intervention in vCenter to continue powering on without the Intel virtualized VT-x/EPT. Refer to the vCenter help topic at Configuring Virtual Machines > Setting Virtual Processors and Memory > Set Advanced Processor Options for more information.
  • If you configure an external load balancer, an HTTP keep-alive connection timeout greater than five seconds

Note: If you are deploying Ops Manager behind a firewall, see Preparing Your Firewall for Deploying Ops Manager.

Minimum Resource Requirements for Ops Manager Deployment with Small Footprint TAS for VMs

The following are the minimum resource requirements for maintaining a Ops Manager deployment with Small Footprint TAS for VMs on vSphere:

  • 1 vSphere cluster/1 AZ
  • 2 resource pools: 1 for NSX-T components and 1 for TAS for VMs or PKS
  • 3 hosts minimum for vSphere HA (4 hosts for vSphere VSAN)
  • Shared storage/VSAN
  • 1 NSX Manager
  • 3 NSX controllers
  • 4 large edge VMs in a cluster
  • Ops Manager: Ops Manager, the BOSH Director, and Small Footprint TAS for VMs

Instance Number and Scaling Requirements

By default, TAS for VMs deploys the number of VM instances required to run a highly available configuration of Ops Manager. If you are deploying a test or sandbox Ops Manager that does not require HA, then you can scale down the number of instances in your deployment.

For information about the number of instances required to run a minimal, non-HA Ops Manager deployment, see Scaling TAS for VMs.