kelvin/warewulf
1
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity

New architecture-specific wwclient overlays

Browse Source 
Signed-off-by: Jonathon Anderson <janderson@ciq.com>
This commit is contained in:
Jonathon Anderson
2025-10-30 11:13:19 -06:00
parent 80f6f15a13
commit e07efeee4c
6 changed files with 44 additions and 24 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
userdocs/images/images.rst
View File

@@ -443,19 +443,11 @@ Then, ``wwctl image exec`` will work regardless of the architecture of the
image. For more information about QEMU, see their `GitHub
<https://github.com/multiarch/qemu-user-static>`_
To use wwclient on a booted image using a different architecture, wwclient must
be compiled for the specific architecture. This requires GOLang build tools 1.21
or newer. Below is an example for building wwclient for arm64:
.. note::
.. code-block:: console
# git clone https://github.com/warewulf/warewulf
# cd warewulf
# GOARCH=arm64 PREFIX=/ make wwclient
# mkdir -p /var/lib/warewulf/overlays/wwclient_arm64/rootfs/warewulf
# cp wwclient /var/lib/warewulf/overlays/wwclient_arm64/rootfs/warewulf
Then, apply the new "wwclient_arm64" system overlay to your arm64 node/profile
When provisioning cluster nodes with a different architecture than the
Warewulf server, also use the matching architecture-specific :ref:`wwclient`
overlay: e.g., wwclient.x86_64 or wwclient.aarch64.
Read-only images
================

13
userdocs/overlays/overlays.rst
View File

@@ -202,6 +202,8 @@ provisioning actions:
- **/warewulf/init.d/:** executed in the final root file system but before
calling ``init``.
.. _wwclient:
wwclient
--------
@@ -209,9 +211,14 @@ All configured overlays are provisioned initially along with the node image
itself; but **wwclient** periodically fetches and applies the runtime overlay to
allow configuration of some settings without a reboot.
wwclient will contat the ``ipaddr`` value from ``warewulf.conf`` by default.
This can be overridden by specifying a ``WW_IPADDR`` environment variable, which
can be set via an overlay in ``/etc/default/wwclient``.
wwclient contacts the ``ipaddr`` value from ``warewulf.conf`` by default. This
can be overridden by specifying a ``WW_IPADDR`` environment variable, which can
be set via an overlay in ``/etc/default/wwclient``.
The default wwclient overlay contains a ``wwclient`` executable compiled for the
same architecture as the Warewulf server. Architecture-specific wwclient.aarch64
and wwclient.x86_64 overlays are available as well. This supports using wwclient
on cluster nodes with a different architecture than the Warewulf server.
Network interfaces
------------------