# Placement policies and availability domains

This page describes spread placement policies and availability domains in
VMware solution on Google Cloud and explains how they map to VMware vSAN fault domains.

[Placement policies](https://docs.cloud.google.com/compute/docs/instances/placement-policies-overview.md.txt) let
you control the physical placement of your bare-metal Compute Engine instances
within a Google Cloud zone. When you apply a spread placement policy to your
bare-metal ESXi nodes, Google Cloud distributes the instances across
separate physical server racks, top-of-rack switches, and power distribution
units to improve resiliency against location-specific hardware or power
disruptions.

## Availability domains

In Compute Engine, an availability domain is a logical grouping of
compute and storage resources within a zone that provides physical failure
isolation:

- **Physical isolation**: Each availability domain maps to isolated, distinct hardware within a Google Cloud data center. Hardware maintenance or a rack-level failure in one availability domain doesn't affect instances in other availability domains.
- **Domain count**: You can configure between 1 and 8 availability domains within a single spread placement policy.
- **Node distribution**: When you create bare-metal nodes, you assign an availability domain to each node so that compute and vSAN storage capacity is distributed evenly across independent fault domains.

> [!WARNING]
> **Warning:** Changing the availability domain of a bare-metal instance after creation requires stopping and restarting the instance. Stopping a bare-metal instance erases all data stored on its local NVMe SSDs.

## Map availability domains to vSAN fault domains

Spread placement policies provide the physical foundation for VMware vSAN fault
domains in your VCF clusters.

> [!CAUTION]
> **Caution:** Nodes in a placement policy must belong to only one vSphere or VCF cluster to maintain a 1:1 mapping between Google Cloud availability domains and VMware vSAN fault domains. If you share nodes from a single placement policy across multiple clusters, you risk misaligned fault domain mappings, which can compromise vSAN data redundancy and failover behavior.

## Placement policy and availability domain best practices

When you configure placement policies and availability domains for your VCF
clusters, follow these best practices:

- **Use one placement policy per cluster**: Create a dedicated spread placement policy for each vSphere cluster in a zone. When you add new nodes to expand an existing cluster, assign them to that cluster's existing placement policy.
- **Configure 5 to 8 availability domains**: Specify 5 to 8 availability domains in your spread placement policy to accommodate cluster growth and RAID-5 or RAID-6 erasure coding policies.
- **Assign availability domains at creation time**: Select the specific availability domain for each node when you provision the instance, and spread nodes evenly across availability domains to prevent single-domain capacity bottlenecks during failover.
- **Align vSAN fault domains with availability domain numbers** : Use each node's assigned availability domain number (`1` through `8`) as its Fault Domain name when you configure vSAN fault domains in vCenter Server.

## What's next

- Explore the [Architecture overview](https://docs.cloud.google.com/vmware-engine/docs/vmware-solution/architecture.md.txt).
- Review cluster sizing guidelines in [About vSphere clusters](https://docs.cloud.google.com/vmware-engine/docs/vmware-solution/concepts-clusters.md.txt).
- Follow the step-by-step guide to [Deploy nodes and configure appliance networking by using the console](https://docs.cloud.google.com/vmware-engine/docs/vmware-solution/deploy.md.txt).
- Learn how to add and remove nodes in [Manage node capacity](https://docs.cloud.google.com/vmware-engine/docs/vmware-solution/capacity-management.md.txt).