================================ EL7 Quickstart (CentOS and RHEL) ================================ Install Warewulf and dependencies ================================= .. code-block:: bash sudo yum install -y golang tftp-server dhcp nfs-utils git clone https://github.com/warewulf/warewulf.git cd warewulf make all sudo make install Configure firewalld =================== Restart firewalld to register the added service file, add the service to the default zone, and reload. .. code-block:: bash sudo systemctl restart firewalld sudo firewall-cmd --permanent --add-service warewulf sudo firewall-cmd --permanent --add-service nfs sudo firewall-cmd --permanent --add-service tftp sudo firewall-cmd --reload Configure the controller ======================== Edit the file ``/etc/warewulf/warewulf.conf`` and ensure that you've set the appropriate configuration parameters. Here are some of the defaults for reference assuming that ``192.168.200.1`` is the IP address of your cluster's private network interface: .. code-block:: yaml WW_INTERNAL: 43 ipaddr: 192.168.200.1 netmask: 255.255.255.0 network: 192.168.200.0 warewulf: port: 9873 secure: false update interval: 60 autobuild overlays: true host overlay: true syslog: false dhcp: enabled: true range start: 192.168.200.50 range end: 192.168.200.99 systemd name: dhcpd tftp: enabled: true systemd name: tftp nfs: enabled: true export paths: - path: /home export options: rw,sync mount options: defaults mount: true - path: /opt export options: ro,sync,no_root_squash mount options: defaults mount: false systemd name: nfs-server container mounts: - source: /etc/resolv.conf dest: /etc/resolv.conf readonly: true .. note:: The DHCP range ends at ``192.168.200.99`` and as you will see below, the first node static IP address (post boot) is configured to ``192.168.200.100``. Start and enable the Warewulf service ===================================== .. code-block:: bash # 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. .. code-block:: bash sudo wwctl configure --all .. note:: If you just installed the system fresh and have SELinux enforcing, you may need to reboot the system at this stage to properly set the contexts of the TFTP contents. After rebooting, you might also need to run ``restorecon -Rv /var/lib/tftpboot/`` if there are errors with TFTP still. 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. .. code-block:: bash sudo wwctl container import docker://ghcr.io/warewulf/warewulf-centos:7 centos-7 --setdefault sudo wwctl kernel import $(uname -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: .. code-block:: bash sudo wwctl profile set -y default -K $(uname -r) -C centos-7 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: .. code-block:: bash sudo wwctl profile set -y default --netdev eth0 --netmask 255.255.255.0 --gateway 192.168.200.1 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. .. code-block:: bash sudo wwctl node add n0000.cluster --ipaddr 192.168.200.100 --discoverable true sudo wwctl node list -a n0000 Turn on your compute node and watch it boot!