Bug 1489364

Assigning to Sergei for review.

It is possible to install the dhcp_remote_isc module by hand -- by installing the corresponding package and updating the config files. My understanding is that the installer is the main/preferred way of updating Satellite/capsule installations? If so, puppet module is probably the way to go.

(In reply to Dmitri Dolguikh from comment #12)
> It is possible to install the dhcp_remote_isc module by hand -- by
> installing the corresponding package and updating the config files. My
> understanding is that the installer is the main/preferred way of updating
> Satellite/capsule installations? If so, puppet module is probably the way to
> go.

Yes, in the guides we must say to use the installer script. I will test if the Puppet module is available on a Capsule.

Thank you

Sergei,

My understanding was that the new implementation to support remote isc dhcp servers was going to be included in 6.3, but I could be wrong.

To answer your questions:

1) foreman-proxy requires access to dhcpd config and leases file in order to get information about the networks (config file) and the reservations (config and leases files) and leases (leases file) the server maintains. This information is used then to determine availability of ip addresses, catch conflicts during host creation, etc.

2) never actually used an iSCSI device, but the guide at [2] sounds good to me.

-d

Updating target milestone to 'GA'.

Hello Dmitri,

From the bug [1] I see that the smart_proxy_dhcp_remote_isc package is pushed downstream. Now we can mention it and dhcp_isc modules in the documentation.

What is the workflow of installing and setting up these modules?

Thank you

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1397702

There are no changes in dhcp_isc core provider, not sure if anything needs to change in the docs. 

dhcp_remote_isc provider should be installable via installer (it is in upstream), its configuration options are exactly the same as for the dhcp_isc provider.

I fixed the issue and released version 0.0.4 of the gem. Updtaed RPM packages should become available once PR is merged.

Updating release flags.

There are two possible installations for smart-proxy and dhcpd: same machine or separate machines. The former case is covered by core smart-proxy and no nfs or additional modules are required. 

In the latter case smart-proxy's remote_dhcp_isc provider needs access to dhcpd's config and lease files. This is usually achieved via exposing those files via NFS, but can be done using any other distributed filesystem.

Internally the difference on the smart-proxy side between the two setups is that the remote isc provider doesn't cache anything at all, and has to fetch config and lease files on every request (which is why it's slow and shouldn't be used by default). 

In order to configure smart-proxy to interface with a remote dhcpd server, the user will need to:
 - install and configure dhcpd, make dhcpd config files and lease file available over NFS
 - install smart-proxy
 - install dhcp_remote_isc provider, configure the provider to use paths from step #1

Let me know if this clears up the questions you had.

These changes are now live on the customer portal: 

https://access.redhat.com/documentation/en-us/red_hat_satellite/6.3/html/installation_guide/configuring_external_services#configuring_satellite_external_dhcp

Hello Dmitri,

Is the remote_isc DHCP provider included into Satellite 6.2. For now, the changes are made only to 6.4 and 6.3 docs. 

Thank you

remote_isc DHCP provider isn't available in Satellite 6.2.