Installing Pivotal Cloud Foundry 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
The following are the minimum resource requirements for maintaining a PCF deployment with Ops Manager and Elastic Runtime on Azure:
- 27 F1s
- 4 F2s
- 4 F4s
- 1 DS11v2
- 1 DS12v2
Note: The F-series is not supported in North Central US, East Asia, Japan East, Australia East, and Australia Southeast. The DSv2-series is not supported in East Asia. If you are deploying PCF in one of these regions, see the Ops Manager API documentation for 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
An Azure subscription that can accommodate a public IP address for each VM
Note: By default, Azure sets an upper limit of 60 public IP addresses. Depending on the size of your deployment, you may need to increase this limit by submitting an Azure support ticket. For more information, see the Azure documentation.
To deploy PCF on Azure, you must have the Azure CLI v0.10.5 or higher. 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:
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.