August 10, 2018
The purpose of this thread is to give you an update on what’s been going on around the development of MAAS since the latest release announcement.
Development release (2.5)
Since MAAS 2.5.0 Alpha 1 was released, we have been working on the following improvements:
Proxying the communication through the rack controller
When proxying squid communication through the rack controller, we discovered that Linux does not allow specifying multiple APT proxies (nor environment proxies, for the matter). This is a problem in HA environments because machines need to know the multiple rack controllers. To address this issue, MAAS will use DNS records to configure the APT proxy on deployed machines.
Squid proxying through the rack is currently undergoing testing.
KVM Pod Networking
- Since the last update, MAAS now includes the ability to attach networks to VMs inside a KVM pod. This allows users to request machines and automatically create interfaces attached to different networks. We are currently testing this feature. More details will come in the next release.
Bug fixes and minor improvements
- ESXi OS driver - We are working on the ability to deploy ESXi.
- Add ‘allow_dns’ Subnet option. - Adds the ability to allow (or trust) clients of a Subnet to use MAAS for DNS resolution.
- LP: #1774206 - Add config option ‘dns_trusted_acl’. - Adds the ability to specify extra networks, not known to MAAS, that will be trusted to use MAAS for DNS resolution.
- LP: #1785721 - Allow reading, updating and deleting a resource pool with its name.
- LP: #1782025 - Discover known machines during enlistment by MAC address.
- LP: #1781275 - Parse FIO metrics on Bionic.
Stable releases (2.3 & 2.4)
MAAS 2.4.1 is currently undergoing internal testing. We are looking to release 2.4.1 during the upcoming week. For more information please refer to:
MAAS 2.3.4 is also undergoing internal testing and will be released next week. For more information please refer to: