maas-devel team mailing list archive

[Andres Rodriguez <andres.rodriguez@xxxxxxxxxxxxx>]

I'm happy to announce that MAAS 1.8.0 has been released. Full release notes
are available at:

http://maas.ubuntu.com/docs1.8/changelog.html#id1

MAAS 1.8 Introduces the following features:

*Major new features:*

   - *WebUI Re-Design*

The new MAAS Web-UI has been fully re-designed and includes the following
new features:


   - Live Updating for Node Details and Node Listing Page
   - Improved Bulk Actions
   - Live Searching
   - Better Filtering
   - Node & Storage Tag Management
   - Add Chassis


   - *Support for Devices*

MAAS now supports the concept of Devices. This allows administrators track
and manage external devices to MAAS and provide IP / DNS for these devices
on the network.


   - *Storage Discovery*

MAAS now discovers all storage attached to a machine.


   - *Twisted Daemons*

MAAS Region Controller has moved away from using apache and now runs under
a Twisted daemon. MAAS Region Controller is now controlled by
*maas-regiond * daemon.


   - *DB Isolation*

MAAS DB Isolation has been increased to provide improved robustness on
distributed environments.


   - *VMWare Support*

MAAS now supports the management of VM's under VMWare products (vCenter,
ESX, VMWare work station).


   - *Add Chassis*

New Add Chassis functionality has been added to MAAS to be able to add all
machines within a chassis or within a Hypervisor (KVM/VMWare).


*Minor notable changes*

   - *RPC Communication & Ports*

Internal communication between the MAAS Region controller and the MAAS
Cluster controller is now limited to ports between 5250 and 5259.
Administrators need to ensure these ports are opened in their firewalls.


   - *Discovered virtual machine names are imported into MAAS*

MAAS will now keep the Virtual Machine names as per defined as the domain
in their hypervisor.


   - *Virtual machine boot order is now set automatically*

Virtual Machines are now told to PXE boot by default to ensure proper MAAS
control.


   - *Systemd support*

MAAS has gained support for systemd, allowing its daemons run under systemd.


*Known problems & Work Arounds*

   - *Disk space not reclaimed when MAAS boot images are superseded.*

Whenever new boot images are synced to MAAS, new large objects in the DB
are created for them, which might replace older version of the same image.
The standard postgresql autovacuum does not remove these large objects that
are no longer used. Therefore, a new command has been introduced to
appropriately vaccum these objects:

maas-region-admin db_vacuum_lobjects.


For more information please see:

https://launchpad.net/bugs/1459876


   - *MAAS logs to maas.log.1 instead of maas.log*

In one
 situation it has been seen that maas.log is empty, and rsyslog
 was sending logs to maas.log.1 instead. This has been identified
as an issue in rsyslog rather than maas. More information can be found on:

  https://launchpad.net/bugs/1460678

The full list of bugs fixed for this milestone is available at:

https://launchpad.net/maas/+milestone/1.8.0


*Testing*
MAAS 1.8.0 will be available for testing for the next 24 hours at:

*ppa:maas-maintainers/testing*


*NOTICE:*
*After the 24 hr period, MAAS 1.8.0 Final Release will replace MAAS 1.7.5
in:*

*ppa:maas-maintainers/stable*

-- 
Andres Rodriguez
Engineering Manager, MAAS & OIL DevOps
Canonical USA, Inc.