Foreman provides integration with DHCP using the Smart Proxy. Technically this is implemented using the dhcp module as a common base and then with various providers:

• dhcp_bluecat (unmaintained)
• dhcp_device42 (unmaintained)
• dhcp_dnsmasq
• dhcp_infoblox
• dhcp_isc
• dhcp_libvirt
• dhcp_native_ms (Windows-only)
• dhcp_remote_isc

The support is documented in the integrating provisioning infrastructure services. Upstream (3.16) and downstream (6.17) have a slightly different set of supported providers.

In addition, there is ISC Kea as the replacement for ISC DHCP. It has a REST API and should allow deprecating the dhcp_isc and dhcp_remote_isc providers. SAT-27739 tracks the support and is likely a lot easier to integrate in a containerized world.

Open questions:

• Which providers to implement
• Do we support managing a DHCP server like we do today?
• Do we drop ISC DHCP (both local and remote) and solely focus on talking to (remote) APIs for services? Users who need it can use n-1 support for Capsules.