MAAS Development Summary – August 21, 2017
Canonical
on 18 August 2017
Hello MAASters! This is the development summary for the past couple of weeks:
MAAS 2.3 (current development release)
The team is preparing and testing the next official release, MAAS 2.3 alpha2. It is currently undergoing a heavy round of testing and will be announced separately the beginning of the upcoming week. In the past three weeks, the team has:
- Support for CentOS Network configuration
We have completed the work to support CentOS Advanced Networking, which provides the ability for users to configure VLAN, bond and bridge interfaces, bringing it feature parity with Ubuntu. This will be available in MAAS 2.3 alpha 2. - Support for Windows Network configuration
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 [1]. - Hardware Testing Phase 2
- Testing scripts now define a type field that informs MAAS for which component will be tested and where the resulting metrics will apply. This may be node, cpu, memory, or storage, defaults to node.
- Completed work to support the definition and parsing of a YAML based description for custom test scripts. This allows the user to defined the test’s title, description, and the metrics the test will output, which allows MAAS to parse and eventually display over the UI/API.
- Network beaconing & better network discovery
- Beaconing is now fully functional for controller registration and interface updates!
- When registering or updating a new controller (either the first standalone controller, or a secondary/HA controller), new interfaces that have been determined to be on an existing VLAN will not cause a new fabric to be created in MAAS.
- Switch modeling
- The basic database model for the new switching model has been implemented.
- On-going progress of presenting switches in the node listing is under way.
- Work is in-progress to allow MAAS to deploy a rack controller which will be utilized when deploying a new switch with MAAS.
- Minor UI improvements
- Renamed “Device Discovery” to “Network Discovery”.
- Discovered devices where MAAS cannot determine the hostname now just show the hostname as “unknown” and grayed out instead of using the MAC address manufacturer as the hostname.
- Bug fixes:
- LP: #1704444 – MAAS API returns 500 internal server error instead of raising actual error.
- LP: #1705501 – django warning on install
- LP: #1707971 – MAAS becomes unstable after rack controller restarts
- LP: #1708052 – Quick erase doesn’t remove md superblock
- LP: #1710681 – Cannot delete an Ubuntu image, “Update Selection” is disabled
MAAS 2.2.2 Released in the Ubuntu Archive!
MAAS 2.2.2 has now also been released in the Ubuntu Archive. For more details on MAAS 2.2.2, please see [2].
[1]: https://maas.io/contact-us
[2]: https://lists.ubuntu.com/archives/maas-devel/2017-August/002663.html
Ubuntu cloud
Ubuntu offers all the training, software infrastructure, tools, services and support you need for your public and private clouds.
Newsletter signup
Related posts
EdgeIQ and Ubuntu Core; bringing security and scalability to device management
Today, EdgeIQ and Canonical announced the release of the EdgeIQ Coda snap and official support of Ubuntu Core on the EdgeIQ Symphony platform. EdgeIQ Symphony...
Ubuntu 20.04 LTS end of life: standard support is coming to an end. Here’s how to prepare.
In 2025, Ubuntu 20.04 LTS (Focal Fossa) will reach the end of its standard five-year support window. It’s time to start thinking about your options for...
Join Canonical in London at Dell Technologies Forum
Canonical is excited to be partnering with Dell Technologies at the upcoming Dell Technologies Forum – London, taking place on 26th November. This prestigious...