VMware Tanzu Application Service for VMs [Windows] enables you to provision, operate, and manage Windows stemcells on Ops Manager.
After you install the TAS for VMs [Windows] tile on the Ops Manager Installation Dashboard, developers can push .NET apps to Windows Diego Cells using the Cloud Foundry Command Line Interface (cf CLI).
For the TAS for VMs [Windows] release notes, see VMware Tanzu Application Service for VMs [Windows] v2.11 Release Notes.
To install the TAS for VMs [Windows] tile, you must have:
Ops Manager v2.11 and VMware Tanzu Application Service for VMs v2.11 deployed to vSphere, Amazon Web Services (AWS), Google Cloud Platform (GCP), or Azure.
A Windows stemcell. For information about obtaining or creating a Windows stemcell, see Downloading or Creating Windows Stemcells.
The minimum resource requirements for each Windows Diego Cell are:
Disk size: 64 GB (100 GB recommended)
Memory: 16 GB
The following limitations affect Windows containers in TAS for VMs [Windows]:
Windows Server Core Containers are used in TAS for VMs [Windows]. The following are known Windows Server Container limitations:
TAS for VMs [Windows] has the following limitations:
TAS for VMs [Windows] can be installed in an environment with the NSX Container Plugin (NCP), but NCP cannot be used with Windows containers in TAS for VMs [Windows]. For more information about NCP, see What’s New in the VMware documentation.
Developers cannot push Docker or other OCI-compatible images to Windows Diego Cells.
Container-to-container networking is not available for Windows-hosted apps.
OpenStack is currently not supported for TAS for VMs [Windows]. Contact your VMware representative for information about OpenStack deployments.
SMB is supported, but Volume Services is not supported.
Due to Known Issue #244 in Windows Server OS, apps hosted on TAS for VMs [Windows] cannot route traffic when deployed with the IPsec. For more information, see Traffic to containers via NAT stops working when using IPsec to encrypt network connections on GitHub.