Installing PCF on Azure
Page last updated:
This guide describes how to install Pivotal Cloud Foundry (PCF) on Azure.
To view production-level deployment options for PCF on Azure, see the Reference Architecture for Pivotal Cloud Foundry on Azure.
The following sections describe general requirements for running PCF and specific requirements for running PCF on Azure.
The following are general requirements for deploying and managing a PCF deployment with Ops Manager and Elastic Runtime:
(Recommended) Ability to create a wildcard DNS record to point to your router or load balancer. Alternatively, you can use a service such as xip.io. For example,
Elastic Runtime gives each application its own hostname in your app domain. With a wildcard DNS record, every hostname in your domain resolves to the IP address of your router 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.compointing to your router, every application deployed to the
example.comdomain resolves to the IP address of your router.
(Recommended) A network without DHCP available for deploying the Elastic Runtime VMs
Note: If you have DHCP, refer to the Troubleshooting Guide to avoid issues with your installation.
Sufficient IP allocation:
- One IP address for each VM instance
- An additional IP address for each instance that requires static IPs
- An additional IP address for each errand
- An additional IP address for each compilation worker:
IPs needed = VM instances + static IPs + errands + compilation workers
Note: BOSH requires that you allocate a sufficient number of additional dynamic IP addresses when configuring a reserved IP range during installation. BOSH uses these IPs during installation to compile and deploy VMs, install Elastic Runtime, and connect to services. We recommend that you allocate at least 36 dynamic IP addresses when deploying Ops Manager and Elastic Runtime.
The most recent version of the Cloud Foundry Command Line Interface (cf CLI)
One or more NTP servers if not already provided by your IaaS
The following are the minimum resource requirements for deploying a PCF deployment with Ops Manager and Elastic Runtime on Azure:
- 27 F1s
- 4 F2s
- 4 F4s
- 1 DS11v2
- 1 DS12v2
Note: Specific instance types are only supported in certain regions. See the Azure documentation for a complete list. If you are deploying PCF in a region that does not support the above instance types, see the Ops Manager API documentation atBy default, Elastic Runtime deploys the number of VM instances required to run a highly available configuration of PCF. If you are deploying a test or sandbox PCF 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 PCF deployment, see Scaling Elastic Runtime.
https://YOUR-OPS-MANAGER-FQDN/docs#overriding-defaults-with-custom-disk-typesfor instructions on how to override the default VM sizes. Changing the default VM sizes may increase the cost of your deployment.
An OS disk of 120 GB for the Ops Manager VM
Note: Ops Manager v1.11 requires a Director VM with at least 8 GB memory.
To deploy PCF on Azure, you must have the Azure CLI v2.0. For instructions on how to install the Azure CLI for your operating system, see Preparing to Deploy PCF on Azure.
Complete the following procedures to install PCF on Azure:
You can choose to deploy Ops Manager Director with an Azure Resource Manager (ARM) template, or manually:
Note: Azure Government Cloud is only supported in PCF 1.10 and later.
To deploy PCF on Azure Government Cloud, see the Deploying PCF on Azure Government Cloud topic.
Note: Azure Germany is only supported in PCF 1.10.1 and later.
To deploy PCF in Azure Germany, see the Deploying PCF in Azure Germany topic.
To troubleshoot known issues when deploying PCF on Azure, see the Troubleshooting PCF on Azure topic.
You can use the Azure Portal console to remove all the components of a PCF on Azure installation.
Upgrade your Ops Manager Director as part of the upgrade process documented in the Upgrading Pivotal Cloud Foundry topic.