Following on from MAAS 2.9, we are happy to announce that MAAS 3.0 Beta 1 has been released. This release provides some new features, along with critical bug fixes.
Call for testing
NOTE that this is currently a BETA release, so there will be bugs, instabilities, and missing or incomplete features. As such, we invite you to thoroughly test this release and provide feedback.
Installing Beta 1The Beta 1 can be installed via packages on Ubuntu 20.04 LTS by adding the `3.0-next` PPA:
sudo add-apt-repository ppa:maas/3.0-next sudo apt install maas
It can be also be installed as a snap with:
sudo snap install --channel=3.0/beta maas
Removing support for RSD pods
With the advent of MAAS 3.0, we are removing support for RSD pods. Registered pods and their machines will be removed by MAAS upon upgrading to MAAS 3.0.
PCI and USB devices are now modelled in MAAS
MAAS 3.0 models all PCI and USB devices detected during commissioning:
Existing machines will have to be recommissioned to have PCI and USB devices modelled
PCI and USB devices are shown in the UI and on the API using the node-devices endpoint
Node devices may be deleted on the API only
On the API using the allocate operation on the machines endpoint a machine may allocated by a device vendor_id, product_id, vendor_name, product_name, or commissioning_driver.
IBM Z DPM partition support
IBM Z14 and above mainframe partitions are supported in MAAS 3.0. Note that partitions must use HyperV sockets and properly-defined storage groups. IBM Z DPM Partitions can be added as a chassis, which allows you to add all partitions in an HMC at once.
MAAS 3.0 supports Proxmox as a power driver:
Only Proxmox VMs are supported
You may authenticate with Proxmox using a username and password or a username and API token
If an API token is used, it must be given permission to query, start and stop VMs.
Proxmox VMs can be added as a chassis; this allows you to add all VMs in Proxmox at once.
Note that proxmox support has also been back-ported to MAAS 2.9
LXD projects support
MAAS 3.0 supports the use of LXD projects:
LXD VM hosts registered in MAAS are now tied to a specific LXD project which MAAS uses to manage VMs
MAAS doesn’t create or manage machines for VMs in other projects
MAAS creates the specified project when the VM host is registered, if it doesn’t exist
All existing VMs in the specified project are commissioned on registration
Resource usage is reported at both project and global levels
PCI and USB device tabs in UI machine details
Tables for detected PCI and USB devices have been added to the machine details page for MAAS 3.0:
These tables include a new skeleton loading state while node devices are being fetched:
The user is prompted to commission the machine if no devices are detected.
Workload annotations have been added to the machine summary page in MAAS 3.0. These allow you to apply
owner_data to a machine and make it visible while the machine is in allocated or deployed state:
This data is cleared once the machine state changes to something other than “allocated” or “deployed.” The machine list can be filtered by these workload annotations. MAAS will warn you on the release page to remind you that workload annotations will be cleared upon releasing the machine.
Fixed status bar
In MAAS 3.0, a fixed status bar has been added to the bottom of the screen, which will always display the MAAS name and version on the left. The right side of the status bar is intended to show contextual data, depending on the UI panel currently displayed. For now, the only data shown is a “last commissioned” timestamp when the user is on a machine details page: