Availability Zones in vSphere

Page last updated:

Warning: Pivotal Cloud Foundry (PCF) v2.4 is no longer supported because it has reached the End of General Support (EOGS) phase as defined by the Support Lifecycle Policy. To stay up to date with the latest software and security updates, upgrade to a supported version.

This topic describes availability zones (AZs) in vSphere and an example of how an operator might scale an app across AZs.

Overview

Pivotal defines an AZ as an operator-assigned, functionally-independent segment of network infrastructure. In cases of partial infrastructure failure, a tile distributes and balances all instances of running apps across remaining AZs. Strategic use of Availability Zones contributes to the fault tolerance and high availability of a tile deployment.

vSphere supports distributing deployments across multiple AZs. For more information, see Step 4: Create Availability Zones in Configuring BOSH Director on vSphere.

It is recommended that customers use three Availability Zones to operate a highly available tile deployment.

Balancing Across AZs During Failure: Example Scenario

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

For a visual representation of this scenario, see the following diagram:

A teal box at the top of the diagram labeled 'Your Runtime' spans the width of the diagram. Three boxes are in a row underneath, labeled A1, A2, and A3. A1 contains two boxes labeled 'App Instance,' while A2 and A3 contain only one.

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

For a visual representation of this scenario, see the following diagram:

This diagram is the same as the diagram as above but with the following differences: The A1 box is depicted as terminated with a red 'X' covering the box. Two arrows each connect from the 'Your Runtime' box to the 'A2' box and the 'A3' box to show that A2 and A3 continue to run.

If A1 remains unavailable, the tile balances new instances of the app across the remaining availability zones.

For a visual representation of this scenario, see the following diagram:

This diagram is the same as the diagram as above but with the following differences: The A1 box, which originally had two app instances, has no app instances. A2 and A3 have each have one additional app instance.