Canonical
on 22 August 2017
MAAS 2.3.0 Alpha 2 Released!
Hello MAASters!
We're happy to announce 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.
PPA Availability
For those running Ubuntu Xenial and would like to use Alpha 1, please use the following PPA:
Snap Availability
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)
Important announcements
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:
- Static network configuration.
- Bonds, VLAN and bridge interfaces.
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.
UI improvements
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 https://launchpad.net/maas/+milestone/2.3.0alpha1