Merge lp:~julian-edwards/maas/1.7-update-releasenotes into lp:maas/1.7
- 1.7-update-releasenotes
- Merge into 1.7
Proposed by
Julian Edwards
Status: | Merged |
---|---|
Approved by: | Julian Edwards |
Approved revision: | no longer in the source branch. |
Merged at revision: | 3295 |
Proposed branch: | lp:~julian-edwards/maas/1.7-update-releasenotes |
Merge into: | lp:maas/1.7 |
Diff against target: |
737 lines (+333/-172) 4 files modified
INSTALL.txt (+13/-5) docs/changelog.rst (+267/-167) docs/index.rst (+1/-0) docs/sstreams-mirror.rst (+52/-0) |
To merge this branch: | bzr merge lp:~julian-edwards/maas/1.7-update-releasenotes |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Julian Edwards (community) | Approve | ||
Review via email: mp+240196@code.launchpad.net |
Commit message
Straight backport of trunk revisions 3306, 3314 and 3326 which add many improvements to the 1.7.0 release notes.
Description of the change
To post a comment you must log in.
Preview Diff
[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
1 | === modified file 'INSTALL.txt' |
2 | --- INSTALL.txt 2014-10-23 19:34:48 +0000 |
3 | +++ INSTALL.txt 2014-10-31 02:23:22 +0000 |
4 | @@ -232,12 +232,14 @@ |
5 | Import the boot images |
6 | ---------------------- |
7 | |
8 | -MAAS will check for and download new Ubuntu images every hour. On a new |
9 | -installation you'll need to start the import process manually once you have |
10 | -set up your MAAS region. |
11 | +Since version 1.7, MAAS stores the boot images in the region controller's |
12 | +database, from where the cluster controllers will synchronise with the region |
13 | +and pull images from the region to the cluster's local disk. This process |
14 | +is automatic and MAAS will check for and download new Ubuntu images every hour. |
15 | |
16 | -There are two ways to start the import: through the web user interface, or |
17 | -through the remote API. |
18 | +However, on a new installation you'll need to start the import process manually |
19 | +once you have set up your MAAS region controller. There are two ways to start |
20 | +the import: through the web user interface, or through the remote API. |
21 | |
22 | To do it in the web user interface, go to the Images tab, check the boxes to |
23 | say which images you want to import, and click the "Import images" button at |
24 | @@ -274,6 +276,12 @@ |
25 | :doc:`customise boot sources </bootsources>` to see examples on how to do that. |
26 | |
27 | |
28 | +Speeding up repeated image imports by using a local mirror |
29 | +---------------------------------------------------------- |
30 | +See :doc:`sstreams-mirror` for information on how to set up a mirror and |
31 | +configure MAAS to use it. |
32 | + |
33 | + |
34 | Configure DHCP |
35 | -------------- |
36 | |
37 | |
38 | === modified file 'docs/changelog.rst' |
39 | --- docs/changelog.rst 2014-10-17 15:57:03 +0000 |
40 | +++ docs/changelog.rst 2014-10-31 02:23:22 +0000 |
41 | @@ -5,10 +5,46 @@ |
42 | 1.7.0 |
43 | ===== |
44 | |
45 | +Important announcements |
46 | +----------------------- |
47 | + |
48 | +**Re-import your boot images** |
49 | + You must re-import your boot images, see below for details. |
50 | + |
51 | +**Update Curtin preseed files** |
52 | + Two changes were made to Curtin preseed files that need your attention |
53 | + if you made any customisations: |
54 | + |
55 | + * The OS name must now appear in the filename. The new schema is shown |
56 | + here, each file pattern is tried in turn until a match is found:: |
57 | + |
58 | + {prefix}_{osystem}_{node_arch}_{node_subarch}_{release}_{node_name} |
59 | + {prefix}_{osystem}_{node_arch}_{node_subarch}_{release} |
60 | + {prefix}_{osystem}_{node_arch}_{node_subarch} |
61 | + {prefix}_{osystem}_{node_arch} |
62 | + {prefix}_{osystem} |
63 | + {prefix} |
64 | + |
65 | + * If you are modifying ``/etc/network/interfaces`` in the preseed, it must be |
66 | + moved so it is processed last in ``late_commands`` since MAAS now writes |
67 | + to this file itself as part of IPv6 setup. For example:: |
68 | + |
69 | + late_commands: |
70 | + bonding_02: ["curtin", "in-target", "--", "wget", "-O", "/etc/network/interfaces", "http://[...snip...]"] |
71 | + |
72 | + must now look like this:: |
73 | + |
74 | + late_commands: |
75 | + zz_write_ifaces: ["curtin", "in-target", "--", "wget", "-O", "/etc/network/interfaces", "http://[...snip...]"] |
76 | + |
77 | + The leading ``zz`` ensures the command sorts to the end of the |
78 | + ``late_commands`` list. |
79 | + |
80 | + |
81 | Major new features |
82 | ------------------ |
83 | |
84 | -Improved image downloading and reporting. |
85 | +**Improved image downloading and reporting.** |
86 | MAAS boot images are now downloaded centrally by the region controller |
87 | and disseminated to all registered cluster controllers. This change includes |
88 | a new web UI under the `Images` tab that allows the admin to select |
89 | @@ -19,7 +55,7 @@ |
90 | |
91 | This process is also completely controllable using the API. |
92 | |
93 | -Note: |
94 | +.. Note:: |
95 | Unfortunately due to a format change in the way images are stored, it |
96 | was not possible to migrate previously downloaded images to the new region |
97 | storage. The cluster(s) will still be able to use the existing images, |
98 | @@ -30,7 +66,7 @@ |
99 | This means that the first thing to do after upgrading to 1.7 is go to the |
100 | `Images` tab and re-import the images. |
101 | |
102 | -Increased robustness. |
103 | +**Increased robustness.** |
104 | A large amount of effort has been given to ensuring that MAAS remains |
105 | robust in the face of adversity. An updated node state model has been |
106 | implemented that takes into account more of the situations in which a |
107 | @@ -45,7 +81,7 @@ |
108 | handles retries when changing the power state of hardware, removing the |
109 | requirement that each power template handle it individually. |
110 | |
111 | -RPC security. |
112 | +**RPC security.** |
113 | As a step towards mutually verified TLS connections between MAAS's |
114 | components, 1.7 introduces a simple shared-secret mechanism to |
115 | authenticate the region with the clusters and vice-versa. For those |
116 | @@ -67,7 +103,7 @@ |
117 | That's it; the upgraded cluster controller will find the secret |
118 | without needing to be told. |
119 | |
120 | -RPC connections. |
121 | +**RPC connections.** |
122 | Each cluster maintains a persistent connection to each region |
123 | controller process that's running. The ports on which the region is |
124 | listening are all high-numbered, and they are allocated randomly by |
125 | @@ -75,15 +111,15 @@ |
126 | each cluster controller needs unfiltered access to each machine in the |
127 | region on all high-numbered TCP ports. |
128 | |
129 | -Node event log. |
130 | +**Node event log.** |
131 | For every major event on nodes, it is now logged in a node-specific log. |
132 | This includes events such as power changes, deployments and any failures. |
133 | |
134 | -IPv6. |
135 | +**IPv6.** |
136 | It is now possible to deploy Ubuntu nodes that have IPv6 enabled. |
137 | See :doc:`ipv6` for more details. |
138 | |
139 | -Removal of Celery and RabbitMQ. |
140 | +**Removal of Celery and RabbitMQ.** |
141 | While Celery was found to be very reliable it ultimately did not suit |
142 | the project's requirements as it is a largely fire-and-forget mechanism. |
143 | Additionally it was another moving part that caused some headaches for |
144 | @@ -96,18 +132,18 @@ |
145 | Since a constant connection is maintained, as a side effect the web UI now |
146 | shows whether each cluster is connected or not. |
147 | |
148 | -Support for other OSes. |
149 | +**Support for other OSes.** |
150 | Non-Ubuntu OSes are fully supported now. This includes: |
151 | - Windows |
152 | - Centos |
153 | - SuSE |
154 | |
155 | -Custom Images. |
156 | +**Custom Images.** |
157 | MAAS now supports the deployment of Custom Images. Custom images can be |
158 | uploaded via the API. The usage of custom images allows the deployment of |
159 | other Ubuntu Flavors, such as Ubuntu Desktop. |
160 | |
161 | -maas-proxy. |
162 | +**maas-proxy.** |
163 | MAAS now uses maas-proxy as the default proxy solution instead of |
164 | squid-deb-proxy. On a fresh install, MAAS will use maas-proxy by default. |
165 | On upgrades from previous releases, MAAS will install maas-proxy instead of |
166 | @@ -116,12 +152,23 @@ |
167 | Minor notable changes |
168 | --------------------- |
169 | |
170 | -Better handling of networks. |
171 | +**Better handling of networks.** |
172 | All networks referred to by cluster interfaces are now automatically |
173 | registered on the Network page. Any node network interfaces are |
174 | automatically linked to the relevant Network. |
175 | |
176 | -Improved logging. |
177 | +.. Note:: |
178 | + Commissioning currently requires an IP address to be available for each |
179 | + network interface on a network that MAAS manages; this allows MAAS to |
180 | + auto-populate its networks database. In general you should use a |
181 | + well-sized network (/16 recommended if you will be using containers and |
182 | + VMs) and dynamic pool. If this feature risks causing IP exhaustion for |
183 | + your deployment and you do not need the auto-populate functionality, you |
184 | + can disable it by running the following command on your region controller:: |
185 | + |
186 | + sudo maas <profile> maas set-config name=enable_dhcp_discovery_on_unconfigured_interfaces value=False |
187 | + |
188 | +**Improved logging.** |
189 | A total overhaul of where logging is produced was undertaken, and now |
190 | all the main events in MAAS are selectively reported to syslog with the |
191 | "maas" prefix from both the region and cluster controllers alike. If MAAS |
192 | @@ -132,238 +179,296 @@ |
193 | On the region controller appservers, maas-django.log contains only appserver |
194 | errors. |
195 | |
196 | -Static IP selection. |
197 | +**Static IP selection.** |
198 | The API was extended so that specific IPs can be pre-allocated for network |
199 | interfaces on nodes and for user-allocated IPs. |
200 | |
201 | -Pronounceable random hostnames. |
202 | +**Pronounceable random hostnames.** |
203 | The old auto-generated 5-letter names were replaced with a pseudo-random |
204 | name that is produced from a dictionary giving names of the form |
205 | 'adjective-noun'. |
206 | |
207 | -Bugs fixed in this release |
208 | --------------------------- |
209 | + |
210 | +Known Problems & Workarounds |
211 | +---------------------------- |
212 | + |
213 | +**Upgrade issues** |
214 | + There may be upgrade issues for users currently on MAAS 1.5 and 1.6; while we |
215 | + have attempted to reproduce and address all the issues reported, some bugs |
216 | + remain inconclusive. We recommend a full, tested backup of the MAAS servers |
217 | + before attempting the upgrade to 1.7. If you do encounter issues, please file |
218 | + these and flag them to the attention of the MAAS team and we will address them |
219 | + in point-releases. See bugs `1381058`_, `1382266`_, `1379890`_, `1379532`_, |
220 | + and `1379144`_. |
221 | + |
222 | +.. _1381058: |
223 | + https://launchpad.net/bugs/1381058 |
224 | +.. _1382266: |
225 | + https://launchpad.net/bugs/1382266 |
226 | +.. _1379890: |
227 | + https://launchpad.net/bugs/1379890 |
228 | +.. _1379532: |
229 | + https://launchpad.net/bugs/1379532 |
230 | +.. _1379144: |
231 | + https://launchpad.net/bugs/1379144 |
232 | + |
233 | +**Split Region/Cluster set-ups** |
234 | + If you site your cluster on a separate host to the region, it needs a |
235 | + security key to be manually installed by running |
236 | + ``maas-provision install-shared-secret`` on the cluster host. |
237 | + |
238 | +**Private boot streams** |
239 | + If you had private boot image stream information configured in MAAS 1.5 or |
240 | + 1.6, upgrading to 1.7 will not take that into account and it will need to be |
241 | + manually entered on the settings page in the MAAS UI (bug `1379890`_) |
242 | + |
243 | +.. _1379890: |
244 | + https://launchpad.net/bugs/1379890 |
245 | + |
246 | +**Concurrency issues** |
247 | + Concurrency issues expose us to races when simultaneous operations are |
248 | + triggered. This is the source of many hard to reproduce issues which will |
249 | + require us to change the default database isolation level. We intend to address |
250 | + this in the first point release of 1.7. |
251 | + |
252 | +**Destroying a Juju environment** |
253 | + When attempting to "juju destroy" an environment, nodes must be in the DEPLOYED |
254 | + state; otherwise, the destroy will fail. You should wait for all in-progress |
255 | + actions on the MAAS cluster to conclude before issuing the command. (bug |
256 | + `1381619`_) |
257 | + |
258 | +.. _1381619: |
259 | + https://launchpad.net/bugs/_1381619 |
260 | + |
261 | +**AMT power control** |
262 | + A few AMT-related issues remain, with workarounds: |
263 | + |
264 | + * Commissioning NUC reboots instead of shutting down (bug `1368685`_). There |
265 | + is `a workaround in the power template`_ |
266 | + |
267 | + * MAAS (amttool) cannot control AMT version > 8. See `workaround described in |
268 | + bug 1331214`_ |
269 | + |
270 | + * AMT NUC stuck at boot prompt instead of powering down (no ACPI support in |
271 | + syslinux poweroff) (bug `1376716`_). See the `ACPI-only workaround`_ |
272 | + |
273 | +.. _1368685: |
274 | + https://bugs.launchpad.net/maas/+bug/1368685 |
275 | +.. _a workaround in the power template: |
276 | + https://bugs.launchpad.net/maas/+bug/1368685/comments/8 |
277 | +.. _workaround described in bug 1331214: |
278 | + https://bugs.launchpad.net/maas/+bug/1331214/comments/18 |
279 | +.. _1376716: |
280 | + https://bugs.launchpad.net/maas/+bug/1376716 |
281 | +.. _ACPI-only workaround: |
282 | + https://bugs.launchpad.net/maas/+bug/1376716/comments/12 |
283 | + |
284 | + |
285 | +**Disk wiping** |
286 | + If you enable disk wiping, juju destroy-environment may fail for you. The |
287 | + current workaround is to wait and re-issue the command. This will be fixed in |
288 | + future versions of MAAS & Juju. (bug `1386327`_) |
289 | + |
290 | +.. _1386327: |
291 | + https://bugs.launchpad.net/maas/+bug/1386327 |
292 | + |
293 | +**BIND with DNSSEC** |
294 | + If you are using BIND with a forwarder that uses DNSSEC and have not |
295 | + configured certificates, you will need to explicitly disable that feature in |
296 | + your BIND configuration (1384334) |
297 | + |
298 | +.. _1384334: |
299 | + https://bugs.launchpad.net/maas/+bug/1384334 |
300 | + |
301 | +**Boot source selections on the API** |
302 | + Use of API to change image selections can leave DB in a bad state |
303 | + (bug `1376812`_). It can be fixed by issuing direct database updates. |
304 | + |
305 | +.. _1376812: |
306 | + https://bugs.launchpad.net/maas/+bug/1376812 |
307 | + |
308 | +**Disabling DNS** |
309 | + Disabling DNS may not work (bug `1383768`_) |
310 | + |
311 | +.. _1383768: |
312 | + https://bugs.launchpad.net/maas/+bug/1383768 |
313 | + |
314 | +**Stale DNS zone files** |
315 | + Stale DNS zone files may be left behind if the MAAS domainname is changed |
316 | + (bug `1383329`_) |
317 | + |
318 | +.. _1383329: |
319 | + https://bugs.launchpad.net/maas/+bug/1383329 |
320 | + |
321 | + |
322 | + |
323 | +Major bugs fixed in this release |
324 | +-------------------------------- |
325 | + |
326 | +See https://launchpad.net/maas/+milestone/1.7.0 for full details. |
327 | + |
328 | #1081660 If maas-enlist fails to reach a DNS server, the node will be named ";; connection timed out; no servers could be reached" |
329 | + |
330 | #1087183 MaaS cloud-init configuration specifies 'manage_etc_hosts: localhost' |
331 | + |
332 | #1328351 ConstipationError: When the cluster runs the "import boot images" task it blocks other tasks |
333 | -#1340208 DoesNotExist: NodeGroupInterface has no nodegroup |
334 | -#1340896 MAAS upgrade from 1.5.2+bzr2282-0ubuntu0.2 to experiment failed |
335 | + |
336 | #1342117 CLI command to set up node-group-interface fails with /usr/lib/python2.7/dist-packages/maascli/__main__.py: error: u'name' |
337 | -#1342395 power_on: ipmi failed: name 'power_off_mode' is not defined at line 12 column 18 in file /etc/maas/templates/power/ipmi.template |
338 | -#1347579 Schema migration 0091 is broken (node boot type) |
339 | + |
340 | #1349254 Duplicate FQDN can be configured on MAAS via CLI or API |
341 | + |
342 | #1352575 BMC password showing in the apache2 logs |
343 | -#1353598 maas-import-pxe-files logger import error for logger |
344 | -#1355014 Can't run tests without a net connection |
345 | + |
346 | #1355534 UnknownPowerType traceback in appserver log |
347 | -#1356788 Test failure: “One or more services are registered” etc. |
348 | -#1359029 Power status monitoring does not scale |
349 | -#1359517 Periodic DHCP probe breaks: "Don't log exceptions to maaslog" |
350 | -#1359551 create_Network_from_NodeGroupInterface is missing a catch for IntegrityError |
351 | -#1360004 UI becomes unresponsive (unaccessible) if RPC to cluster fails |
352 | -#1360008 Data migration fails with django.db.utils.InternalError: current transaction is aborted, commands ignored until end of transaction block |
353 | -#1360676 KeyError raised importing boot images |
354 | -#1361799 absolute_reverse returns incorrect url if base_url is missing ending / |
355 | -#1362397 django.core.exceptions.ValidationError: {'power_state': [u'Ensure this value has at most 10 characters (it has 18).']} |
356 | -#1363105 Change in absolute_reverse breaks netbooting on installed MAAS |
357 | -#1363116 DHCP Probe timer service fails |
358 | -#1363138 DHCP Probe TimerService fails with 'NoneType' object has no attribute 'encode' |
359 | -#1363474 exceptions.KeyError: u'subarches' when syncing uploaded image from region to cluster |
360 | -#1363525 preseed path for generated tgz doesn't match actual path |
361 | -#1363722 Boot resource upload failed: error: length too large |
362 | + |
363 | #1363850 Auto-enlistment not reporting power parameters |
364 | + |
365 | #1363900 Dev server errors while trying to write to '/var/lib/maas' |
366 | + |
367 | #1363999 Not assigning static IP addresses |
368 | -#1364062 New download boot resources method doesn't use the configured proxy |
369 | + |
370 | #1364481 http 500 error doesn't contain a stack trace |
371 | + |
372 | #1364993 500 error when trying to acquire a commissioned node (AddrFormatError: failed to detect a valid IP address from None) |
373 | + |
374 | #1365130 django-admin prints spurious messages to stdout, breaking scripts |
375 | -#1365175 bootloader import code goes directly to archive.ubuntu.com rather than the configured archive |
376 | + |
377 | #1365850 DHCP scan using cluster interface name as network interface? |
378 | -#1366104 [FFe] OperationError when large object greater than 2gb |
379 | + |
380 | #1366172 NUC does not boot after power off/power on |
381 | + |
382 | #1366212 Large dhcp leases file leads to tftp timeouts |
383 | + |
384 | #1366652 Leaking temporary directories |
385 | -#1366726 CI breakage: Deployed nodes don't get a static IP address |
386 | + |
387 | #1368269 internal server error when deleting a node |
388 | + |
389 | #1368590 Power actions are not serialized. |
390 | + |
391 | #1370534 Recurrent update of the power state of nodes crashes if the connection to the BMC fails. |
392 | + |
393 | #1370958 excessive pserv logging |
394 | -#1371033 A node can get stuck in the 'RELEASING' state if the power change command fails to power down the node. |
395 | -#1371064 Spurious test failure: maasserver.rpc.tests.test_nodes.TestCreateNode.test_creates_node |
396 | -#1371236 power parameters for probe-and-enlist mscm no longer saved for enlisted nodes |
397 | -#1372408 PowerQuery RPC method crashes with exceptions.TypeError: get_power_state() got an unexpected keyword argument 'power_change' |
398 | -#1372732 ImportError running src/metadataserver/tests/test_fields.py |
399 | -#1372735 Deprecation warning breaks Node model tests |
400 | + |
401 | #1372767 Twisted web client does not support IPv6 address |
402 | + |
403 | #1372944 Twisted web client fails looking up IPv6 address hostname |
404 | + |
405 | #1373031 Cannot register cluster |
406 | + |
407 | #1373103 compose_curtin_network_preseed breaks installation of all other operating systems |
408 | -#1373207 Can't build package |
409 | -#1373237 maas-cluster-controller installation breaks: __main__.py: error: unrecognized arguments: -u maas -g maas |
410 | -#1373265 Where did the “Import boot images” button go? |
411 | -#1373357 register_event_type fails: already exists |
412 | + |
413 | #1373368 Conflicting power actions being dropped on the floor can result in leaving a node in an inconsistent state |
414 | -#1373477 Circular import between preseed.py and models/node.py |
415 | -#1373658 request_node_info_by_mac_address errors during enlistment: MACAddress matching query does not exist |
416 | + |
417 | #1373699 Cluster Listing Page lacks feedback about the images each cluster has |
418 | -#1373710 Machines fail to PXE Boot |
419 | + |
420 | #1374102 No retries for AMT power? |
421 | -#1374388 UI checkbox for Node.disable_ipv4 never unchecks |
422 | -#1374793 Cluster page no longer shows whether the cluster is connected or not. |
423 | -#1375594 After a fresh install, cluster can't connect to region |
424 | -#1375664 Node powering on but not deploying |
425 | -#1375835 Can't create node in the UI with 1.7 beta 4 |
426 | -#1375970 Timeout leads to inconsistency between maas and real world state, can't commission or start nodes |
427 | + |
428 | #1375980 Nodes failed to transition out of "New" state on bulk commission |
429 | -#1376000 oops: 'NoneType' object has no attribute 'encode' |
430 | + |
431 | #1376023 After performing bulk action on maas nodes, Internal Server Error |
432 | -#1376028 maasserver Unable to identify boot image for (ubuntu/amd64/generic/trusty/poweroff): cluster 'maas' does not have matching boot image. |
433 | -#1376031 WebUI became unresponsive after disconnecting Remote Cluster Controller (powered node off) |
434 | -#1376303 Can't commission a node: xceptions.AttributeError: 'NoneType' object has no attribute 'addCallback' |
435 | -#1376304 Timeout errors in RPC commands cause 500 errors |
436 | -#1376782 Node stuck with: "another action is already in progress for that node." |
437 | + |
438 | #1376888 Nodes can't be deleted if DHCP management is off. |
439 | + |
440 | #1377099 Bulk operation leaves nodes in inconsistent state |
441 | -#1377860 Nodes not configured with IPv6 DNS server address |
442 | -#1379154 "boot-images" link in the "Visit the boot images page to start the import." is a 404 |
443 | + |
444 | #1379209 When a node has multiple interfaces on a network MAAS manages, MAAS assigns static IP addresses to all of them |
445 | -#1379568 maas-cluster fails to register if the host has an IPv6 address |
446 | -#1379591 nodes with two interfaces fail to deploy in maas 1.7 beta5 |
447 | -#1379641 IPv6 netmasks aren't *always* 64 bits, but we only configure 64-bit ones |
448 | -#1379649 Invalid transition - 'Releasing Failed' to 'Disk Erasing' |
449 | + |
450 | #1379744 Cluster registration is fragile and insecure |
451 | -#1379924 maas 1.7 flooded with OOPSs |
452 | -#1380927 Default Cluster does not autoconnect after a fresh install |
453 | + |
454 | #1380932 MAAS does not cope with changes of the dhcp daemons |
455 | + |
456 | #1381605 Not all the DNS records are being added when deploying multiple nodes |
457 | -#1381714 Nodes release API bypasses disk erase |
458 | + |
459 | #1012954 If a power script fails, there is no UI feedback |
460 | -#1057250 TestGetLongpollContext.test_get_longpoll_context is causing test failures in metadataserver |
461 | + |
462 | #1186196 "Starting a node" has different meanings in the UI and in the API. |
463 | + |
464 | #1237215 maas and curtin do not indicate failure reasonably |
465 | + |
466 | #1273222 MAAS doesn't check return values of power actions |
467 | + |
468 | #1288502 archive and proxy settings not honoured for commissioning |
469 | -#1300554 If the rabbit password changes, clusters are not informed |
470 | -#1315161 cannot deploy Windows |
471 | + |
472 | #1316919 Checks don't exist to confirm a node will actually boot |
473 | + |
474 | #1321885 IPMI detection and automatic setting fail in ubuntu 14.04 maas |
475 | + |
476 | #1325610 node marked "Ready" before poweroff complete |
477 | + |
478 | #1325638 Add hardware enablement for Universal Management Gateway |
479 | -#1333954 global registry of license keys |
480 | -#1334963 Nodegroupinterface.clean_ip_ranges() is very slow with large networks |
481 | -#1337437 [SRU] maas needs utopic support |
482 | -#1338169 Non-Ubuntu preseed templates are not tested |
483 | -#1339868 No way to list supported operating systems via RPC |
484 | -#1339903 No way to validate an OS license key via RPC |
485 | + |
486 | #1340188 unallocated node started manually, causes AssertionError for purpose poweroff |
487 | -#1340305 No way to get the title for a release from OperatingSystem |
488 | + |
489 | #1341118 No feedback when IPMI credentials fail |
490 | + |
491 | #1341121 No feedback to user when cluster is not running |
492 | + |
493 | #1341581 power state is not represented in api and ui |
494 | -#1341619 NodeGroupInterface is not linked to Network |
495 | -#1341772 No way to get extra preseed data from OperatingSystem via RPC |
496 | + |
497 | #1341800 MAAS doesn't support soft power off through the API |
498 | -#1343425 deprecate use-fastpath-installer tag and use a property on node instead |
499 | + |
500 | #1344177 hostnames can't be changed while a node is acquired |
501 | + |
502 | #1347518 Confusing error message when API key is wrong |
503 | + |
504 | #1349496 Unable to request a specific static IP on the API |
505 | + |
506 | #1349736 MAAS logging is too verbose and not very useful |
507 | + |
508 | #1349917 guess_server_address() can return IPAddress or hostname |
509 | + |
510 | #1350103 No support for armhf/keystone architecture |
511 | + |
512 | #1350856 Can't constrain acquisition of nodes by not having a tag |
513 | -#1350948 IPMI power template treats soft as an option rather than a command |
514 | -#1354014 clusters should sync boot images from the region |
515 | -#1356490 Metadataserver api needs tests for _store_installing_results |
516 | -#1356780 maaslog items are logged twice |
517 | + |
518 | #1356880 MAAS shouldn't allow changing the hostname of a deployed node |
519 | -#1357071 When a power template fails, the content of the event from the node event log is not readable (it contains the whole template) |
520 | -#1357685 docs/bootsources.rst:: WARNING: document isn't included in any toctree |
521 | + |
522 | #1357714 Virsh power driver does not seem to work at all |
523 | -#1358177 maas-region-admin requires root privileges [docs] |
524 | -#1358337 [docs] MAAS documentation suggests to execute 'juju --sync-tools' |
525 | -#1358829 IPMI power query fails when trying to commit config changes |
526 | + |
527 | #1358859 Commissioning output xml is hard to understand, would be nice to have yaml as an output option. |
528 | + |
529 | #1359169 MAAS should handle invalid consumers gracefully |
530 | + |
531 | #1359822 Gateway is missing in network definition |
532 | -#1361897 exceptions in PeriodicImageDownloadService will cause it to stop running |
533 | -#1361941 erlang upgrade makes maas angry |
534 | -#1361967 NodePowerMonitorService has no tests |
535 | + |
536 | #1363913 Impossible to remove last MAC from network in UI |
537 | + |
538 | #1364228 Help text for node hostname is wrong |
539 | + |
540 | #1364591 MAAS Archive Mirror does not respect non-default port |
541 | -#1364617 ipmipower returns a zero exit status when password invalid |
542 | -#1364713 selenium test will not pass with new Firefox |
543 | + |
544 | #1365616 Non-admin access to cluster controller config |
545 | + |
546 | #1365619 DNS should be an optional field in the network definition |
547 | -#1365722 NodeStateViolation when commissioning |
548 | -#1365742 Logged OOPS ... NoSuchEventType: Event type with name=NODE_POWER_ON_FAILED could not be found. |
549 | + |
550 | #1365776 commissioning results view for a node also shows installation results |
551 | + |
552 | #1366812 Old boot resources are not being removed on clusters |
553 | + |
554 | #1367455 MAC address for node's IPMI is reversed looked up to yield IP address using case sensitive comparison |
555 | -#1368398 Can't mark systems that 'Failed commissioning' as 'Broken' |
556 | -#1368916 No resources found in Simplestreams repository |
557 | -#1370860 Node power monitor doesn't cope with power template answers other than "on" or "off" |
558 | -#1370887 No event is registered on a node for when the power monitor sees a problem |
559 | -#1371663 Node page Javascript crashes when there is no lshw output to display yet |
560 | -#1371763 Need to use RPC for validating license key. |
561 | -#1372974 No "installation complete" event |
562 | -#1373272 "No boot images are available.…" message doesn't disappear when images are imported |
563 | + |
564 | #1373580 [SRU] Glen m700 cartridge list as ARM64/generic after enlist |
565 | + |
566 | #1373723 Releasing a node without power parameters ends up in not being able to release a node |
567 | -#1373727 PXE node event logs provide too much info |
568 | -#1373900 New install of MAAS can't download boot images |
569 | -#1374153 Stuck in "power controller problem" |
570 | -#1374321 Internal server error when attempting to perform an action when the cluster is down |
571 | -#1375360 Automatic population of managed networks for eth1 and beyond |
572 | -#1375427 Need to remove references to older import images button |
573 | -#1375647 'static-ipaddresses' capability in 1.6 not documented. |
574 | -#1375681 "Importing images . . ." message on the image page never disappears |
575 | -#1375953 bootsourcecache is not refreshed when sources change |
576 | -#1376016 MAAS lacks a setting for the Simple Streams Image repository location |
577 | -#1376481 Wrong error messages in UI |
578 | -#1376620 maas-url config question doesn't make clear that localhost won't do |
579 | -#1376990 Elusive JavaScript lint |
580 | -#1378366 When there are no images, clusters should show that there |
581 | -#1378527 Images UI doesn't handle HWE images |
582 | -#1378643 Periodic test failure for compose_curtin_network_preseed_for |
583 | -#1378837 "Abort operation" action name is vague and misleading |
584 | -#1378910 Call the install log 'install log' rather than 'curtin log' |
585 | -#1379401 Race in EventManager.register_event_and_event_type |
586 | -#1379816 disable_ipv4 has a default setting on the cluster, but it's not visible |
587 | -#1380470 Event log says node was allocated but doesn't say to *whom* |
588 | -#1380805 uprade from 1.5.4 to 1.7 overwrote my cluster name |
589 | -#1381007 "Acquire and start node" button appears on node page for admins who don't own an allocated but unstarted node |
590 | -#1381213 mark_fixed should clear the osystem and distro_series fields |
591 | -#1381747 APIRPCErrorsMiddleware isn't installed |
592 | -#1381796 license_key is not given in the curtin_userdata preseed for Windows |
593 | -#1172773 Web UI has no indication of image download status. |
594 | + |
595 | #1233158 no way to get power parameters in api |
596 | + |
597 | #1319854 `maas login` tells you you're logged in successfully when you're not |
598 | -#1351451 Impossible to release a BROKEN node via the API. |
599 | -#1361040 Weird log message: "Power state has changed from unknown to connection timeout." |
600 | -#1366170 Node Event log doesn't currently display anything apart from power on/off |
601 | + |
602 | #1368480 Need API to gather image metadata across all of MAAS |
603 | -#1370306 commissioning output XML and YAML tabs are not vertical |
604 | -#1371122 WindowsBootMethod request pxeconfig from API for every file |
605 | -#1376030 Unable to get RPC connection for cluster 'maas' <-- 'maas' is the DNS zone name |
606 | -#1378358 Missing images warning should contain a link to images page |
607 | + |
608 | #1281406 Disk/memory space on Node edit page have no units |
609 | + |
610 | #1299231 MAAS DHCP/DNS can't manage more than a /16 network |
611 | + |
612 | #1357381 maas-region-admin createadmin shows error if not params given |
613 | -#1357686 Caching in get_worker_user() looks like premature optimisation |
614 | -#1358852 Tons of Linking <mac address> to <cluster interface> spam in log |
615 | -#1359178 Docs - U1 still listed for uploading data |
616 | -#1359947 Spelling Errors/Inconsistencies with MAAS Documentation |
617 | -#1365396 UI: top link to “<name> MAAS” only appears on some pages |
618 | -#1365591 "Start node" UI button does not allocate node before starting in 1.7 |
619 | -#1365603 No "stop node" button on the page of a node with status "failed deployment" |
620 | -#1371658 Wasted space in the "Discovery data" section of the node page |
621 | + |
622 | #1376393 powerkvm boot loader installs even when not needed |
623 | -#1376956 commissioning results page with YAML/XML output tabs are not centered on page. |
624 | + |
625 | #1287224 MAAS random generated hostnames are not pronounceable |
626 | + |
627 | #1348364 non-maas managed subnets cannot query maas DNS |
628 | -#1381543 Disabling Disk Erasing with node in 'Failed Erasing' state leads to Invalid transition: Failed disk erasing -> Ready. |
629 | + |
630 | |
631 | 1.6.1 |
632 | ===== |
633 | @@ -453,30 +558,25 @@ |
634 | #1322606 maas-import-pxe-files fails when run from the command line |
635 | #1324237 call_and_check does not report error output |
636 | #1328659 import_boot_images task fails on utopic |
637 | -#1332596 AddrFormatError: failed to detect a valid IP address from None execu |
638 | -ting upload_dhcp_leases task |
639 | +#1332596 AddrFormatError: failed to detect a valid IP address from None executing upload_dhcp_leases task |
640 | #1250370 "sudo maas-import-ephemerals" steps on ~/.gnupg/pubring.gpg |
641 | -#1250435 CNAME record leaks into juju's private-address, breaks host based ac |
642 | -cess control |
643 | +#1250435 CNAME record leaks into juju's private-address, breaks host based access control |
644 | #1305758 Import fails while writing maas.meta: No such file or directory |
645 | #1308292 Unhelpful error when re-enlisting a previously enlisted node |
646 | #1309601 maas-enlist prints "successfully enlisted" even when enlistment fail |
647 | s. |
648 | #1309729 Fast path installer is not the default |
649 | -#1310844 find_ip_via_arp() results in unpredictable, and in some cases, incor |
650 | -rect IP addresses |
651 | +#1310844 find_ip_via_arp() results in unpredictable, and in some cases, incorrect IP addresses |
652 | #1310846 amt template gives up way too easily |
653 | #1312863 MAAS fails to detect SuperMicro-based server's power type |
654 | #1314536 Copyright date in web UI is 2012 |
655 | #1315160 no support for different operating systems |
656 | #1316627 API needed to allocate and return an extra IP for a container |
657 | #1323291 Can't re-commission a commissioning node |
658 | -#1324268 maas-cli 'nodes list' or 'node read <system_id>' doesn't display the |
659 | - osystem or distro_series node fields |
660 | +#1324268 maas-cli 'nodes list' or 'node read <system_id>' doesn't display the osystem or distro_series node fields |
661 | #1325093 install centos using curtin |
662 | #1325927 YUI.Array.each not working as expected |
663 | -#1328656 MAAS sends multiple stop_dhcp_server tasks even though there's no dh |
664 | -cp server running. |
665 | +#1328656 MAAS sends multiple stop_dhcp_server tasks even though there's no dhcp server running. |
666 | #1331139 IP is inconsistently capitalized on the 'edit a cluster interface' p |
667 | age |
668 | #1331148 When editing a cluster interface, last 3 fields are unintuitive |
669 | |
670 | === modified file 'docs/index.rst' |
671 | --- docs/index.rst 2014-10-23 19:34:48 +0000 |
672 | +++ docs/index.rst 2014-10-31 02:23:22 +0000 |
673 | @@ -59,6 +59,7 @@ |
674 | bootsources |
675 | nodes |
676 | hardware-enablement-kernels |
677 | + sstreams-mirror |
678 | networks |
679 | kernel-options |
680 | installing-ubuntu |
681 | |
682 | === added file 'docs/sstreams-mirror.rst' |
683 | --- docs/sstreams-mirror.rst 1970-01-01 00:00:00 +0000 |
684 | +++ docs/sstreams-mirror.rst 2014-10-31 02:23:22 +0000 |
685 | @@ -0,0 +1,52 @@ |
686 | +Local Mirroring of Boot Images |
687 | +============================== |
688 | + |
689 | +Boot images are delivered to MAAS via the simplestreams protocol. It is |
690 | +useful in some situations, such as testing, to mirror the images locally |
691 | +so that you don't need to repeatedly pull them down over a slower Internet |
692 | +link. |
693 | + |
694 | +First, install the required packages on the host where you wish to store |
695 | +the mirrored images:: |
696 | + |
697 | + $ sudo apt-get install simplestreams ubuntu-cloudimage-keyring apache2 |
698 | + |
699 | +Now you can pull the images over using the mirroring tools for simplestreams. |
700 | +This example gets the daily trusty (14.04) and precise (12.04) images for the |
701 | +amd64/generic and amd64/hwe-t architectures:: |
702 | + |
703 | + $ sudo sstream-mirror --keyring=/usr/share/keyrings/ubuntu-cloudimage-keyring.gpg http://maas.ubuntu.com/images/ephemeral-v2/daily/ /var/www/html/maas/images/ephemeral-v2/daily 'arch=amd64' 'subarch~(generic|hwe-t)' 'release~(trusty|precise)' --max=1 |
704 | + |
705 | +This may take a while as hundreds of megabytes will be downloaded. |
706 | + |
707 | +The images will be written to the local disk and you can verify their |
708 | +presence by browsing to |
709 | +``http://<server>/maas/images/ephemeral-v2/daily/streams/v1/index.sjson`` |
710 | +(replace ``<server>`` with your own server's name). |
711 | + |
712 | +It is a good idea to configure a ``cron`` job to repeat this import on a |
713 | +regular basis to keep your mirror up-to-date. |
714 | + |
715 | + |
716 | +Configuring MAAS to use the local mirror |
717 | +---------------------------------------- |
718 | + |
719 | +You can do this using the API or the web UI. To do this via the API you |
720 | +can use the ``maas`` (see :doc:`maascli`) command, logged in as the admin |
721 | +user:: |
722 | + |
723 | + $ maas <profile> boot-sources create url=http://<server>keyring_filename=/usr/share/keyrings/ubuntu-cloudimage-keyring.gpg |
724 | + |
725 | +And then initiate the download with:: |
726 | + |
727 | + $ maas <profile> boot-resources import |
728 | + |
729 | +See :doc:`bootsources` for more detail. |
730 | + |
731 | +In the web UI, browse to the Settings tab as the admin user and scroll down |
732 | +to the "Boot Images" section. There you will find input boxes for the |
733 | +Sync URL and the keyring path, which should be set as the values in the API |
734 | +example above. |
735 | + |
736 | +The import is initiated by browsing to the Images tab and following the |
737 | +instructions on that page. |
Not a code change and no risk, so self-approving.