This topic describes how to install VMware Tanzu Operations Manager (Ops Manager) on Microsoft Azure.
It includes resource requirements, prerequisites, instructions for installing Ops Manager on Azure, and additional resources.
You can install Ops Manager on Azure, Azure Government Cloud, or Azure Germany. For more information about Azure regions, see the Microsoft Azure documentation.
You can install Ops 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 you meet the requirements for TAS for VMs and the requirements specific to Azure before installing Ops Manager on Azure. For more information, see Requirements below.
This section lists the resource requirements for installing Ops Manager on Azure:
For TAS for VMs-specific resource requirements, see TAS for VMs Resource Requirements.
For Azure-specific resource requirements, see Azure Resource Requirements below.
The following are the minimum resource requirements for deploying an Ops Manager deployment with TAS for VMs on Azure:
An OS disk of 120 GB for the Ops Manager VM.
Note: Ops Manager v1.11 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 Ops Manager:
| VM Type | VM Count |
|---|---|
| F1s | 22 |
| F2s | 22 |
| DS1 v2 | 2 |
| DS11 v2 | 10 |
| DS12 v2 | 24 |
Note: If you are deploying a test or sandbox Ops 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 Ops 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 | ||
| Ops Manager | DS2 v2 | 1 | |
| F4s | 4 |
Note: 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 Ops Manager on an Azure region that does not support the above VM instance types, you must override the default VM sizes. For more information, see Overriding defaults with custom disk types in the Ops Manager API documentation. Changing the default VM sizes may increase the cost of your deployment.
Before installing Ops Manager on Azure, you must:
Install the Azure CLI v2.0. To install the Azure CLI for your operating system, see Preparing to Deploy Ops 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 Ops Manager domain.
Note: To deploy Ops Manager to a production environment, you must obtain a certificate from a certificate authority (CA). VMware recommends using a self-signed certificate generated by Ops Manager for development and testing purposes only.
Assign administrative rights to a domain for Ops 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.
Note: 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 repository on GitHub.
(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 in production deployments for BOSH Director and TAS for VMs. An external database must be configured to use the UTC timezone.
(Optional) Configure external user stores. When you deploy Ops Manager, 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.
To install Ops Manager on Azure, see Installing Ops Manager on Azure.
To install Ops Manager on Azure Government Cloud, see Configuring BOSH Director on Azure Government Cloud.
To install Ops Manager in Azure Germany, see Configuring BOSH Director on Azure Germany.
The following are additional resources related to installing Ops Manager on GCP:
For information about troubleshooting the Ops Manager on Azure install process, see Troubleshooting Ops Manager on Azure.
For production-level deployment options for Ops Manager on Azure, see Reference Architecture for Ops Manager on Azure.
For information about how to manage IaaS users and credentials in Azure, see the Azure security documentation.
For recommendations on how to create and scope Azure accounts for Ops Manager, see IaaS Permissions Guidelines.
For information about deleting an Ops Manager on Azure installation, see Deleting Ops Manager from Azure.
For information about upgrading Ops Manager on Azure, see Upgrading BOSH Director on Azure.
