MAAS 1.6.0
Milestone information
- Active:
- No. Drivers cannot target bugs and blueprints to this milestone.
Activities
- Assigned to you:
- No blueprints or bugs assigned to you.
- Assignees:
- 5 Blake Rouse, 1 Diogo Matsubara, 2 Dustin Kirkland , 1 Gavin Panella, 5 Graham Binns, 2 Jason Hobbs, 7 Jeroen T. Vermeulen, 15 Julian Edwards, 4 Newell Jensen, 13 Raphaël Badin
- Blueprints:
- No blueprints are targeted to this milestone.
- Bugs:
- 55 Fix Released
Download files for this release
Release notes
1.6.0
=====
Special notice:
Cluster interfaces now have static IP ranges in order to give nodes stable
IP addresses. You need to set the range in each interface to turn on this
feature. See below for details.
Major new features
------------------
IP addresses overhaul.
This release contains a total reworking of IP address allocation. You can
now define a separate "static" range in each cluster interface configuration
that is separate from the DHCP server's dynamic range. Any node in use by
a user will receive an IP address from the static range that is guaranteed
not to change during its allocated lifetime. Previously, this was at the
whim of the DHCP server despite MAAS placing host maps in its configuration.
Currently, dynamic IP addresses will continue to receive DNS entries so as
to maintain backward compatibility with installations being upgraded from
1.5. However, this will be changed in a future release to only give
DNS entries to static IPs.
You can also use the API to `reserve IP addresses`_ on a per-user basis.
.. _reserve IP addresses: http://
Support for additional OSes.
MAAS can now install operating systems other than Ubuntu on nodes.
Preliminary beta support exists for CentOS and SuSE via the `Curtin`_ "fast"
installer. This has not been thoroughly tested yet and has been provided
in case anyone finds this useful and is willing to help find and report bugs.
Minor notable changes
-------
DNS entries
In 1.5 DNS entries for nodes were a CNAME record. As of 1.6, they are now
all "A" records, which allows for reliable reverse look-ups.
Only nodes that are allocated to a user and started will receive "A" record
entries. Unallocated nodes no longer have DNS entries.
Removal of bootresources.yaml
The bootresources.yaml file, which had to be configured separately on each
cluster controller, is no longer in use. Instead, the configuration for
which images to download is now held by the region controller, and defaults
to downloading all images for LTS releases. A `rudimentary API`_ is
available to manipulate this configuration.
.. _rudimentary API: http://
Fast installer is now the default
Prevously, the slower Debian installer was used by default. Any newly-
enlisted nodes will now use the newer `fast installer`_. Existing nodes
will keep the installer setting that they already have.
.. _fast installer: https:/
Changelog
This release does not have a changelog.