The first step in configuring a DHCP server is to create the configuration file that stores the network information for the clients.
Use this file to declare options and global options for client systems.
So we figured we’d probably needed one of those as well.
We tried to roll our own but soon enough we came across a package that does all this combined. Also being somewhat biased, we would prefer to run Cobbler in a container. If you search for Cobbler on the Docker Hub, there are 10 hits.
It also allows integration with the Puppet configuration management tool to allow you to configure your newly provisioned hosts.
Installing Cobbler We're going to install on a Red Hat Enterprise Linux 5 host.
cobbler - a provisioning and update server cobbler is a provisioning (installation) and update server.
If and when these two are accepted as part of the Internet Engineering Task Force (IETF) standards process, there will be a third mode — the standard DNS update method.
Cobbler currently has RPM packages available via the EPEL repository, or you can install from source. To install Cobbler, we need some prerequisite packages: We need to do this every time we change the settings.
Setting up DHCP management, TFTP server and firewalls We also need to decide if we want Cobbler to manage our DHCP or use an existing server.
Distributions contain information about what kernel and initrd are used, plus metadata (required kernel parameters, etc).
Profiles associate a Distribution with a kickstart file and optionally customize the metadata further.
The configuration file can contain extra tabs or blank lines for easier formatting.