Ensure that you meet the following requirements and prerequisites before installing VMware Tanzu Operations Manager on Microsoft Azure.
You can install Tanzu Operations Manager on either Azure or Azure Government Cloud. For information about Azure regions, see the Azure documentation. For more information about Azure Government Cloud, see Configuring BOSH Director on Azure Government Cloud.
You can install Tanzu Operations Manager on Azure with the VMware Tanzu Application Service for VMs (TAS for VMs) runtime. There are resource requirements specific to both TAS for VMs and Azure. Ensure that you meet the requirements for TAS for VMs and the requirements specific to Azure before installing Tanzu Operations Manager on Azure. For more information, see Requirements.
This section lists the resource requirements for installing Tanzu Operations Manager on Azure.
For TAS for VMs-specific resource requirements, see TAS for VMs Resource Requirements.
The following are the minimum resource requirements for deploying a Tanzu Operations Manager deployment with TAS for VMs on Azure:
An OS disk of 120 GB for the Tanzu Operations Manager VM.
Tanzu Operations Manager v2.10 requires a BOSH Director VM with at least 8 GB memory.
A minimum of the following VM instance limits in your Azure account. The number of VMs required depends on the number of tiles and availability zones (AZs) you plan to deploy. The following VM guidelines apply to the TAS for VMs and Small Footprint TAS for VMs runtimes:
TAS for VMs: A new Azure deployment requires the following VMs for TAS for VMs and Tanzu Operations Manager:
VM Type | VM Count |
---|---|
F1s | 22 |
F2s | 22 |
DS1 v2 | 2 |
DS11 v2 | 10 |
DS12 v2 | 24 |
If you are deploying a test or sandbox Tanzu Operations Manager that does not require high availability, then you can scale down the number of VM instances in your deployment. For more information, see Scaling TAS for VMs.
Small Footprint TAS for VMs: A new Azure deployment requires the following VMs for Small Footprint TAS for VMs and Tanzu Operations Manager:
VM Type | VM Count | Notes | |
---|---|---|---|
Small Footprint TAS for VMs | DS11 v2 | 1 | |
DS12 v2 | 2 | ||
F2s | 0 | Add 1 to count if using HAProxy | |
F1s | 5 | ||
Tanzu Operations Manager | DS2 v2 | 1 | |
F4s | 4 |
Some VM instance types are only supported in certain Azure regions. For more information, see Products available by region in the Microsoft Azure documentation. To deploy Tanzu Operations Manager on an Azure region that does not support the preceding VM instance types, you must override the default VM sizes. For more information, see Overriding defaults with custom disk types in the Tanzu Operations Manager API documentation. Changing the default VM sizes might increase the cost of your deployment.
Before you install Tanzu Operations Manager on Azure, you must:
Install the Azure CLI. To install the Azure CLI for your operating system, see Preparing to Deploy Tanzu Operations Manager on Azure.
Configure sufficient IP allocation for TAS for VMs. For more information about IP allocation requirements, see TAS for VMs Resource Requirements.
Create an SSL certificate for your Tanzu Operations Manager domain.
To deploy Tanzu Operations Manager to a production environment, you must obtain a certificate from a certificate authority (CA). VMware recommends using a self-signed certificate generated by Tanzu Operations Manager for development and testing purposes only.
Assign administrative rights to a domain for Tanzu Operations Manager. You must be able to add wildcard records to this domain.
Create 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
. Then, create at least one wildcard TLS certificate that matches the DNS record you configured. With a wildcard DNS record, every hostname in your domain resolves to the IP address of your Gorouter or load balancer. For example, if you create a DNS record *.example.com
pointing to your Gorouter, every app deployed to the example.com
domain resolves to the IP address of your Gorouter.
Create one or more NTP servers, if the NTP servers are not already provided by your Azure project.
Install the most recent version of the Cloud Foundry Command Line Interface (cf CLI). For more information, see the Cloud Foundry Command Line Interface in the GitHub repository.
(Optional) Configure external storage. VMware recommends using external storage if possible. For more information about how file storage location affects platform performance and stability during upgrades, see Configure file storage in Configuring TAS for VMs for Upgrades.
(Optional) Configure external databases. VMware recommends using external databases for BOSH Director and TAS for VMs in production deployments. An external database must be configured to use the UTC timezone.
(Optional) Configure external user stores. When you deploy Tanzu Operations Manager, you can select a SAML user store for Tanzu Operations Manager or a SAML or LDAP user store for TAS for VMs, to integrate existing user accounts.
To install Tanzu Operations Manager on Azure, see Installing Tanzu Operations Manager on Azure.
To install Tanzu Operations Manager on Azure Government Cloud, see Configuring BOSH Director on Azure Government Cloud.
The following are additional resources related to installing Tanzu Operations Manager on Microsoft Azure: