|
1695.1.1
by Julian Edwards
Docs for kernel options |
1 |
===========================
|
2 |
Setting kernel boot options
|
|
3 |
===========================
|
|
4 |
||
5 |
MAAS is able to send specific kernel options to booting nodes on both |
|
6 |
a global basis and a per-node basis. |
|
7 |
||
8 |
Global kernel options
|
|
9 |
---------------------
|
|
10 |
||
11 |
As an admin, click on the gear icon at the top right and scroll down to |
|
12 |
the Global Kernel Parameters section, as shown here: |
|
13 |
||
14 |
.. image:: media/global_kernel_opts.png |
|
15 |
||
16 |
Whatever you set here is sent as-is to all booting nodes. |
|
17 |
||
18 |
Per-node kernel options
|
|
19 |
-----------------------
|
|
20 |
||
21 |
Per-node kernel options are set using tags. The easiest way of doing this |
|
|
1923.1.4
by Julian Edwards
Fix documentation and man pages |
22 |
is to use the ``maas`` command. You will need to :ref:`be
|
|
1695.1.1
by Julian Edwards
Docs for kernel options |
23 |
logged in to the API first <api-key>` and then you can add a tag which has its |
24 |
``kernel_opts`` value set, like this:: |
|
25 |
||
|
1923.1.4
by Julian Edwards
Fix documentation and man pages |
26 |
$ maas maas tags new name='nomodeset' \
|
|
1695.1.5
by Julian Edwards
clarify which tag is used for kernel opts |
27 |
comment='nomodeset kernel option' kernel_opts='nomodeset vga'
|
|
1695.1.1
by Julian Edwards
Docs for kernel options |
28 |
|
29 |
Once the tag is defined, you can add it to a node or nodes::
|
|
30 |
||
|
1923.1.4
by Julian Edwards
Fix documentation and man pages |
31 |
$ maas maas tag update-nodes nomodeset add=<system_id_1> \
|
|
1695.1.1
by Julian Edwards
Docs for kernel options |
32 |
add=<system_id_2>
|
33 |
||
34 |
.. note:: |
|
35 |
||
36 |
Any per-node kernel options set will completely override the global options. |
|
|
1695.1.5
by Julian Edwards
clarify which tag is used for kernel opts |
37 |
If multiple tags attached to a node have the kernel_opts defined, the first |
38 |
one ordered by name is used. |