I’m happy to annouce that MAAS 2.3.0 Alpha 2 has now been released and it is currently available in Ubuntu Artful, PPA for Xenial and as a snap.
For those running Ubuntu Xenial and would like to use Alpha 1, please use the following PPA:
For those running from the snap, or would like to test the snap, please use the Beta channel on the default track:
sudo snap install maas –devmode –beta
MAAS 2.3.0 (alpha2)
Advanced Network for CentOS & Windows
The MAAS team is happy to announce that MAAS 2.3 now supports the ability to perform network configuration for CentOS and Windows. The network configuration is performed via cloud-init. MAAS CentOS images now use the latest available version of cloud-init that includes these features.
New Features & Improvements
CentOS Networking support
MAAS can now perform machine network configuration for CentOS, giving CentOS networking feature parity with Ubuntu. The following can now be configured for MAAS deployed CentOS images:
Thanks for the cloud-init team for improving the network configuration support for CentOS.
Windows Networking support
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 (https://maas.io/contact-us).
Network Discovery & 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.
Minor UI improvements have been made
Renamed “Device Discovery” to “Network Discovery”.
Discovered devices where MAAS cannot determine the hostname now show the hostname as “unknown” and greyed out instead of using the MAC address manufacturer as the hostname.
Issues fixed in this release
Issues fixed in this release are detailed at:
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 .
- 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 .