Update v4.6.x docs

Author: actions-user

static/docs/v4.6.x/_sources/getting-started/debian-quickstart.rst.txt

@@ -127,7 +127,7 @@ and set it for the "default" node profile.
 
 .. code-block:: bash
 
-   sudo wwctl image import docker://ghcr.io/warewulf/warewulf-debian:12.0 debian-12.0
+   sudo wwctl image import --build docker://ghcr.io/warewulf/warewulf-debian:12.0 debian-12.0
    sudo wwctl profile set default --image=debian-12.0
 
 Set up the default node profile
@@ -179,7 +179,7 @@ configurations.
 
 .. code-block:: bash
 
-   sudo wwctl node add n0000.cluster --ipaddr 192.168.200.100 --discoverable true
+   sudo wwctl node add n0000.cluster --ipaddr 192.168.200.100 --discoverable
 
 At this point you can view the basic configuration of this node by
 typing the following:

static/docs/v4.6.x/_sources/nodes/disks.rst.txt

@@ -4,7 +4,8 @@ Provisioning disks
 
 As a tech preview, Warewulf provides structures to define disks, partitions, and
 file systems. These structures can generate a configuration for `Ignition`_ to
-provision partitions and file systems dynamically on cluster nodes.
+provision partitions and file systems dynamically on cluster nodes, or with
+sfdisk, mkfs, and mkswap during boot.
 
 .. _Ignition: https://coreos.github.io/ignition/
 
@@ -145,3 +146,117 @@ file systems once, you may
 See the `upstream ignition documentation`_ for additional information.
 
 .. _upstream ignition documentation: https://coreos.github.io/ignition/operator-notes/#filesystem-reuse-semantics
+
+
+.. _provision to disk:
+
+Provision to disk
+=================
+
+*New in Warewulf v4.6.2*
+
+As a tech preview, the Warewulf two-stage boot process can provision the node
+image to local storage.
+
+.. warning::
+
+   This functionality is a technology preview and should be used with care. Pay
+   specific attention to ``wipeFilesytem`` and similar settings.
+
+.. note::
+
+   Warewulf doesn't install a bootloader to the disk or add UEFI entries. Nodes
+   still request an image and configuration from the Warewulf server on every
+   boot.
+
+.. note::
+
+   While provisioning to disk should be possible during a single-stage boot, not
+   all features are available:
+
+   - Warewulf does not perform hardware detection to ensure that necessary
+     kernel modules are loaded prior to init.
+   - Warewulf does not load udev to ensure that ``/dev/disk/by-*`` symlinks are
+     available prior to init.
+
+With Ignition
+-------------
+
+Warewulf needs a prepared file system to deploy the image to. Warewulf can
+provision this file system using Ignition. To use Ignition, include ``ignition``
+in your system overlay. The ignition overlay provisions disks during init and,
+optionally, during the first stage of a two-stage boot. This allows the
+root file system to be provisioned before the image is loaded.
+
+.. code-block:: shell
+
+   wwctl node set wwnode1 \
+     --diskname /dev/vda --diskwipe \
+     --partname rootfs --partcreate --partnumber 1 \
+     --fsname rootfs --fsformat ext4 --fspath /
+
+In order to allow Dracut to provision the disk, partition, and file system,
+Ignition must be included in the Dracut image.
+
+.. code-block:: shell
+
+   wwctl image exec rockylinux-9 -- /usr/bin/dracut --force --no-hostonly --add wwinit --add ignition --regenerate-all
+
+The necessary file system may alternatively be prepared out-of-band.
+
+With sfdisk and mkfs
+--------------------
+
+Systems that do not have access to Ignition (e.g., Rocky Linux 8) can provision
+the root file system using a combination of ``sfdisk`` and ``mkfs``. To use
+them, include ``sfdisk`` and ``mkfs`` in your system overlay. The ``sfdisk`` and
+``mkfs`` overlays provision disk and file systems during the first stage of a
+two-stage boot. This allows the root file system to be provisioned before the
+image is loaded.
+
+Configure the ``sfdisk`` and ``mkfs`` overlays using resources:
+
+.. code-block:: shell
+
+   wwctl node set wwnode1 \
+     --diskname /dev/vda --diskwipe \
+     --partname rootfs --partcreate --partnumber 1 \
+     --fsname rootfs --fsformat ext4 --fspath /
+
+In order to allow Dracut to provision the disk, partition, and file system, some
+additional commands must be included in the Dracut image, depending on which
+functionality is used:
+
+- **sfdisk:** writes the partition table
+
+  - **blockdev:** used to re-read the partition table after writing
+
+  - **udevadm:** used to trigger udev events after writing the partition table
+
+- **mkfs:** formats file systems (may also require file-system-specific commands like mkfs.ext4)
+
+  - **mkfs.ext4**, **mkfs.btrfs**, etc: used by mkfs to format specific file systems
+
+  - **wipefs:** used to determine if a file system already exists
+
+.. code-block:: shell
+
+   wwctl image exec rockylinux-8 -- /usr/bin/dracut --force --no-hostonly \
+     --add wwinit \
+     --install sfdisk \
+     --install blockdev \
+     --install udevadm \
+     --install mkfs \
+     --install mkfs.ext4 \
+     --install wipefs \
+     --regenerate-all
+
+Configuring the root device
+---------------------------
+
+Set the desired storage device for the node image using the ``--root``
+parameter.
+
+.. code-block:: shell
+
+   wwctl node set wwnode1 --root /dev/disk/by-partlabel/rootfs

static/docs/v4.6.x/_sources/nodes/network.rst.txt

@@ -34,6 +34,17 @@ specifying  ``--netname``.
    an interface may fail to be named correct if its desired name conflicts with
    the kernel-assigned name of another interface during the boot process.
 
+.. _nettags:
+
+Network Tags
+============
+
+Each network device can optionally have one or more key-value pair tags.
+
+.. code-block:: shell
+
+   wwctl node set n1 --nettagadd="DNS1=1.1.1.1"
+
 .. _bonding:
 
 Bonding

static/docs/v4.6.x/_sources/nodes/nodes.rst.txt

@@ -199,3 +199,48 @@ overlays.
              passno: 0
 
 Resources can only be managed with ``wwctl node edit``.
+
+Importing Nodes From a File
+===========================
+
+You can import nodes into Warewulf by using the ``wwctl node import`` command.
+The file used must be in YAML format.
+
+The YAML file must be a mapping of node names to their attributes, where each
+node is represented as a dictionary of attributes. To simplify the creation of
+the YAML file, you can use the wwctl node export command to export the current
+node configuration to a YAML file. This exported file can serve as a template
+for creating new nodes.
+
+A minimal example of a YAML file looks like this:
+
+.. code-block:: yaml
+
+   n1:
+      profiles:
+         - default
+      image name: rockylinux-9
+      ipxe template: default
+      kernel:
+         args:
+            - quiet
+            - crashkernel=no
+            - nosplash
+            - console=ttyS0,115200
+      network devices:
+         default:
+            type: ethernet
+            device: eno1
+            hwaddr: "00:00:00:00:00:01"
+            ipaddr: 10.0.2.1
+            netmask: 255.255.255.0
+            gateway: 172.16.131.1
+            tags:
+            DNS1: 1.1.1.1
+      primary network: default
+
+This can be imported with the following command:
+
+.. code-block:: shell
+
+   wwctl node import /path/to/nodes.yaml