Skip to main content

openSUSE Leap and SLES 15 Quickstart

Install Warewulf and dependencies#

sudo zypper install -t pattern devel_basis
sudo zypper install go
sudo zypper install tftp dhcp-server nfs-kernel-server
sudo systemctl stop firewalld
sudo systemctl disable firewalld
git clone
cd warewulf
make all
sudo make install

You can also just install the 'warewulf4' package with zypper, but please note that for this package you have to replace '/var/warewulf' with '/var/lib/warewulf' in the rest of this document.

Configure the controller#

Edit the file /etc/warewulf/warewulf.conf and ensure that you've set the appropriate configuration paramaters. Here are some of the defaults for reference assuming that is the IP address of your cluster's private network interface:

port: 9873
secure: true
update interval: 60
enabled: true
range start:
range end:
config file: /etc/dhcpd.conf
template: default
systemd name: dhcpd
enabled: true
tftproot: /var/lib/tftpboot
systemd name: tftp
systemd name: nfs-server
- /home
- /var/warewulf

The DHCP range ends at and as you will see below, the first node static IP address (post boot) is configured to

Start and enable the Warewulf service#

# Create the group the warewulfd service will run as
sudo groupadd -r warewulf
# Reload system services
sudo systemctl daemon-reload
# Start and enable the warewulfd service
sudo systemctl enable --now warewulfd

Configure system services automatically#

There are a number of services and configurations that Warewulf relies on to operate. If you wish to configure all services, you can do so individually (omitting the --all) will print a help and usage instructions.

sudo wwctl configure --all

If the dhcpd service was not used before you will have to add the interface on which the cluster network is running to the DHCP_INTERFACE in the file /etc/sysconfig/dhcpd.

Pull and build the VNFS container and kernel#

This will pull a basic VNFS container from Docker Hub and import the default running kernel from the controller node and set both in the "default" node profile.

$ sudo wwctl container import docker:// --setdefault
$ sudo wwctl kernel import $(name -r) --setdefault

Set up the default node profile#

The --setdefault arguments above will automatically set those entries in the default profile, but if you wanted to set them by hand to something different, you can do the following:

sudo wwctl profile set -y default -K $(uname -r) -C leap-15.3-hpc:latest

Next we set some default networking configurations for the first ethernet device. On modern Linux distributions, the name of the device is not critical, as it will be setup according to the HW address. Because all nodes will share the netmask and gateway configuration, we can set them in the default profile as follows:

sudo wwctl profile set -y default --netdev eth0 --netmask --gateway
sudo wwctl profile list

Add a node#

Adding nodes can be done while setting configurations in one command. Here we are setting the IP address of eth0 and setting this node to be discoverable, which will then automatically have the HW address added to the configuration as the node boots.

Node names must be unique. If you have node groups and/or multiple clusters, designate them using dot notation.

Note that the full node configuration comes from both cascading profiles and node configurations which always supersede profile configurations.

sudo wwctl node add n0000.cluster --netdev eth0 -I --discoverable
sudo wwctl node list -a n0000

Warewulf Overlays#

There are two types of overlays: system and runtime overlays.

System overlays are provisioned to the node before /sbin/init is called. This enables us to prepopulate node configurations with content that is node specific like networking and service configurations.

Runtime overlays are provisioned after the node has booted and periodically during the normal runtime of the node. Because these overlays are provisioned at periodic intervals, they are very useful for content that changes, like users and groups.

Overlays are generated from a template structure that is viewed using the wwctl overlay commands. Files that end in the .ww suffix are templates and abide by standard text/template rules. This supports loops, arrays, variables, and functions making overlays extremely flexible.


When using the overlay subsystem, system overlays are never shown by default. So when running overlay commands, you are always looking at runtime overlays unless the -s option is passed.

All overlays are compiled before being provisioned. This accelerates the provisioning process because there is less to do when nodes are being managed at scale.

Here are some of the common overlay commands:

sudo wwctl overlay list -l
sudo wwctl overlay list -ls
sudo wwctl overlay edit default /etc/hello_world.ww
sudo wwctl overlay build -a

Boot your compute node and watch it boot#