As mentioned in the Configuration section, node configs are persisted to the
nodes.conf YAML file but generally it is best not to edit this file directly (however that is supported, it is just prone to errors).
This method of using a YAML configuration file as a backend datastore is both scalable and very lightweight. We've tested this out to over 10,000 node entries which yielded update latencies under 1 second, which we felt was both tolerable and advantageous.
Creating a new node is as simple as running the following command:
For small clusters, you can use simple names (e.g.
n0000) but for larger, more complicated clusters that are compromised of multiple clusters and roles, it is highly recommended to use node names that include a cluster descriptor. In Warewulf, this is generally done by using a domain name (e.g.
n0000.cluster01). Warewulf will automatically assume that the domain is the equivalent of the cluster name.
This also means that you can address groups of nodes by the cluster descriptor with globs. For example, you are able to refer to all nodes in "cluster01" with the following string:
*.cluster01 which is valuable for other
Once you have configured one or more nodes, you can list them and their attributes as follows:
You can also see the node's full attribute list by specifying the
-a option (all):
note: The attribute values in parenthesis are default values and can be overridden in the next section, granted, the default values are generally usable.
In the above output we can see that there is no kernel or container defined for this node. To provision a node, the minimum requirements are a kernel and container, and for that node to be useful, we will also need to configure the network so the nodes are reachable after they boot.
Node configurations are set using the
wwctl node set command. To see a list of all configuration attributes, use the command
wwctl node set --help.
And you can check that the container name is set for
To configure the network, we have to pick a network device name and provide the network information as follows:
You can now see that the node contains configuration attributes for container, kernel, and network:
While we have a
set command we do not have an
unset command (however as of the time of this writing there is a GitHub issue requesting this).
If you wish to
unset a particular value you have to use the
UNDEF value as we did with previous versions of Warewulf. For example:
And to unset this configuration attribute: