You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While developing our deployment server, we encountered the following issues:
We would like to add omapi settings (global) to the dhcpd.conf file.
We would like to add the next-server setting (global) to the dhcpd.conf file.
We would like to add custom options to the dhcpd.conf file.
We would like to add custom lines to the dhcpd.conf file.
Rationale:
We make use of Foreman for deploying nodes and Foreman makes use of the omapi interface.
We need the next-server setting for all hosts.
We have some specific custom options like:
option fqdn.no-client-update True;
We have some specific lines to add:
if option architecture = 00:06 {
filename "grub2/shim.efi";
} elsif option architecture = 00:07 {
filename "grub2/shim.efi";
} elsif option architecture = 00:09 {
filename "grub2/shim.efi";
} else {
filename "pxelinux.0";
}
In order to realize this, we made some modifications to the dhcpd formula. But that will give
us a maintenance issue in the future. It would be nice to have these updates in a next version
of the formula.
While developing our deployment server, we encountered the following issues:
Rationale:
option fqdn.no-client-update True;
if option architecture = 00:06 {
filename "grub2/shim.efi";
} elsif option architecture = 00:07 {
filename "grub2/shim.efi";
} elsif option architecture = 00:09 {
filename "grub2/shim.efi";
} else {
filename "pxelinux.0";
}
In order to realize this, we made some modifications to the dhcpd formula. But that will give
us a maintenance issue in the future. It would be nice to have these updates in a next version
of the formula.
The changes we made are:
changes.patch.txt
The text was updated successfully, but these errors were encountered: