About images

MAAS provides supported images for stable Ubuntu releases, and for CentOS 6.6, CentOS 7, and CentOS 8.0 releases. Ubuntu Advantage is needed to build customer Windows, RHEL and ESXi images. This article will help you learn:

MAAS stores images in the region controller’s database, from where the rack controller proxies them to the individual machines. It’s important to note that for ESXi images, network configuration includes only these five parameters:

  1. DHCP
  2. Static/auto IP assignments
  3. Aliases
  4. VLANs
  5. Bonds

Bonds are mapped to NIC teaming in only three ways:

  1. balance-rr – portid
  2. active-backup – explicit
  3. 802.3ad – iphash, LACP rate and XMIT hash policy settings ignored

About boot sources and why they matter

The place from where a region controller downloads its images is known as a boot source. The main characteristics of a boot source are its location (URL) and its associated GPG public keyring.

A boot resource is another name for an image. So boot resources are found within a boot source.

MAAS comes configured with a boot source that should suffice for most users:


The above URL points to the ‘stable’ stream (for the v3 format). See Local image mirror for some explanation regarding the availability of other streams.

Although the backend supports multiple boot sources, MAAS itself uses a single source. If multiple sources are detected, the web UI will print a warning and will be unable to manage images.

The link “Local image mirror” works great here on discourse.maas.io but is broken on https:// maas.io/docs/about-images#heading--boot-sources

I’m sure this isn’t the only document where links appear to be broken on maas [dot] io but work on discourse [dot] maas [dot] io

(edit due to new users can only post 2 links and it thinks that mass [dot] io is a link)