Skip to content

docs: document availability zones - #5127

Open
joelle-a-dev wants to merge 1 commit into
canonical:mainfrom
joelle-a-dev:docs/availability-zones
Open

docs: document availability zones#5127
joelle-a-dev wants to merge 1 commit into
canonical:mainfrom
joelle-a-dev:docs/availability-zones

Conversation

@joelle-a-dev

@joelle-a-dev joelle-a-dev commented Aug 7, 2026

Copy link
Copy Markdown

Summary

Availability zones are a fully implemented feature (zones, enable-zones, disable-zones commands, launch --zone, the Zone field in info/list, and the Unavailable instance state) but had no documentation at all.

  • Add reference pages for zones, enable-zones, and disable-zones
  • Document --zone on launch, and fix the sample launch output (was missing in <zone>)
  • Add an explanation page for the availability zone concept (default zones, per-zone subnets, automatic round-robin assignment, disable/enable semantics)
  • Add the Unavailable instance state, missing from instance-states.md
  • Add a how-to guide: list zones → launch into one → simulate an outage → recover
  • Cross-link from list.md/info.md, and document the Zone column that list already prints by default

Closes #5118

Test plan

  • Built the docs locally with Sphinx (pip install -r docs/requirements.txt && sphinx-build -b html docs /tmp/build) — completes with zero warnings or errors (aside from expected "Git clone too shallow" notices from a shallow local clone)
  • Verified all new pages appear in the rendered output and are wired into their toctrees
  • Cross-checked all documented command options, output formats (table/json/yaml/csv), and error messages directly against the CLI/daemon source (src/client/cli/cmd/{zones,enable_zones,disable_zones,launch}.cpp, the formatter implementations, and src/daemon/daemon.cpp)
  • Not verified against a live build of multipassd (not built in this environment), would appreciate a maintainer sanity check of the transcribed --help output blocks

Availability zones (default zone1/zone2/zone3, per-zone subnets,
automatic round-robin assignment at launch, and the enable-zones/
disable-zones commands for simulating a cloud outage) were fully
implemented but entirely undocumented.

- Add reference pages for the zones, enable-zones, and disable-zones
  commands
- Document the --zone option on launch, and fix the sample launch
  output which was missing "in <zone>"
- Add an explanation page describing the concept
- Add the Unavailable instance state, which was missing from
  instance-states.md
- Add a how-to guide walking through listing zones, launching into
  one, and disabling/re-enabling a zone
- Cross-link from list.md and info.md, and add the Zone column that
  list already prints by default but wasn't documented

Closes canonical#5118
@joelle-a-dev
joelle-a-dev marked this pull request as ready for review August 7, 2026 21:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Availability Zones needs to be documented

1 participant