What is new with MAAS
Here you will find release notes for:
We are happy to announced that MAAS 3.2.6 has been released. This point release of MAAS 3.2 provides a fix for a critical bug that prevented MAAS from enlisting machines on subnets with active DNS:
No other changes were made for this point release.
MAAS 3.2.5 was an attempt to fix a critical issue in 3.2.4. This issue was resolved in MAAS 3.2.6, listed above.
We are happy to announce that MAAS 3.2.4 has been released. This point release of MAAS 3.2 provides a fix for a critical bug that prevented the controllers page from displaying under certain conditions:
This release also addresses build issues found in prior point releases.
MAAS 3.2.2 and MAAS 3.2.3 were successive attempts to fix issues in MAAS. These issues were resolved in MAAS 3.2.4, listed above.
We are happy to announce that MAAS 3.2.1 has been released. This point release of MAAS 3.2.1 provides support for Rocky Linux UEFI (bug number 1955671), along with fixes for a number of recently-reported bugs:
- #1955671: support for rocky linux UEFI
- #1980436: MAAS CLI with anonymous access fails when TLS is enabled
- #1980490: MAAS regiond IPC crash due to a machine-resources binary crash when parsing some VPDs
- #1980818: Configure DHCP for VLAN
- #1981536: volume group creation fails on md device - MAAS 3.2
- #1981560: upgrade from 3.1 to 3.2 using debian packages missing steps
- #1982984: reverse-proxy service is not displayed for region controller
- #1929478: Commissioning fails with binary data in IPMI Lan_Conf_Security_Keys
- #1982208: agent.yaml.example is missing when maas is installed via deb package
- #1982846: Missing update_interface method on controller websocket handler
Please see the release notes for the 3.2 release, below, for a summary of 3.2 features.
We are happy to announce that MAAS 3.2 is now available.
MAAS 3.2 provides several new features, as well as the usual cadre of bug fixes.
As part of the MAAS 3.2 development effort, we have taken steps to improve the performance of machine listings. To date, we have measured the speed of listing a large number (100-1000) of machines via the REST API to be 32% faster, on average. During the next cycle, we will be actively working to improve MAAS performance for other operations (such as search).
MAAS has previously supported the Redfish protocol for some time, but as an option, preferring IPMI over all others if a choice of protocol was possible. In contrast, MAAS 3.2 supports Redfish as a BMC protocol by preferring Redfish over IPMI, provided that:
- The BMC has a Redfish Host Interface enabled
- That host interface can be accessed by the MAAS host
MAAS already supports Redfish, but with MAAS 3.2 we’re trying to auto-detect Redfish and use it if it’s available.
You may know that Redfish is an alternative to the IPMI protocol for connecting with machine BMCs. It provides additional features above and beyond those provided by IPMI. Eventually, Redfish should supplant IPMI as the default BMC interface.
If the machine uses either IPMI or Redfish for its BMC, the ephemeral environment will automatically detect it, create a separate user for MAAS and configure the machine, so that MAAS may check and control the machine’s power status. Note that the name of the user that MAAS creates in the BMC is controlled by the
maas_auto_ipmi_user config setting, both for IPMI and Redfish; nothing has changed in this regard with MAAS 3.2.
You can check whether or not a machine can communicate via Redfish, with the command:
dmidecode -t 42
If the machine has been enlisted by MAAS, you can also check the output of the
30-maas-01-bmc-config commissioning script to discover this.
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.
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.
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.
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.
MAAS 3.2 can be installed fresh from snaps (recommended) with:
sudo snap install --channel=3.2 maas
MAAS 3.2 can be installed from packages by adding the
sudo add-apt-repository ppa:maas/3.2 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.
Here is the breakdown of bugs fixed across the MAAS 3.2 release:
- MAAS 3.2.1
- MAAS 3.2
- MAAS 3.2 RC 2
- MAAS 3.2 RC 1
- MAAS 3.2 Beta 6
- MAAS 3.2 Beta 5
- MAAS 3.2 Beta 4
- MAAS 3.2 Beta 3
- MAAS 3.2 Beta 2
- MAAS 3.2 Beta 1
The following known issues exist for MAAS 3.2:
Cannot update controller/device tags via WebSocket API
If you attempt to update a list of tags of a device with an automatic tag, you get an error: “Cannot add tag tag-name to node because it has a definition”.
If you attempt to manually make the same API request, but send a list of tags with the automatic tag filtered out, the automatic tag will be removed from the device.
Here are release notes for other relatively recent MAAS versions: