Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions docs/.custom_wordlist.txt
Original file line number Diff line number Diff line change
Expand Up @@ -6,11 +6,13 @@ CPUs
dev
echoless
ethernet
failover
Hyperkit
IPs
Junos
Kaspersky
misconfiguration
mysqldump
NIC
NICs
overallocate
Expand Down
2 changes: 1 addition & 1 deletion docs/.sphinx/.wordlist.txt
Original file line number Diff line number Diff line change
Expand Up @@ -61,4 +61,4 @@ UI
UUID
VM
webhook
YAML
YAML
10 changes: 10 additions & 0 deletions docs/explanation/availability-zones.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,10 @@
(explanation-availability-zones)=
# Understanding Zones

```{important}
It is important to note that availability zones are a simulation-only feature and do not deploy on actual physical zones. Multipass provides the capability to distribute instances across as many as three availability zones.
```

Multipass availability zones allow you to simulate fault injection at the level of availability zones. In real cloud environments, availability zones are separate datacenters with independent power, cooling, and networking components. By using Multipass availability zones, you can mimic this setup locally to test and improve the fault tolerance of your applications through simulated data redundancy and zone failures.

To conduct an experiment, you can make one or more zones unavailable. This action shuts down all running instances within those zones, enabling you to analyze the resilience of your applications
Loading