Skip to main content
  1. Blog
  2. Article

Canonical
on 5 September 2017

MAAS Development Update – Aug 21st – Sept 1st


Hello MAASters! This is the development summary for the past couple of weeks:

MAAS 2.3 (current development release)

Hardware Testing Phase 2

  • Added parameters form for script parameters validation.
  • Accept and validate results from nodes.
  • Added hardware testing 7zip CPU benchmarking builtin script.
  • WIP – ability to send parameters to test scripts and process results of individual components. (e.g. will provide the ability for users to select which disk they want to test, and capture results accordingly)
  • WIP – disk benchmark test via Fio.

Network beaconing & better network discovery

  • MAAS controllers now send out beacon advertisements every 30 seconds, regardless of whether or not any solicitations were received.

Switch Support

  • Backend changes to automatically detect switches (during commissioning) and make use of the new switch model.
  • Introduce base infrastructure for NOS drivers, similar to the power management one.
  • Install the Rack Controller when deploying a supported Switch (Wedge 40, Wedge 100)
  • UI – Add a switch listing tab behind a feature flag.

Minor UI improvements

  • The version of MAAS installed on each controller is now reported on the controller details page.

python-libmaas

  • Added ability to power on, power off, and query the power state of a machine.
  • Added PowerState enum to make it easy to check the current power state of a machine.
  • Added ability to reference the children and parent interfaces of an interface.
  • Added ability to reference the owner of node.
  • Added base level `Node` object that `Machine`, `Device`, `RackController`, and `RegionController` extend from.
  • Added `as_machine`, `as_device`, `as_rack_controller`, and `as_region_controller` to the Node object. Allowing the ability to convert a `Node` into the type you need to perform an action on.

Bug fixes:

  • LP: #1676992 – force Postgresql restart on maas-region-controller installation.
  • LP: #1708512 – Fix DNS & Description misalignment
  • LP: #1711714 – Add cloud-init reporting for deployed Ubuntu Core systems
  • LP: #1684094 – Make context menu language consistent for IP ranges.
  • LP: #1686246 – Fix docstring for set-storage-layout operation
  • LP: #1681801 – Device discovery – Tooltip misspelled
  • LP: #1688066 – Add Spice graphical console to pod created VM’s
  • LP: #1711700 – Improve DNS reloading so its happens only when required.
  • LP: #1712423, #1712450, #1712422 – Properly handle a ScriptForm being sent an empty file.
  • LP: #1621175 – Generate password for BMC’s with non-spec compliant password policy
  • LP: #1711414 – Fix deleting a rack when it is installed via the snap
  • LP: #1702703 – Can’t run region controller without a rack controller installed.

This article originally appeared at Andres Rodriguez's blog

Related posts


Pedro Lazzarotto
12 June 2026

A decade of Ubuntu on IBM Z and IBM LinuxONE

Partners Article

This year we celebrate a decade of Ubuntu Server support on the s390x architecture: marking a long-standing collaboration between Canonical and IBM that began at LinuxCon 2015. The first release happened on April 21, 2016, bringing Ubuntu 16.04 LTS (Xenial Xerus) to IBM Z and IBM LinuxONE platforms.  A first for Ubuntu on IBM That ...


Pedro Lazzarotto
11 June 2026

AI at the edge: simplifying infrastructure with Cisco and Canonical

AI Article

Legacy infrastructure was not designed for the requirements of the AI era. While large-scale model training remains centralized in data centers, test-time inference is rapidly shifting to the edge to reduce latency and bandwidth consumption. This shift creates a new frontier for enterprise AI, but deploying at the edge introduces signific ...


estelacarmona
11 June 2026

The next era of telco clouds: get open infrastructure choice with Sylva and Canonical Kubernetes

5G Article

Achieving vendor neutrality in telco clouds requires an infrastructure layer that respects open standards, without wrapping them in rigid platform layers. By combining upstream alignment with up to 15 years of support longevity, Canonical’s approach to Sylva is built around a requirement that matters deeply to telcos: follow upstream clou ...