We are happy to announce MAAS 2.6.0 alpha 1. This release introduces new and exciting features and UI improvements.
Deploying machines with multiple “default” gateways
Deploying machines in complex network scenarios, where you want traffic to go out through a different gateway other than the default gateway, requires machines to be configured with source routing. This ensures that any outgoing traffic for which there are no defined routes goes out through the same interface as the incoming traffic.
MAAS 2.6 now changes the default machine network configuration to take advantage of source routing.
New features & improvements
Multiple default gateways
Previous MAAS versions deployed machines with a single default gateway. This meant that if a machine was configured in multiple subnets with gateways (with or without any routes), all incoming traffic on a given gateway would go out through the default gateway instead of the intended gateway.
From MAAS 2.6, this behavior now changes as MAAS now leverages the use of netplan and source routing to configure multiple “default” gateways, ensuring that all outgoing traffic goes out through the correct gateway rather than always going out through the default gateway.
For example, in previous versions of MAAS if a machine was with two subnets (subnet1, subnet2), and using subnet1’s gateway as the default gateway, all traffic in subnet two to the outside world would go out through the default gateway. Instead, with the newer changes, all traffic in subnet2 will go out through subnet2’s gateway in case it needs to reach the outside world.
Ephemeral deployment for disk-less machines
In older versions, MAAS prevented machines without any attached disks to be deployed. As of 2.6, MAAS now allows deployment all diskless machines to be ephemerally deployed, by default, which simply runs the operating system in memory. This feature provides the ability to:
- Network interface configuration - MAAS will apply the network interface configuration on the ephemeral environment.
- Deployment customization via cloud-init (user-data) - MAAS will continue to allow users to provide user-data to customize their deployments.
- Reconfiguration on reboot - On reboot, an ephemerally deployed machined will re-run all configuration that was provided to cloud-init, including that provided by the user (user-data).
Please note that ephemeral deployments are limited in that:
- Ubuntu as the only ephemeral OS.
- Curtin preseeds are no longer applicable for deployment configuration.
- Storage is no longer configured.
Redfish power management
MAAS now adds the ability to power manage machines via Redfish, and has been tested against HP and Dell servers. Please note that most BMC’s continue to support IPMI alongside Redfish REST APIs for remote management of the BMC, as such a few considerations:
- If the machine is automatically enlisted, MAAS will default to discover/configure IPMI.
- If a machine has been switched to use Redfish, or created with the Redfish power driver, MAAS will always use this and won’t automatically switch back to IPMI.
- It allows defining a node ID in case the machine is inside a chassis management interface with multiple machines.
PXE over UUID
MAAS now supports legacy PXE booting over UUID. The MAAS commissioning process will now gather the machine’s UUID, which is also used for the PXE process over pxelinux. MAAS, by default, will now prefer to respond to PXE requests based on the UUID rather than the MAC address. This was originally added to start supporting s390x deployment.
Minor Performance improvements
As a result of a bugfix where MAAS was creating database records for interface links against null IP address, the UI performance has been increased. This underlying issue was causing load times of network elements in the UI. The fix has reduced the queries from 30s to 1s. This improves the perceived performance in large environments where there’s significant DHCP traffic.
Work in progress
Apart from the given features, MAAS has other various features that are being develop concurrently. These include:
Stats and metrics gathering
MAAS is adding support to start collecting metrics and stats about the environment and performance. This will all users to have more insight about usage and performance, as well as help developers use this data to futher improve performance.
ESXi - Storage support creating data stores
The current ESXi support only allows for configuring the installation of the ESXi image on a single disk. In 2.6, MAAS will support the ability to further configure storage by providing the ability to configure extra data stores for the VMs.
MAAS 2.6 introduces the ability to tag machines in bulk over the Web UI.
Clear discovered devices
The device discover page now has the ability to clear all discovered records, or clear individual ones.
Power actions in table (machine listing)
The machine listing page now includes an in-table dropdown action to execute power actions on the machine.
For other issues or bugs fixed in this release, please refer to:
sudo apt-add-repository ppa:maas/next sudo apt install maas