Here are the requirements for installing VMware Tanzu Application Service for VMs (TAS for VMs) on vSphere. For general resource requirements, see TAS for VMs resource 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 Tanzu Operations 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.
- Tanzu Operations 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 fails with a
power_on_vm error when BOSH attempts to create virtual machines (VMs).
- Deactivate 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 can deactivate 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 Setting Virtual Processors and Memory 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.
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 TKGI
- 3 hosts minimum for vSphere HA (4 hosts for vSphere VSAN)
- Shared storage (Such as iSCSI, NFS, and VSAN)
- 1 NSX Manager
- 3 NSX controllers
- 4 large edge VMs in a cluster
- Ops Manager: Tanzu Operations 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.