EL7 Quickstart (CentOS and RHEL)
#
Install Warewulf and dependencies#
Configure firewalldRestart firewalld to register the added service file, add the service to the default zone, and reload.
#
Configure the controllerEdit 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:
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#
Configure system services automaticallyThere 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.
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
$ sudo restorecon -Rv /var/lib/tftpboot/
if there are errors with TFTP still.
#
Pull and build the VNFS container and kernelThis 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.
#
Set up the default node profileThe --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:
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:
#
Add a nodeAdding 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.