I'm happy to annouce that MAAS 2.1.0 Alpha 3 has been released.

MAAS 2.1.0 Alpha 3 has been made available in:


*Filing bugs*
Users can file bugs in [1], please use a prefix for the subject, such as

[1] https://bugs.launchpad.net/maas/+filebug

*Release Notes*
Major new features


   *First User Configuration Journey (UI)*

Starting from alpha 3, MAAS now provides the ability for administrators to
perform some initial configuration when they log-in into the UI for the
first time. The configuration includes:


   Ability to change the name of your MAAS.

   Ability to configure options that affect connectivity:

      Option to select an Upstream DNS Server (Optional)

      Option to input different Ubuntu Mirrors (Required).

      Option to input an external proxy (Optional)

   Ability to select additional images to download.


   MAAS Images page re-written in AngularJS

Continuing the transition from YUI to AngularJS, the MAAS Images page has
now been completely redesigned and reimplemented in AngularJS. Improvements
to the Image page include:

   - Ability to select the image source (maas.io or custom repository).
      - Show the releases and architectures available in the custom
      repository before the import starts.
      - Ability to view the status of the image in the import process.
      - Show percentage based progress on the image import.
      - Additionally, the ‘Boot Images’ section in the Settings page has
      been removed.


   MAAS time sync, NTP services and configuration

Starting from alpha 3, MAAS now provides managed NTP services (with ntpd)
in both the Region and Rack controller. This allows MAAS to not only keep
its own controllers time synced, but the deployed machines as well.

   - Region Controller time syncs from external source

The Region Controller configures the NTP service (ntpd) to keep its time
sync from one or various external sources. By default, the MAAS region
controller syncs its time from ntp.ubuntu.com. The default can be changed
by one or multiple external NTP servers from the Settings page, under the
Network Configuration section.

   - Rack Controller time syncs from the Region Controller

The Rack Controllers also configure the NTP service (ntpd). Unlike the
Region Controllers, the Rack Controllers sync their time from the Region
Controller(s) instead of accessing directly to the external time source.

Additionally, the Rack Controllers also configure DHCP with the correct NTP
information, so that any machine on the network that DHCP’s from MAAS can
benefit of the NTP configuration.

   - Machines configured to sync time from external NTP (transitional).

MAAS also configures deployed machines with NTP configuration. This is done
by cloud-init via MAAS vendor data.

MAAS will configure machines to use either the MAAS Rack Controllers on the
same VLAN, or the external time source (if configured under the Settings

Minor new features


   *(Backend) Ability to import SSH keys from Launchpad and Github*

MAAS now provides the ability to import SSH keys for a user from Launchpad
and Github. This is currently supported via the API or via the user
creation process. Users can import their SSH keys when creating their user
for Launchpad or Github:

maas createadmin --ssh-import lp:<user-id>

maas createadmin --ssh-import gh:<user-id>

Or via the API based CLI with:

maas <maas username> sshkeys import protocol=lp auth_id=<user-id>

maas <maas username> sshkeys import protocol=gh auth_id=<user-id>


   MAAS now provides cloud-init vendor data for NTP

As of MAAS 2.1 alpha 3, MAAS now provide cloud-init vendor data. Vendor
data allows cloud-init to do some initial configurations on the system
before user data is being run. As of 2.1, MAAS will provide NTP
configuration which is delivered via vendor data. Note that this is
dependent on the latest version of cloud-init (0.7.8-1-g3705bb5-0ubuntu1
This is currently available in Yakkety and is in progress to be available
in Xenial.


   Add ability to enable or disable network discovery

MAAS now provides the ability to disable the discovery of networks and
devices. By default, discovery is enabled. This setting can be changed
under the Settings page, or via the MAAS CLI and API using the
“network_discovery” configuration key. (Accepted values are “enabled” and
“disabled”.) When discovery is disabled, mDNS records and ARP requests will
no longer be stored in MAAS, and the listening processes on each rack
controller will be shut down.


   New command: maas-rack scan-network [[interface|cidr] [cidr…]]

MAAS now provides a command that can be used to scan networks for
neighbours. Only networks connected to each rack controller will be
scanned. If ‘nmap’ is installed, MAAS will make use of its ARP scanning
capability to quickly scan each attached network. Otherwise, it will fall
back to a slower scan using parallel ‘ping’ requests. Only IPv4 networks
will be scanned.
Bugs fixed


   *Bug #1620514 <http://launchpad.net/bugs/1620514>: [2.1a2] errors during
   network observation processes can result in a process leak*

      Fixes an issue that caused out-of-memory conditions on MAAS racks in
      certain situations, due to too many neighbour discovery processes being
      allowed to spawn concurrently.

Other notable changes


   MAAS new CSS Framework - Vanilla

In MAAS 2.1 alpha 3, MAAS started using the MAAS Vanilla Framework. This
introduces a extensible CSS framework that allow MAAS to follow the same
design patters as other Ubuntu websites and products. The Vanilla framework
is originally produced by the Ubuntu design team, and MAAS has adopted such

Users will see a new refreshed look on their MAAS.

Known issues and workaroundsUnable to cancel the image import.

When downloading images, MAAS will fail to cancel the import of all or any
of the images being imported. MAAS will first download all the images
before the user is able to remove them.



Unable to enable DHCP if NTP server is unresolvable.

If the NTP server(s) are unresolvable, DHCP will fail to enable. This is
because DHCP doesn’t accept DNS names for DHCP’s NTP configuration, and as
such, MAAS tries to resolve the domain before it is able to set it in the



Rack failed to run/register on fresh install

The MAAS Rack Controller is unable to register after a fresh install due to
being unable to parse network interfaces. After manual restart of
maas-rackd, the rack was successfully registered.

   - https://bugs.launchpad.net/maas/+bug/1624693

Ongoing work


   First User Journery - Ability to import SSH Keys

   Device Discovery - WebUI

   Improved IPv6 Support

   MAAS Image Consolidation

   Support for HWE Rolling Kernels

Andres Rodriguez
Engineering Manager, MAAS
Canonical USA, Inc.
Maas-devel mailing list
Modify settings or unsubscribe at: 

Reply via email to