maas-devel team mailing list archive

[Andres Rodriguez <andres.rodriguez@xxxxxxxxxxxxx>]

I'm happy to announce that MAAS 1.9.0 Alpha 2 has been released for testing.
(For full details please refer to
http://maas.ubuntu.com/docs/changelog.html#alpha2 ).

*Features:*

   - *Advanced Network Configuration*
      - Supports the configuration of MAAS node networking and writes
      /etc/network/interfaces.
      - Allows the configuration of VLANs and bonds.
      - More information on networking please refer to http://maas
      .ubuntu.com/docs/networking.html
      <http://maas.ubuntu.com/docs/storage.html>


   - *Fabrics, Spaces, Subnets, FANs*
      - MAAS now has gained knowledge of Fabrics, Spaces, Subnets and FANs.
      - For more information, please refer to
      http://maas.ubuntu.com/docs/networking.html
      <http://maas.ubuntu.com/docs/storage.html>


   - *CentOS as a first class citizen*
      - CentOS is now available to download in the MAAS Images page.
      However, while the image is being tested, this will only be available if
      MAAS is using the updated Images (aka daily).
      - To change to the usage of daily image, please change the 'Sync URL'
      setting under 'Boot Images' in the MAAS' Settings page to:
      http://maas.ubuntu.com/images/ephemeral-v2/daily/


   - *Commissioning Actions*
      - MAAS now supports different commissioning actions:
         - Imports the user's SSH key into the commissioning environment,
         and allows it to ssh using the 'ubuntu' system user.
         - Prevent's the machine from turning off after commissioning has
         finished.
         - Preserve's the user's network configuration. If the user has
         made any manual network configuration and desires to re-commission the
         machine, the user can decide to preserve this configuration,
otherwise MAAS
         will simply replace it.
         - Preserve's the user's storage configuration. The same concept
         applies as preserving network configuration.

*Known problems and Work Arounds*

   - 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 2 will be available for testing in:

*ppa:maas/next-proposed*

After 48hrs, MAAS 1.9.0 Alpha 2 will be made available in:

*ppa:maas/next*


*Other 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:

   - Storage Configuration WebUI.
   - Network Configuration WebUI
   - Networks Page - Read only WebUI


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