12
MAAS now collects LLDP data on each node during its
13
commissioning cycle. The router to which the node is connected will have
14
its MAC address parsed out of the data and made available for using as a
15
placement constraint (passing connected_to or not_connected_to to the
16
acquire() API call), or you can define tags using expressions such as
17
``//lldp:chassis/lldp:id[@type="mac"]/text() = "20:4e:7f:94:2e:10"``
18
which would tag nodes with a router using that MAC address.
20
New faster installer for nodes.
21
MAAS will now make use of the new Curtin_ installer which is much quicker
22
than the old Debian Installer process. Typically an installation now
23
takes a couple of minutes instead of upwards of 10 minutes. To have a node
24
use the faster installer, add the ``use-fastpath-installer`` tag to it,
25
or click the "Use the fast installer" button on the node page.
27
.. _Curtin: https://launchpad.net/curtin
29
More extensible templates for DHCP, power control, PXE and DNS.
30
Templates supplied for these activities are now all in their own template
31
file that is customisable by the user. The files now generally live under
32
/etc/maas/ rather than embedded in the code tree itself.
37
Reworked ephemeral downloading
38
While there is no end-user visible change, the ephemeral image download
39
process is now driven by a data stream published by Canonical at
40
http://maas.ubuntu.com/images/streams. In the future this will allow end
41
users to use their own customised images by creating their own stream.
42
The configuration for this is now also part of ``pserv.yaml``, obsoleting
43
the maas_import_ephemerals configuration file. The config will be auto-
44
migrated on the first run of the ``maas-import-ephemerals`` script.
46
Improved maas-cli support
47
Users can now manage their SSH keys and API credentials via the maas-cli
51
MAAS is updated to work with Django 1.5
53
Bugs fixed in this release
54
--------------------------
55
#1039513 maas-import-pxe-files doesn't cryptographically verify what
58
#1158425 maas-import-pxe-files sources path-relative config
60
#1204507 MAAS rejects empty files
62
#1208497 netboot flag defaults to 'true' on upgrade, even for allocated
65
#1227644 Releasing a node using the API errors with "TypeError:
66
00:e0:81:dd:d1:0b is not JSON serializable"
68
#1234853 MAAS returns HTTP/500 when adding a second managed interface
71
#971349 With 100% of nodes in 'declared' state, pie chart is white on white
73
#974035 Node listing does not support bulk operations
75
#1045725 SAY clauses in PXE configs are being evaluated as they're
76
encountered, not when the label is branched to
78
#1054518 distro_series can be None or ""
80
#1064777 If a node's IP address is known, it's not shown anywhere
82
#1084807 Users are editing the machine-generated dhcpd.conf
84
#1155607 Conflict between "DNS zone name" in Cluster controller and
85
"Default domain for new nodes" in settings
87
#1172336 MAAS server reference to AvahiBoot wiki page that does not exist
89
#1185160 no way to see what user has a node allocated
91
#1202314 Discrepancy between docs and behavior
93
#1206222 Documentation Feedback and Site suggestions
95
#1209039 Document that MAAS requires 'portfast' on switch ports connected
98
#1215750 No way of tracing/debugging http traffic content in the appserver.
100
#1223157 start_commissioning needlessly sets owner on commissioning nodes
102
#1227081 Error in apache's log "No handlers could be found for logger
105
#1233069 maas-import-pxe-files fails when md5 checksums can't be downloaded
107
#1117415 maas dhcp responses do not have domain-name or domain-search
109
#1136449 maas-cli get-config and set-config documentation
111
#1175405 Pie chart says "deployed" which is inconsistent with the node
114
#1233833 Usability: deleting nodes is too easy
116
#1185897 expose ability to re-commission node in api and cli
118
#997092 Can't delete allocated node even if owned by self
added
removed
docs/changelog.rst
