MAAS 3.1 has been released. Find out what’s new in 3.1.

What is new with MAAS 3.2

We are happy to announce that MAAS 3.2 Beta 4 is now available.

New MAAS 3.2 features

MAAS 3.2 provides several new features, as well as the usual cadre of bug fixes.

MAAS native TLS

MAAS 3.2 provides native TLS. MAAS now has built-in TLS support for communicating with the UI and API over HTTPS. This eliminates the need to deploy a separate TLS-terminating reverse-proxy solution in front of MAAS to provide secure access to API and UI. Note that you can still set up an HA proxy if you are using multiple controllers.

Hardware sync for deployed machines

MAAS 3.2 allows you to sync hardware changes for deployed machines. You can see real-time updates to storage, etc., for a running machine. This feature requires a special parameter be set prior to deployment. Coupled with the existing ability to commission deployed machines, MAAS 3.2 moves a step closer to real-time reconfiguration of active, deployed, bare-metal.

Expanded tagging capability

MAAS 3.2 provides greatly expanded tagging capability. You can auto-apply tags to machines that match a custom XPath expression. Setting up an automatic tag lets you recognise special hardware characteristics and settings, e.g., the gpu passthrough.

More new features

MAAS 3.2 rounds out the feature set with a few more items:

  • Support for observability (O11y) in MAAS: MAAS now supports integration with FOSS Observability stacks.

  • Ability for user to specify IPMI cipher suite: You can explicitly select which cipher suite to use when interacting with a BMC.

  • Roll-out of our new tabbed Reader Adaptive Documentation (incremental across the release cycle): We’ve eliminated the top menus; each page now contains information for all versions, selectable by dropdowns above the relevant sections.

This is a Beta release, so you may encounter bugs and incomplete features. We strongly recommend that you take the necessary precautions, which include (but are not limited to) the following steps:

- Install Beta versions on a system specifically designated for testing; Beta is not recommended for production.
- Take a backup of any unrecoverable data on your test system prior to installing Beta versions.
- More specifically, if you use a system for testing MAAS releases, back up the MAAS database and any unique configuration files related to your use of MAAS prior to installing Beta versions.

Also, you should make sure that you are using the latest version of PostgreSQL. Here’s how you can upgrade that.

Essentially, expect that the Beta may not function properly under all conditions, possibly overwriting data and configuration information on the test machine. Beta versions usually behave fairly well, but be warned that across-the-board, error-free performance isn’t something we expect from Beta releases.

As you encounter failures, please take the time to file a bug or let us know your thoughts on the discourse user forum.

How to install MAAS 3.2

MAAS 3.2 can be installed fresh from snaps (recommended) with:

sudo snap install --channel=3.2/beta maas

MAAS 3.2 can be installed from packages by adding the ppa:maas/3.2-next PPA:

sudo add-apt-repository ppa:maas/3.2-next
sudo apt update
sudo apt install maas

You can then install MAAS 3.2 fresh (recommended) with:

sudo apt-get -y install maas

Or, if you prefer to upgrade, you can:

sudo apt upgrade maas

At this point, proceed with a normal installation.

Bugs fixed in MAAS 3.2

Here is the breakdown of bugs fixed across the MAAS 3.2 release:

Known issues for MAAS 3.2

Currently, there are no known issues associated with MAAS 3.2.0.

Last updated 7 days ago.