19
19
Brand new hardware gets released all the time. We want that hardware to
20
20
work well wih Ubuntu and MAAS, even if it was released after the latest
21
release of MAAS or Ubuntu. Hardware Enablement (HWE) is all about making
22
keeping pace with the new hardware.
21
release of MAAS or Ubuntu. Hardware Enablement (HWE) is all about keeping
22
pace with the new hardware.
24
24
Ubuntu's solution to this is to offer newer kernels for older releases.
25
25
There are at least two kernels on offer for Ubuntu releases: the
39
39
.. _LTS Enablement Stack:
40
40
https://wiki.ubuntu.com/Kernel/LTSEnablementStack
42
Importing hardware-enablement kernels
43
-------------------------------------
45
Hardware-enablement kernels need to be imported to a cluster controller
46
before that cluster's nodes can use them.
48
In order to import HWE kernels to a cluster controller you need to edit
49
the controller's ``/etc/maas/bootresources.yaml`` file, and update the
50
subarches that you want to import, like this::
53
storage: "/var/lib/maas/boot-resources/"
56
- path: "http://maas.ubuntu.com/images/ephemeral-v2/releases/"
57
keyring: "/usr/share/keyrings/ubuntu-cloudimage-keyring.gpg"
60
arches: ["i386", "amd64"]
61
subarches: ["generic", "hwe-q", "hwe-r", "hwe-s", "hwe-t"]
64
Once you've updated ``bootresources.yaml``, you can tell the cluster to
65
re-import its boot images using the ``maas`` command (You will need to
66
:ref:`be logged in to the API first <api-key>`)::
68
$ maas <profile-name> node-group import-boot-images \
69
<cluster-controller-uuid>
71
You can also tell the cluster controller to re-import its boot images by
72
clicking the ``Import boot images`` button in the ``Clusters`` page of
75
Using hardware-enablement kernels in MAAS
76
-----------------------------------------
78
A MAAS administrator can choose to use HWE kernels on a per-node basis
81
The quickest way to do this is using the MAAS command, like this::
43
Booting hardware-enablement kernels
44
-----------------------------------
46
MAAS imports hardware-enablement kernels along with its generic boot images,
47
but as different "sub-architectures" to the default "generic" one.
49
So, for example, a common server might have architecture and sub-architecture
50
of ``amd64/generic``, but some newer system chassis which doesn't become
51
fully functional with the default kernel for Ubuntu 14.04 Trusty Tahr, for
52
example, may require ``amd64/hwe-t``.
54
The quickest way to make a node use a hardware-enablement kernel is by using
55
the MAAS command, like this::
83
57
$ maas <profile-name> node update <system-id>
84
58
architecture=amd64/hwe-t
86
If you specify an architecture that doesn't exist (e.g.
87
``amd64/hwe-z``), the ``maas`` command will return an error.
60
If you specify an architecture that doesn't exist (e.g. ``amd64/hwe-zz``),
61
the ``maas`` command will return an error.
90
63
It's also possible to use HWE kernels from the MAAS web UI, by visiting
91
64
the Node's page and clicking ``Edit node``. Under the Architecture field,