Merge lp:~julian-edwards/maas/release-notes-1.7 into lp:~maas-committers/maas/trunk

Proposed by Julian Edwards
Status: Merged
Merged at revision: 3266
Proposed branch: lp:~julian-edwards/maas/release-notes-1.7
Merge into: lp:~maas-committers/maas/trunk
Diff against target: 126 lines (+104/-1)
2 files modified
docs/changelog.rst (+102/-0)
docs/conf.py (+2/-1)
To merge this branch: bzr merge lp:~julian-edwards/maas/release-notes-1.7
Reviewer Review Type Date Requested Status
Andres Rodriguez (community) Approve
Review via email: mp+238109@code.launchpad.net
To post a comment you must log in.
Revision history for this message
Jeroen T. Vermeulen (jtv) wrote :

Saying that it's now possible to "deploy nodes using IPv6" may end up being misleading. It is now possible to deploy (Ubuntu) nodes that have IPv6 networking enabled. The actual deployment process still uses IPv4. Or a mix of IPv4 and IPv6, as the case may be.

Revision history for this message
Andres Rodriguez (andreserl) :
review: Approve
Revision history for this message
Graham Binns (gmb) :
Revision history for this message
Raphaël Badin (rvb) :
Revision history for this message
Julian Edwards (julian-edwards) wrote :

On Monday 13 Oct 2014 09:16:48 you wrote:
> Saying that it's now possible to "deploy nodes using IPv6" may end up being
> misleading. It is now possible to deploy (Ubuntu) nodes that have IPv6
> networking enabled. The actual deployment process still uses IPv4. Or a
> mix of IPv4 and IPv6, as the case may be.

Good point, fixed. Thank you.

Revision history for this message
Julian Edwards (julian-edwards) wrote :

> I think s/the syslog/its syslog entries/ would scan better.

You're right, thanks.

Revision history for this message
Julian Edwards (julian-edwards) wrote :

On Monday 13 Oct 2014 13:52:30 you wrote:
> typo: s/psuedo/pseudo.

Extremely well spotted! Thanks.

Revision history for this message
Graham Binns (gmb) wrote :

We should also add a note re: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1379144 to point out that maas-proxy isn't installed by default on upgrade; if you want to use it instead of squid-deb-proxy you need to install it manually (it will remove squid-deb-proxy).

Telling you here rather than working up a branch since this hasn't landed yet :)

Revision history for this message
Blake Rouse (blake-rouse) wrote :

You might want to also include that there is support to deploy custom images, but only the API can be used to upload custom images.

Revision history for this message
Julian Edwards (julian-edwards) wrote :

On Thursday 16 Oct 2014 16:16:45 you wrote:
> You might want to also include that there is support to deploy custom
> images, but only the API can be used to upload custom images.

Will, do, thanks both.

Revision history for this message
Raphaël Badin (rvb) :

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
1=== modified file 'docs/changelog.rst'
2--- docs/changelog.rst 2014-09-15 06:36:06 +0000
3+++ docs/changelog.rst 2014-10-16 01:50:58 +0000
4@@ -2,6 +2,108 @@
5 Changelog
6 =========
7
8+1.7.0
9+=====
10+
11+Major new features
12+------------------
13+
14+Improved image downloading and reporting.
15+ MAAS boot images are now downloaded centrally by the region controller
16+ and disseminated to all registered cluster controllers. This change includes
17+ a new web UI under the `Images` tab that allows the admin to select
18+ which images to import and shows the progress of the ongoing download.
19+ This completely replaces any file-based configuration that used to take
20+ place on cluster controllers. The cluster page now shows whether it has
21+ synchronised all the images from the region controller.
22+
23+ This process is also completely controllable using the API.
24+
25+Note:
26+ Unfortunately due to a format change in the way images are stored, it
27+ was not possible to migrate previously downloaded images to the new region
28+ storage. The cluster(s) will still be able to use the existing images,
29+ however the region controller will be unaware of them until an import
30+ is initiated. When the import is finished, the cluster(s) will remove
31+ older image resources.
32+
33+Increased robustness.
34+ A large amount of effort has been given to ensuring that MAAS remains
35+ robust in the face of adversity. An updated node state model has been
36+ implemented that takes into account more of the situations in which a
37+ node can be found including any failures at each stage.
38+
39+ When a node is getting deployed, it is now monitored to check that each
40+ stage is reached in a timely fashion; if it does not then it is marked
41+ as failed.
42+
43+ The core power driver was updated to check the state of the power on each
44+ node and is reported in the web UI and API. The core driver now also
45+ handles retries when changing the power state of hardware, removing the
46+ requirement that each power template handle it individually.
47+
48+Node event log.
49+ For every major event on nodes, it is now logged in a node-specific log.
50+ This includes events such as power changes, deployments and any failures.
51+
52+IPv6
53+ It is now possible to deploy Ubuntu nodes that have IPv6 enabled.
54+ See :doc:`ipv6` for more details.
55+
56+Removal of Celery and RabbitMQ
57+ While Celery was found to be very reliable it ultimately did not suit
58+ the project's requirements as it is a largely fire-and-forget mechanism.
59+ Additionally it was another moving part that caused some headaches for
60+ users and admins alike, so the decision was taken to remove it and implement
61+ a custom communications mechanism between the region controller and cluster
62+ controllers. The new mechanism is bidirectional and allowed the complex
63+ interactions to take place that are required as part of the robustness
64+ improvements.
65+
66+ Since a constant connection is maintained, as a side effect the web UI now
67+ shows whether each cluster is connected or not.
68+
69+ XXX security for cluster to region
70+
71+Support for other OSes
72+ Non-Ubuntu OSes are fully supported now. This includes:
73+ - Windows
74+ - Centos
75+ - SuSE
76+
77+Minor notable changes
78+---------------------
79+
80+Better handling of networks.
81+ All networks referred to by cluster interfaces are now automatically
82+ registered on the Network page. Any node network interfaces are
83+ automatically linked to the relevant Network.
84+
85+Improved logging.
86+ A total overhaul of where logging is produced was undertaken, and now
87+ all the main events in MAAS are selectively reported to syslog with the
88+ "maas" prefix from both the region and cluster controllers alike. If MAAS
89+ is installed using the standard Ubuntu packaging, its syslog entries are
90+ redirected to /var/log/maas/maas.log.
91+
92+ On the clusters, pserv.log is now less chatty and contains only errors.
93+ On the region controller appservers, maas-django.log contains only appserver
94+ errors.
95+
96+Static IP selection.
97+ The API was extended so that specific IPs can be pre-allocated for network
98+ interfaces on nodes and for user-allocated IPs.
99+
100+Pronounceable random hostnames.
101+ The old auto-generated 5-letter names were replaced with a pseudo-random
102+ name that is produced from a dictionary giving names of the form
103+ 'adjective-noun'.
104+
105+Bugs fixed in this release
106+--------------------------
107+XXX Full milestone list here.
108+
109+
110 1.6.1
111 =====
112
113
114=== modified file 'docs/conf.py'
115--- docs/conf.py 2014-07-18 17:05:57 +0000
116+++ docs/conf.py 2014-10-16 01:50:58 +0000
117@@ -52,7 +52,8 @@
118 # The first item should be the development version.
119 from collections import OrderedDict
120 doc_versions = OrderedDict([
121- ('1.7', 'Development trunk'),
122+ ('dev', 'Development trunk'),
123+ ('1.7', 'MAAS 1.7'),
124 ('1.6', 'MAAS 1.6'),
125 ('1.5', 'MAAS 1.5'),
126 ('1.4', 'MAAS 1.4'),