Machine network configuration is now handled by cloud-init.
With previous versions of MAAS (and curtin), network configuration was performed directly by curtin during the installation process. In an effort to improve robustness, this network configuration has been consolidated with cloud-init.
MAAS continues to pass network configuration to curtin which in turn delegates the configuration to cloud-init.
To reduce the number of dependencies and improve reliability, MAAS ephemeral (network boot) images are no longer loaded using iSCSI (tgt). By default, these images are now obtained using HTTP requests to the rack controller.
After upgrading to MAAS 2.3, please ensure you have the latest available images. For more information please refer to Ephemeral images now use HTTP below.
MAAS 2.3 now supports the ability to perform network configuration for CentOS and Windows via cloud-init. The MAAS CentOS images now use the latest available version of cloud-init to support these features.
MAAS now performs machine network configuration for CentOS 6 and 7, providing those operating systems with networking feature parity with Ubuntu.
The following can now be configured for MAAS deployed CentOS images:
- Bonds, VLAN and bridge interfaces.
- Static network configuration.
Our thanks to the cloud-init team for improving the network configuration support for CentOS.
MAAS can now configure NIC teaming (bonding) and VLAN interfaces for Windows deployments. This uses the native NetLBFO in Windows 2008+.
Contact us for more information.
MAAS 2.3 introduces a new hardware testing framework that significantly improves the granularity and provision of hardware testing feedback. These improvements include:
- Run individual tests. The new framework allows MAAS to run each component individually. This enables MAAS to run tests against storage devices, for example, and capture results separately.
- Define a custom testing script with a YAML definition.
The ability to describe custom hardware tests with a YAML definition enables
MAAS do the following:
- Collate details about the tests, such as script name, description, required packages, and other metadata about what information the script will gather. All of which will be used by MAAS to render in the UI.
- Determine whether the test supports a parameter, such as storage, that lets the test to be run against individual storage devices.
- The option to run tests in parallel.
- Performance metrics. Capture performance metrics for the tests that can provide them:
- Failed testing override. The ability to override a machine that has been marked ‘Failed testing’. This allows administrators to acknowledge that a machine is usable despite it having failed testing.
Hardware testing improvements include the following web UI changes:
- Machine Listing page:
- Displays whether a test is pending, running or failed for the machine components (CPU, Memory or Storage.)
- Displays whether a test not related to CPU, Memory or Storage has failed.
- Displays a warning when the machine has been overridden and has failed tests but is in a ‘Ready’ or ‘Deployed’ state.
- Machine Details page:
- The Summary tab now provides hardware testing information about the different components (CPU, Memory, Storage).
- The Hardware Tests /Commission tab now displays an improved view of the latest test run, its run time as well as an improved view of previous results. It also adds more detailed information about specific tests, such as status, exit code, tags, runtime and logs/output (such as stdout and stderr).
- The Storage tab now displays the status of specific disks, including whether a test is OK or failed after running hardware tests.
For more information, please refer to https://docs.ubuntu.com/maas/2.3/en/nodes-hw-testing
In order to confirm network connectivity and aide with the discovery of VLANs, fabrics and subnets, MAAS 2.3 introduces network beaconing.
MAAS now sends out encrypted beacons to facilitate network discovery and monitoring. Beacons are sent using IPv4 and IPv6 multicast (and unicast) to UDP port 5240.
When registering a new controller, MAAS uses the information gathered from the beaconing protocol to ensure that newly registered interfaces on each controller are associated with existing known networks in MAAS.
Using network beaconing, MAAS can better correlate which networks are connected to its controllers, even if interfaces on those controllers are not configured with IP addresses.
Future uses for beaconing could include validation of networks from commissioning nodes, MTU verification and a better user experience when registering new controllers.
MAAS 2.3 enables an upstream HTTP proxy to allow MAAS-deployed machines to continue to use a caching proxy for repositories. This provides greater flexibility for closed environments, including:
- Enabling MAAS itself to use a corporate proxy while allowing machines to continue to use the MAAS proxy.
- Allowing machines that don’t have access to a corporate proxy to gain network access using the MAAS proxy.
Upstream proxy support includes an improved configuration pane on the settings page. See Settings > Proxy for more details.
Historically, MAAS used tgt to provide images over iSCSI for the ephemeral environments (such as during commissioning, the deployment environment and rescue mode). MAAS 2.3 changes the default behaviour by now providing images over HTTP instead.
This change means that initrd (run via PXE) will contact the rack controller to download the image to load in the ephemeral environment directly.
Support for using 'tgt' is being phased out in MAAS 2.3 and will no longer be supported from MAAS 2.4 onwards.
Users who would like to continue to use and load their ephemeral images via 'tgt' they can disable http boot with the following command.
maas $PROFILE maas set-config name=http_boot value=False
Alongside the UI improvements outlined above, MAAS 2.3 introduces an improved web UI design for the machines, devices and controllers detail pages that include the following changes:
- Summary tab. Now only displays details on a specific node (machine, device or controller), organised across cards.
- Configuration. This includes all editable settings for the specific node (machine, device or controllers).
The MAAS web UI now displays the version of each running controller and notifies the users of any version mismatch between the region and rack controllers.
This helps administrators identify potential problems when upgrading MAAS on a multi-node MAAS cluster, such as within a HA setup.
- Added DHCP status column on the Subnets tab.
- Added architecture filters
- VLAN and Space details page no longer allows inline editing.
- VLAN page adds the IP ranges tables.
- Zones page converted to AngularJS (away from YUI).
- New warnings when changing a subnet’s mode (Unmanaged or Managed).
- Renamed Device Discovery to Network Discovery.
- When MAAS cannot determine the hostname for discovered devices, it will show the hostname as 'unknown' and greyed-out rather than using the MAC address manufacturer as the hostname.
MAAS 2.3 can now automatically deploy rack controllers when deploying a machine.
This is accomplished by providing cloud-init user data. Cloud-init will install and configure the rack controller after a machine has been deployed. Upon rack controller registration, MAAS will automatically detect whether the machine is a rack controller and process the transition automatically.
To deploy a rack controller, users can do so via the API (or CLI), e.g:
maas $PROFILE machine deploy $SYSTEM_ID install_rackd=True
Note: This features makes use of the MAAS snap to configure the rack controller on the deployed machine. 'snap store' mirrors are not yet available, which means the machine will need access to the internet.
This release includes various improvements to the DNS reload mechanism, allowing MAAS to be smarter about when to reload DNS after changes have been automatically detected or made.
The machines API endpoint now provide more information on configured storage and provides additional output that includes volume_groups, raids, cache_sets, and bcaches fields.
MAAS 2.3 now supports the latest Django LTS version, Django 1.11. This allows MAAS to work with the newer Django version in Ubuntu Artful, which serves as a preparation for the next Ubuntu LTS release.
- Users running MAAS in Ubuntu Artful will use Django 1.11.
- Users running MAAS in Ubuntu Xenial will continue to use Django 1.9.
For issues fixed in MAAS 2.3, please refer to the following milestone:
For more information on previous bug fixes across 2.3, please refer to the following milestones:
The MAAS team is excited to announce the support for the Intel Rack Scale Design (RSD). Intel Rack Scale Design (RSD) is a hardware architecture that allows for the dynamic composition of physical systems from a pool of available hardware resources.
MAAS, as a cloud-like, scale-out bare-metal provisioning system, will leverage the use of Intel RSD to compose (create) and provision systems. With the support for RSD, MAAS introduces the ability to manually or dynamically compose (create) new machines from an available pool of resources. It will allow administrators to request machines with specific resources on demand and be able to deploy their workloads on them.
The definition of spaces has changed from a Layer 3 concept to a Layer 2 concept.
The spaces definition in MAAS (first introduced in MAAS 1.9) is "a set of subnets that can mutually communicate". The assumption is that these spaces can route to each other, and have appropriate firewall rules for their purposes. (For example, a "dmz" space might contain subnets with internet access, or a "storage" space might contain subnets that can access the same storage networks.) Juju uses the current definition in order to ensure that deployed applications have access to networks appropriate for the services they provide.
The current definition of spaces as a L3 concept is problematic, in that sometimes Juju wants to deploy applications that themselves create a Layer 3 subnet. Therefore, it was decided that the concept of spaces will be pushed down a layer (to apply to VLANs in MAAS).
With spaces as a Layer 2 concept, it is now "a set of VLANs whose subnets can mutually communicate". As such:
- VLANs will gain a 'space' reference, and subnets will have their spaces
migrated to the VLANs they are on.
- On upgrades, if two subnets on the same VLAN are in different spaces, the most recently created space will be used for both.
- Spaces will become optional.
- Fresh installs will not have a default space (e.g. space-0).
- On upgrades, if only the default space (space-0) exists, it will be removed.
The following API changes will occur in MAAS 2.2:
- Editing a subnet's space will no longer be possible. Spaces must now be assigned on a per-VLAN basis. (Note: this is an API-breaking change; any usage of the MAAS API involving assigning subnets to spaces must be updated.)
- For backward compatibility, a subnet's endpoint will present the underlying VLAN's space as a read-only value.
Recommended actions for MAAS administrators prior to upgrading to MAAS 2.2:
- Ensure that no two subnets in the same VLAN are in different spaces, so that the upgrade path migrates the expected space to the VLAN.
- In order to preserve backward compatibility with Juju charms that use the subnet-based definition of a space, ensure that each space contains subnets capable of mutual communication. It may be helpful to view the list of subnets grouped by space (using the "Group by: Spaces" option on the Subnets page in the web UI) in order to verify that each space is defined correctly.
Please note that MAAS and Juju make assumptions about the security and isolation of a network based on the space defined for a VLAN (and, by extension, each subnet in that VLAN). Since a VLAN containing subnets in multiple spaces implies lack of network isolation, MAAS and Juju cannot support that use model.
MAAS 2.2 introduces a new concept called pods. In MAAS, pods are an abstraction to describe the availability of resources that allows MAAS to create or compose a machine with a set of those resources.
Pods refer to a combination of hardware resources that can be used to construct a machine. Each pod can be thought of as a pool of hardware with various available resources, such as CPU, RAM, and (local or remote) storage capacity. MAAS allows the manual allocation of physical hardware based on resources available in the pod. Users can use the MAAS UI or the API to allocate hardware from a pod.
In addition, MAAS will now make more efficient use of resources by dynamically allocating hardware (using Juju or the MAAS API). That is, machines can be allocated "just in time", based on CPU, RAM, and storage constraints.
The MAAS 2.2 release supports two types of pods:
- Physical systems with Intel RSD
- Virtual Machines with libvirt and qemu-kvm
MAAS now supports Intel Rack Scale Design (RSD). The supported version of Intel RSD is with the Intel OEM PODM/PSME software version 1.2.5, which is APIv1 and based on Redfish.
MAAS Intel RSD support includes the following features:
- Ability to discover all available resources
- Ability to discover all pre-composed (pre-existing) resources or machines
- Ability to compose machines (manually) via the API or the web UI
- Ability to compose machines (manually and dynamically) with remote attached storage (iSCSI)
- Ability to (dynamically) compose machines
MAAS supports using a given qemu-kvm system as a pod, using libvirt. MAAS will treat the libvirt hypervisor as a pod, including the following features:
- Ability to discover all available resources
- Ability to discover all pre-composed (pre-existing) resources or machines
- Ability to compose (create) machines (manually) via the API or the web UI
- Ability to (dynamically) compose machines
Hardware Testing in MAAS allows administrators to perform a series of tests to ensure the reliability of CPU, RAM, storage, and network environment. Therefore, MAAS administrators can now easily identify hardware issues before placing hardware into production.
Users can run hardware testing as part the commissioning processes, or as a separate action available on machines in "Ready" or "Deployed" state. When hardware tests are run as part of the commissioning process, machines that fail testing will not transition to the "Ready" state, and cannot be used for deployment.
The available tests are described below:
- smartctl-validate - uses the smartctl tool to verify existing SMART data on all drives has not detected any errors.
- smartctl-short & smartctl-long - runs the SMART self tests to validate health on all disks. It provides a long running and a short running test.
- smartctl-conveyance - runs the conveyance SMART self tests to validate health on all disks.
- badblocks - runs badblocks testing on all disks in parallel.
- badblocks-destructive - runs badblocks destructive tests on all disks in parallel. This means that badblocks will overwrite any date currently on the disks.
- stress-ng-cpu-short/long - stress tests the CPU of a machine for 5 minutes/12 hours respectively.
- stress-ng-memory-short/long - stress tests the memory of a machine for 5 minutes/12 hours.
- memtester - runs memtester over all available RAM.
- Internet connectivity - ensures machines can connect to the Internet.
- NTP connectivity - ensures that machines can connect to the configured NTP server, whether this is MAAS or an external NTP server.
MAAS now supports the modeling of DHCP relays in your network. For example, if an edge switch is forwarding DHCP traffic to a MAAS DHCP server, an administrator can tell MAAS that the VLAN at the edge will have its DHCP traffic forwarded to a particular destination VLAN. This allows MAAS to configure the DHCP server running on the primary and/or secondary rack controller to include a shared-network statement for that VLAN.
Please note that MAAS does not provide a DHCP relay service. Network administrators must configure a DHCP relay service to forward DHCP traffic from edge networks to the IP addresses of of the primary and/or secondary rack controller(s), on the VLAN where DHCP is enabled.
In MAAS 2.0, the concept of a "static range" (a specific range of addresses in which MAAS was allowed to freely allocate addresses from) was removed from MAAS, in favour of the idea that MAAS managing entire subnets. As such, the only way to tell MAAS to not allocate certain sections of a subnet is to add a reserved IP range.
MAAS 2.2 now enhances this functionality by introducing unmanaged subnets. By setting a subnet in MAAS to "unmanaged", administrators prevent MAAS from using that subnet for automatic IP assignment. On unmanaged subnets, MAAS will only allocate IP addresses from reserved ranges. If no reserved range exists on an unmanaged subnet, IP allocation will fail.
MAAS 2.2 introduces a new notification system that surfaces messages to the user via the web UI, providing more visibility to the user when:
- Rack controllers get disconnected
- Image imports fail on your region controller
- Rack controllers have images that the region controller does not
- Static IP address allocations on a subnet are close to exhaustion
MAAS now has the ability to automatically discover and manage the Facebook Wedge 40 and Wedge 100 switches. When enlisting a Wedge switch, MAAS will identify OpenBMC-compatible management, provide power management, and allow the deployment of Ubuntu. MAAS will also automatically tag the fact that the device is a switch (and which particular model was found) for easy identification.
Additionally, MAAS will automatically identify if the Trident or Tomahawk ASICs are connected to the switch, and will automatically identify them via tags.
The MAAS web UI is now more responsive on mobile devices, resulting in a better user experience for users working from their phone or tablet. These users will see a slick new design for these devices. Thanks goes to the Ubuntu Web team for making MAAS look great on small devices.
MAAS 2.2 improves the ability to configure storage configuration for Windows. This includes the ability to select the root device where Windows will be installed. Note that this ability extends to all DD images that MAAS can deploy.
MAAS 2.2 provides a 'Details Page' for 'Devices' allowing administrators to add new interfaces as well as modifying existing ones. It also provides the ability to update a device hostname and domain name.
MAAS 2.2 improves its package repositories support for Ubuntu mirrors by adding the ability to disable components. These components are Universe, Multiverse, and Restricted.
Several improvements have been made to the commissioning process in MAAS 2.2:
Ability to select custom commissioning scripts
As of 2.1, MAAS would run all uploaded custom commissioning scripts that. MAAS 2.2 now provides the ability to select which custom commissioning scripts to run. By default, however, all custom commissioning scripts will be run.
Commissioning no longer dependent on a 20 minute timeout
In 2.1, if the entire commissioning process took longer than 20 minutes to run, the machine would fail to commission.
As of 2.2, this is no longer the case. MAAS now has the ability to track both, builtin and custom commissioning scripts. This provides the flexibility to add custom commissioning scripts that would take longer than the initial 20 minute timeout, allowing them to fully run their scripts without marking a node 'Failed Commissioning'.
Several web UI improvements have been made:
Navigation improvements - adding tabs
Following the UX improvements from our design team, the web UI now has improved navigation. This includes a new tab-based approach for second level navigation items (for example, machines, devices, and controllers on the Nodes page).
Better error surfacing
Added error surfacing when editing node interfaces (including both machine and devices interfaces).
The MAAS team is happy to announce the introduction of a new and improved MAAS client library (python-libmaas). The MAAS team has started work on an asyncio-based client library to allow developers, integrators, and administrators to better interact with MAAS.
While this is an initial client library release and does not support all MAAS endpoints (nor all operations), we encourage all of our users to try it out and provide feedback. The currently supported releases include both MAAS 2.1 & 2.2.
If you wish to contribute to the development of the client library, please see below!
The library currently has the following endpoints:
- Boot-resources, boot-sources (manages images)
- Machines, devices, region-controllers & rack-controllers (manages nodes)
- Events (manages machine events)
- Configuration (settings)
If you would like to know more about python-libmaas, please refer to the below resources:
For installation and initial steps: http://maas.github.io/python-libmaas/index.html
For a few examples:
For pypi information: https://pypi.python.org/pypi/python-libmaas
If you would like to contribute you can find the source code in GitHub:
For more questions, please find us:
maas-develmailing list is a good place for questions
In MAAS 2.1, administrators will be shown the new MAAS dashboard after they log in to the web UI for the first time. Here, they are prompted to answer a few questions in order to get MAAS up and running quickly (see configuration journey section for details). In addition, administrators can view hosts that have been discovered on the network and quickly convert them to a device in MAAS.
In order to support new kernels, MAAS has moved to a new format for image streams. Previous releases used stream in 'v2' format. Starting with MAAS 2.1, the 'v3' format image stream will be used.
Users upgrading from earlier versions of MAAS who are using the default image source will be automatically migrated to the v3 format.
MAAS will not migrate the URL of a non-default image source (i.e. a mirror) as
it must first contain the v3 stream, which is available at
Old images downloaded from the v2 stream will continue to work but the MAAS team only supports MAAS 2.1 users using the v3 stream. Note that the default image source may eventually drop the v2 stream.
Bootloaders are now included in the default image source (see bootloaders section for details). Mirrors should be updated accordingly.
Starting with MAAS 2.1 and Ubuntu 16.04 LTS (Xenial), MAAS is adhering to a new naming convention for hardware enablement (HWE) kernels and general availability (GA) kernels. MAAS will no longer support the old naming convention for HWE kernels (e.g. hwe-y) when selecting images (Xenial and newer) to import. The new nomenclature is as follows:
ga-<version>: The GA kernel has the major kernel version of the kernel which the corresponding Ubuntu release shipped with. For example, ‘ga-16.04’ is the kernel which shipped with 16.04 yet comes with all the bug fixes provided by the Ubuntu archives. As per Ubuntu policy, a GA kernel will never have its major version upgraded (until the release itself is upgraded).
hwe-<version>: The latest HWE kernel available for a given LTS release. As new HWE kernels become available (from newly shipped Ubuntu releases), the hwe-
kernel will be correspondingly changed (up to, and including, the next LTS). For example, at time of writing, 'hwe-16.04' is equivalent to 'ga-16.04'. Soon after Ubuntu 16.10 is released, 'hwe-16.04' will point to 'ga-16.10'.
In the past, MAAS stored
pxe/uefi templates in
/etc/maas/templates. As of MAAS 2.1, these templates are no longer available
in that location as they are not intended to be modified by users.
Administrators can now perform some initial configuration upon logging in to the web UI for the first time. This includes:
- Ability to change the name of your MAAS
- Ability to configure options that affect connectivity:
- Select an upstream DNS Server (Optional)
- Input different Ubuntu mirrors (Required)
- Input an external proxy (Optional)
- Ability to select additional images to download
- Ability to import SSH keys from Launchpad or GitHub
MAAS now automatically listens to the network and reports any discovered
devices. Devices are identified when the rack controller observes them
communicating on an attached IPv4 subnet. Discovered devices that do not
correspond to machines and devices already known to MAAS are shown on the
dashboard. If a device advertises a hostname using
mDNS (such as with
Bonjour), MAAS will also present the discovered hostname in the dashboard.
Using the dashboard, a discovery can quickly be added to MAAS as a device or as
a network interface to a machine or device.
The device discovery feature was designed to operate passively by default. While MAAS will not send any traffic on attached networks for discovery purposes unless instructed to, there are two ways to instruct MAAS to map your networks:
On-demand: Administrators can choose to map their subnet using an action on the subnet details page. This action will scan the subnet just once, so that observed devices on that subnet may quickly be seen in the dashboard. This feature is useful after initially installing MAAS, to quickly populate the list of discoveries with active devices on the network.
Periodically (recommended): By enabling active discovery on a per-subnet basis, subnets will be scanned at a user-specified interval (default is every three hours). This allows MAAS to maintain current information about which IP addresses are in use on each subnet.
Before actively mapping any networks, it is recommended that the
be installed on each rack controller. Doing so results in faster scans that
require less network traffic. If nmap is not installed, MAAS will resort to
scanning using the
MAAS 2.1 improves offline deployment by adding support for Ubuntu derived repositories, PPAs, and custom APT repositories. This enables MAAS to configure deployed machines with the correct APT repositories and keyrings, without being dependent on Internet connectivity.
Prior to 2.1, MAAS only allowed users to change the Ubuntu archive to use. This was limited to defining the location of an official Ubuntu mirror.
Derived repositories are based on an Ubuntu mirror, but have had packages added or removed, which requires signing the repository with an unofficial GPG key. MAAS now allow users to provide GPG key fingerprints to support this type of repository. These fingerprints are required in order for the derived repository to be trusted, and will be added to the APT keyring on each machine.
PPAs can now be specified, which will be added to the APT sources on deployed machines. Users may define a GPG key fingerprint in order for the machine to trust the PPA, for cases where the deployed machine cannot access the Ubuntu key server.
Custom repositories can be specified to add additional packages to deployed machines. The distribution and component can be customized as appropriate. For example, users would be able to add the Google Chrome repository, which is as follows:
deb http://dl.google.com/linux/chrome/deb/ stable main
In this case, the distribution is 'stable', and the component is 'main'.
MAAS now provides managed NTP services (with
ntpd) for all region and rack
controllers. This allows MAAS to both keep its own controllers synchronized,
and keep deployed machines synchronized as well.
The region controller configures the NTP service (ntpd) to keep its time synchronized from one or more external sources. By default, the MAAS region controller uses ntp.ubuntu.com. This can be customized on the Settings page.
The rack controllers also configure the NTP service (ntpd). They synchronize their time with the region controllers.
Rack controllers also configure DHCP with the correct NTP information. Any machine on the network that obtains a DHCP lease from MAAS will benefit from NTP support.
External sites can be used as a time source for both controllers and machines. An existing NTP infrastructure can be used so that all machines and controllers sync their time from it. This is done by selecting the 'External Only' option on the Settings page.
MAAS 2.1 introduces the ability to define static routes. This allows administrators to configure reachability to a subnet from a source subnet. Administrators can define routes on a per-subnet basis to use a particular gateway, using a configured destination and metric.
MAAS 2.1 supports the creation of bridge interfaces. This support is limited to the ability to create a bridge against a single interface, such as for the purpose of eventually deploying virtual machines or containers on the machine.
Automatic bridge creation on all configured interfaces can also be performed at allocation time using the API.
MAAS 2.1 supports a new state in the machine lifecycle: Rescue mode. This allows users to boot a Deployed or a Broken node using an ephemeral image (Ubuntu running in memory on the underlying machine). This allows administrators to SSH to the machine for maintenance purposes.
The MAAS images page has been completely redesigned. Improvements include:
- Supports selecting the image source (maas.io or custom repository).
- Now shows the image releases and architectures available in a repository before the import starts.
- Now displays detailed status throughout the image import process.
- The Boot Images section in the Settings page has been removed.
MAAS 1.7 introduced the ability to erase disks when a machine is Released. This support was limited to erasing the whole disk and could only be enabled (or disabled) globally.
Starting with 2.1, MAAS supports the ability to request disk erasure on a per-machine basis, at the time the machine is released. In addition, new options for the disk erase mode have been added:
- Secure erase: MAAS will attempt to erase via secure erase (if the storage device supports it), otherwise, it will perform a full erase or a quick erase (depending on the options provided).
- Quick erase: MAAS will only erase the beginning and the end of each storage device.
MAAS now attempts to auto-detect and tag SR-IOV NIC cards.
MAAS now allows the definition of tags per network interface via the web UI.
Starting with Ubuntu 16.04 LTS, low latency kernels are available on i386 and amd64 for both GA and HWE kernels. The currently available low latency kernels are:
- hwe-x-lowlatency: the Xenial low latency HWE kernel for Trusty
- ga-16.04-lowlatency: the low latency GA kernel for Xenial
- hwe-16.04-lowlatency: the low latency HWE kernel for Xenial
Note: As time of writing, the last 2 kernels are the same.
Previously, bootloaders were downloaded on the rack controller from the Ubuntu archives for each architecture MAAS had images for. Starting with MAAS 2.1, bootloaders are downloaded with the images from where rack controllers retrieve them, as they do with images. So MAAS no longer directly interacts with the Ubuntu archives.
In the case that bootloaders are missing from the stream, MAAS will attempt to locate previous downloads of the bootloader as well as package installs of the bootloader. Users with image mirrors must ensure image their mirrors include the bootloaders in order to be running the latest supported versions.
Users can now initiate the import of SSH public keys from the web UI. Users who log in to MAAS for the first time will be given the opportunity to import their SSH keys. Alternatively, users can import keys later into their user profile page, or continue to upload keys manually.
Both the DHCP Snippets section and the Package Repositories section have been improved in order to show errors in a more user-friendly way.
The HTML templates and CSS frameworks in MAAS have been completely rebuilt with the Vanilla CSS framework. Icons and interactions in MAAS have greatly improved; users will notice smoother, more intuitive interactions with the web UI.
The MAAS team would like to thank the Canonical design and web teams for their contributions in this area.
The Networks page has been renamed to Subnets.
MAAS version 2.0 is supported on Ubuntu 16.04 LTS. MAAS 2.0 and greater will NOT be supported on Ubuntu 14.04 LTS. The latest MAAS 1.9 point release will continue to be supported on Ubuntu 14.04 LTS (Trusty) until it reaches end-of-life.
Upgrades are supported for users running Ubuntu 14.04 systems running MAAS 1.9 or earlier. Upon upgrading to Ubuntu 16.04, the MAAS database and configuration will be seamlessly migrated to the supported MAAS version.
Please see the “Other Notable Changes” section below for more details regarding the reasons for this change.
Cluster controllers have been renamed to rack controllers.
Starting from MAAS 2.0, MAAS cluster controllers have been deprecated,
along with the legacy
nodegroups API. The new API endpoint is
rackcontrollers, which provides feature parity with earlier versions
For more information on rack controllers, refer to the Major new Features section bellow or refer to rack-configuration.
Starting from MAAS 2.0, the MAAS REST API version 1.0 has been deprecated. MAAS 2.0 drops support for the legacy 1.0 API, in favor of API version 2.0. With the introduction of the new API version, various endpoints have now been deprecated, and new end-points have been introduced. API users will need to update their client tools to reflect the changes.
For more information on API 2.0, refer to API documentation <region-controller-api>.
Starting from MAAS 2.0, static IP ranges (previously found on the cluster interface page) have been deprecated. MAAS now assumes total control of a subnet. MAAS will automatically assign IP addresses to deployed machines, as long as those IP addresses are not within a dynamic or a reserved IP range. Users are now only required to specify one or more dynamic ranges per subnet. Dynamic ranges are used for auto-enlistment, commissioning, and any other systems configured for DHCP. IP addresses in-use for purposes such as devices, default gateways, DNS servers, rack and region controllers, and BMCs are automatically avoided when assigning IP addresses. Reserved IP ranges may be added if MAAS should avoid certain ranges of IP addresses in the subnet.
maas-region-controller-min package has been renamed to
maas-region-api. This package provides API services for MAAS
maas-regiond) and can be used to scale out the API front-end of a
Starting from MAAS 2.0, the
maas command now provides the ability to
create admin users. The
maas-region createadmin command has
been deprecated. New administrators should now be created with
The MAAS rack controller command-line interface (
been replaced by the
The MAAS region controller command-line interface (
has been replaced by the
maas-region command. Note that this command
provides an interface to interact directly with Django, which should
only be used for debugging purposes.
Because support for the Debian Installer (DI) has been dropped (as of MAAS 1.9), MAAS no longer downloads DI-related files from simplestreams. Upon upgrading to MAAS 2.0, DI-related files will be removed from the MAAS region (and all rack controllers).
Starting from MAAS 2.0, MAAS cluster controllers have been renamed to rack controllers.
nodegroups/(group)/interfacesAPI endpoints have been deprecated. In MAAS 2.0, the
rackcontrollersinterface partially replaces this functionality. For defining dynamic and reserved ranges, or specifying default gateways, use the
subnetsendpoint. For enabling or disabling DHCP, use the
- The Clusters tab is no longer available in the Web UI. Controllers are now found under the Nodes tab, where each region and/or rack controller can be found. Other cluster interface properties have been moved to the Subnet and VLAN details pages under the Networks tab.
Machines no longer belong to a specific controller. In earlier versions of MAAS, machines would directly assigned to a cluster controller. The cluster controller that the machine belonged to would not only perform DHCP for that machine, but also all the PXE booting and power management.
In order to support high availability for rack controllers, (starting from MAAS 2.0) machines no longer belong to a specific rack controller. The best controller to manage a machine is now determined at runtime.
DHCP is now configured per-VLAN. In earlier versions of MAAS, DHCP was directly linked and configured per cluster interface. As of MAAS 2.0, DHCP is now configured and managed per-VLAN, which allows any rack controller to potentially provide DHCP in a high-availability environment.
- Rack controllers have been enabled for high availability. Starting from MAAS 2.0, rack controllers in the same VLAN become candidates to manage DHCP, PXE/TFTP, and power control for machines on the VLAN. MAAS now supports the concept of a primary and a secondary rack controller. If a secondary controller determines that the primary controller is unavailable, it will assume control of those services.
maas-rack support-dumpcommand. For increased support observability, users can now dump the contents of several internal MAAS data structures by executing
sudo maas-rack support-dump. This command will dump networking diagnostics, rack configuration, and image information. Information can be restricted to a particular category by using the
- Rack controllers can now be found under the Nodes tab in the Web UI. MAAS 2.0 Adds a new Controllers section under thee Nodes tab. This section will now list all rack and region controllers. Under a rack controller, the user will be able to see service tracking, connected VLANs, rack interfaces and other relevant information.
Starting from MAAS 2.0, MAAS provides the ability to scale out (provide
redundancy for) the MAAS region controller API, HTTP server, and DNS.
This will allow administrators to set up multiple MAAS region
maas-region-api) against a common database, providing
redundancy of services. With further manual configuration, users will be
able to setup the MAAS region controller in high availability mode.
MAAS 2.0 introduces a few new Web UI features that were not available in previous versions of MAAS.
- Added fabric and space details pages.
- Added the ability to add and remove fabrics, spaces, subnets and VLANs. This can be done using the actions menu on the Networks tab. The ability to delete fabrics, spaces, subnets and VLANs is also available from the details page for each respective object.
MAAS 2.0 extends DNS management by adding the following features:
- Ability to create multiple DNS domains.
- Ability to add multiple records (
SRV) per domain. (API only)
- Ability to select the domain for machines and devices.
- Ability to assign (additional) names to IP addresses. (API only)
- For deployed machines,
Arecords continue to be created for the IP of the PXE interface.
- Additional PTR records are now created for all non-PXE interfaces in
- Reverse DNS is now generated for only the subnet specified, rather than the parent /24 or /16. By default, RFC2137 glue is provided for networks smaller than /24. This can be disabled or changed on a per-subnet basis via the API.
Previous versions of MAAS used the concepts of a dynamic range and static range, which were properties of each cluster interface. This has been redesigned for MAAS 2.0 as follows:
- Dynamic ranges have been migrated from earlier MAAS releases as-is.
Because static ranges have been removed from MAAS, each static range has been migrated to one or more reserved ranges, which represent the opposite of the previous static range. (MAAS now assumes it has full control of each managed subnet, and is free to assign IP addresses as it sees fit, unless told otherwise.)
For example, if in an earlier MAAS release a cluster interface was configured on 192.168.0.1/24, with a dynamic range of 192.168.0.2 through 192.168.0.99, and a static range of 192.168.0.100 through 192.168.0.199, this will be migrated to:
IP range #1 (dynamic): 192.168.0.2 - 192.168.0.99 IP range #2 (reserved): 192.168.0.200 - 192.168.0.254
Since 192.168.0.100 - 192.168.0.199 (the previous static range) is not accounted for, MAAS assumes it is free to allocate static IP addresses from that range.
Scalability is now possible by means of adding a second dynamic IP range to a VLAN. (To deal with IP address exhaustion, MAAS supports multiple dynamic ranges on one or more subnets within a DHCP-enabled VLAN.)
- Reserved ranges can now be allocated to a particular MAAS user.
- A comment field has been added, so that users can indicate why a particular range of IP addresses is reserved.
- IP ranges can be configured in the Web UI via the Subnet details
page, or using the
subnetsREST API endpoint.
Version 1.0 of the MAAS REST API has been removed and replaced with the 2.0 version of the REST API. As such, new endpoints and commands have been introduced:
RackControllers - This endpoint/command has the following operations in addition to the base operations provided by nodes:
import-boot-images- Import the boot images on all rack controllers
describe-power-types- Query all of the rack controllers for power information
RackController - This endpoint/command has the following operations in addition to the base operations provided by nodes
import-boot-images- Import boot images on the given rack controller
refresh- refresh the hardware information for the given rack controller
- Machines - This endpoint/command replaces many of the operations
previously found in the nodes endpoint/command. The machines
endpoint/command has the following operations in addition to the
base operations provided by nodes.
power-parameters- Retrieve power parameters for multiple machines
list-allocated- Fetch machines that were allocated to the user/oauth token.
allocate- Allocate an available machine for deployment.
accept- Accept declared machine into MAAS.
accept-all- Accept all declared machines into MAAS.
create- Create a new machine.
add-chassis- Add special hardware types.
release- Release multiple machines.
- Machine - This endpoint/command replaces many of the operations
previously found in the node endpoint/command. The machine
endpoint/command has the following operations in addition to the
base operations provided by node.
power-parameters- Obtain power parameters for the given machine.
deploy- Deploy an operating system to a given machine.
abort- Abort the machines current operation.
get-curtin-config- Return the rendered curtin configuration for the machine.
power-off- Power off the given machine.
set-storage-layout- Change the storage layout of the given machine.
power-on- Turn on the given machine.
release- Release a given machine.
clear-default-gateways- Clear any set default gateways on the machine.
update- Change machine configuration.
query-power-state- Query the power state of a machine.
commission- Begin commissioning process for a machine
- All list commands/operations have been converted to read
- All new and add commands/operations have been converted to create
- Nodes - The nodes endpoint/command is now a base endpoint/command
for all other node types(devices, machines, and rack-controllers).
As such most operations have been moved to the machines
endpoint/command.The following operations remain as they can be used
on all node types.
is-registered- Returns whether or not the given MAC address is registered with this MAAS.
set-zone- Assign multiple nodes to a physical zone at once.
read- List nodes visible to the user, optionally filtered by criteria.
- Node - The node endpoint/command is now a base endpoint/command for
all other node types(devices, machines, and rack-controllers). As
such most operations have been moved to the machine
endpoint/command. The following operations remain as they can be
used on all node types.
read- Read information about a specific node
details- Obtain various system details.
delete- Delete a specific node.
- With the migration of nodes to machines the following items
previously outputted with the list command have been changed or
removed from the machines read command:
- ``status - Will now show all status types
substatus_name- Replaced by
- ``boot_type - Removed, MAAS 2.0 only supports fastpath.
pxe_mac- Replaced by
hostname- Now only displays the hostname (without the domain) of the machine.
domainattributes can now be used instead.
- And other endpoints/commands have been deprecated:
- NodeGroups - Replacement operations are found in the RackControllers, Machines, and BootResources endpoints/commands.
- NodeGroupInterfaces - replacement operations are found in the RackController, IPRanges, Subnets, and VLANS endpoints/commands.
MAAS 2.0 Storage Model has been extended to support:
- XFS as a filesystem.
- Mount options.
- Swap partitions. (MAAS 1.9 only supported the creation of a swap file in the filesystem.)
All of these options are currently available over the CLI.
MAAS 2.0 introduces the ability to define DHCP snippets. This feature allows administrators to manage DHCP directly from MAAS, removing the need to manually modify template files. The following types of DHCP snippets can be defined:
- Host snippets - used for configuration for a particular node in MAAS.
- Subnet snippets - used for configuration for a specific subnet in MAAS.
- Global snippets - used for configuration that will affect DHCP (isc-dhcp) as a whole.
For more information, see DHCP Snippets <dhcpsnippets>.
Starting from MAAS 2.0, MAAS now manages the configuration for
maas-proxy. This allows MAAS to lock down the proxy so that it only
allows traffic from networks MAAS knows about. For more information,
see MAAS Proxy <proxy>.
MAAS 2.0 now enables
rsyslog for the enlistment and commissioning
environment (when using Xenial as the commissioning image). This allows
users to see
cloud-init's syslog information in
MAAS 2.0 introduces the ability to change a machine’s DNS domain via the Web UI. It was previously supported on the API only.
In the Networks tab, a new networks overview has been introduced, which provides a high-level view of the MAAS networking mode. The network model can be grouped by either fabrics or spaces.
MAAS now tracks the status of the services required for its operation,
Starting with MAAS 2.0, MAAS has now been ported to Python 3.5 (the default version of Python in Ubuntu 16.04 "Xenial").
MAAS is now based on Django 1.8. Django 1.8 has dropped support for the South migration system in favor of the native Django migration system, which breaks backwards compatibility with previous versions of Django.
MAAS continues to support a full upgrade path. MAAS versions 1.5, 1.7, 1.8, and 1.9 have been tested and confirmed to upgrade seamlessly to MAAS 2.0.
MAAS no longer scans the leases file every 5 minutes.
now directly notifies MAAS if a lease is committed, released,
Host entries are now rendered in the DHCP configuration instead of placed in the leases file. This removes any state that previously existed in the DHCP lease database on the cluster controller.
Starting with MAAS 2.0, if the dhcpd.leases file is lost (such as during a failure scenario in a high availability environment), MAAS will be able to reconstruct it.
MAAS selects one of the available rack controllers to power control or query a BMC. The same rack controller that powers the BMC does not need to be the rack controller that the machine PXE boots from.
We'd love to hear about how you're using MAAS, whether it's at the smallest of scales or the largest. Our team is always approachable and can usually be found in the following locations: