1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
|
cc_mounts:
description: |
This module can add or remove mount points from ``/etc/fstab`` as well as
configure swap. The ``mounts`` config key takes a list of ``fstab`` entries
to add. Each entry is specified as a list of ``[ fs_spec, fs_file,
fs_vfstype, fs_mntops, fs-freq, fs_passno ]``.
For more information on these options, consult the manual for
``/etc/fstab``. When specifying the ``fs_spec``, if the device name starts
with one of ``xvd``, ``sd``, ``hd``, or ``vd``, the leading ``/dev`` may be
omitted. Any mounts that do not appear to either an attached block device
or network resource will be skipped with a log like "Ignoring nonexistent
mount ...".
Cloud-init will attempt to add the following mount directives if available
and unconfigured in ``/etc/fstab``:
.. code-block:: yaml
mounts:
- ["ephemeral0", "/mnt", "auto", "defaults,nofail,x-systemd.after=cloud-init-network.service", "0", "2"]
- ["swap", "none", "swap", "sw", "0", "0"]
In order to remove a previously-listed mount, an entry can be added to the
``mounts`` list containing ``fs_spec`` for the device to be removed but no
mount point (i.e. ``[ swap ]`` or ``[ swap, null ]``).
The ``mount_default_fields`` config key allows default values to be
specified for the fields in a ``mounts`` entry that are not specified,
aside from the ``fs_spec`` and the ``fs_file`` fields. If specified, this
must be a list containing 6 values. It defaults to:
.. code-block:: yaml
mount_default_fields: [none, none, "auto", "defaults,nofail,x-systemd.after=cloud-init-network.service", "0", "2"]
Non-systemd init systems will vary in ``mount_default_fields``.
Swap files can be configured by setting the path to the swap file to create
with ``filename``, the size of the swap file with ``size``, maximum size
of the swap file if using an ``size: auto`` with ``maxsize``. By default,
no swap file is created.
.. note::
If multiple mounts are specified, where a subsequent mount's mount point
is inside of a previously-declared mount's mount point, (i.e. the 1st
mount has a mount point of ``/abc`` and the 2nd mount has a mount point
of ``/abc/def``) then this will not work as expected -- ``cc_mounts``
first creates the directories for all the mount points **before** it
starts to perform any mounts and so the sub-mount point directory will
not be created correctly inside the parent mount point.
For systems using ``util-linux``'s ``mount`` program, this issue can be
worked around by specifying ``X-mount.mkdir`` as part of a ``fs_mntops``
value for the subsequent mount entry.
examples:
- comment: >
Example 1: Mount ``ephemeral0`` with ``noexec`` flag, ``/dev/sdc`` with
``mount_default_fields``, and ``/dev/xvdh`` with custom ``fs_passno "0"``
to avoid ``fsck`` on the mount.
Also provide an automatically-sized swap with a max size of 10485760 bytes.
file: cc_mounts/example1.yaml
- comment: >
Example 2: Create a 2 GB swap file at ``/swapfile`` using human-readable
values.
file: cc_mounts/example2.yaml
name: Mounts
title: Configure mount points and swap files
|
