14
14
The script is usually run regularly by a cron task, though it
15
15
needs to be run manually the first time a MAAS system is installed.
16
16
Images that are already in place are kept unchanged, unless the
17
version in the archive has since been updated.
19
The script reads a configuration file /etc/maas/import_pxe_files in
17
version in the archive has since been updated. Only new data is
18
downloaded, so routine runs will not be costly.
20
An easier way to run the script is to trigger it from the MAAS web user
21
interface. To do that, log in to your MAAS as an administrator using a
22
web browser, click the cogwheel icon in the top right of the page to go
23
to the Clusters page, and click "Import boot images." This will start
24
imports on all cluster controllers simultaneously. The same thing can
25
also be done through the region-controller API, or through the
26
command-line interface.
28
The script reads a configuration file `/etc/maas/bootresources.yaml` in
20
29
order to determine:
23
Location of the Ubuntu download archive
26
Ubuntu releases to download
29
Architectures for which images should be downloaded
31
The script uses `wget` to download the kernel and initrd image for
32
each architecture in ARCHES and each release in RELEASES. In addition
33
it copies the Intel-architecture pre-boot loader `pxelinux.0` (plus
34
some of its modules such as `chain.c32`) from its installed location in
31
* the location in the filesystem where downloaded images should be stored,
32
and made available to nodes through TFTP and iSCSI;
33
* Simplestream sources from where boot images should be downloaded; and
34
* which kinds of images are needed: architecture, operating system
37
37
These images are the minimum that's required to start installing a node.
38
38
During installation, a node may download its packages over the network.
added
removed
docs/man/maas-import-pxe-files.8.rst
