Understanding Availability Zones in VMware Installations

Page last updated:

Pivotal defines an Availability Zone (AZ) as an operator-assigned, functionally independent segment of network infrastructure. In cases of partial infrastructure failure, Pivotal Cloud Foundry (PCF) Elastic Runtime distributes and balances all instances of running applications across remaining AZs. Strategic use of Availability Zones contributes to the fault tolerance and high availability of a Elastic Runtime deployment.

Elastic Runtime on VMware vSphere supports distributing deployments across multiple AZs. See the section on AZs in Configuring Ops Manager Director for VMware vSphere.

It is recommended that customers use three Availability Zones to operate a highly available installation of Elastic Runtime.

Balancing Across AZs During Failure: Example Scenario

An operator scales an application to four instances in an Elastic Runtime environment distributed across three availability zones: A1, A2, and A3. The environment allocates the instances according to the Diego Auction.

Az er 1

If A1 experiences a power outage or hardware failure, the two application instances running in A1 terminate while the application instances in zones A2 and A3 continue to run:

Az er 2

If A1 remains unavailable, Elastic Runtime balances new instances of the application across the remaining availability zones:

Az er 3

Create a pull request or raise an issue on the source for this page in GitHub