Thread Previous • Date Previous • Date Next • Thread Next |
I'm happy to announce that MAAS 1.9.0 Alpha 4 has been released for testing. Notable changes: *Changes:* - Minor UI/UX fixes and improvements. - Addressed various backend concurrency issues. - Addressed an issue where MAAS will fail to deploy on disks larger than 2 TiB. *Known problems and Work Arounds (Recurring from Alpha2)* - Juju fail to SSH due to changing MAAS' /etc/network/interfaces - By default, Juju will change eth0 on /etc/network/interfaces in order to support LXC container addressability with MAAS. However, starting from MAAS 1.9 provided that MAAS writes /etc/network/interfaces, users will be unable to successfully finish the bootstrap process provided Juju re-configures /etc/network/interfaces causing that eth0 never comes back up. - To work around this issue, users will have to deploy with `disable-network-management: true`. - For more information, please refer to *[2] https://launchpad.net/bugs/1494476 <https://launchpad.net/bugs/1494476>* - CentOS fails to deploy when deploying with LVM MAAS will fail to deploy CentOS with LVM by default. This can be changed by changing the Setting of the default deployment layout to Flat. This can be done in the MAAS Settings page under the storage section. *[3]:* *https://launchpad.net/bugs/1499558 <https://launchpad.net/bugs/1499558>* *Testing* MAAS 1.9.0 Alpha 4 is available for testing in: *ppa:maas/next* *Work in progress* Please note that there's other work in progress, that is not yet visible, to enhance some of the features above or to complete some new features that will be made available as part of 1.9. Current work in progress is: - Advanced Storage Configuration WebUI - LVM - RAID - BCache -- Andres Rodriguez Engineering Manager, MAAS & OIL DevOps Canonical USA, Inc.
Thread Previous • Date Previous • Date Next • Thread Next |