Documentation for external DHCP

Hello,

When configuring a smart proxy for external DHCP (isc), is very different
than letting Foreman handle DHCP internally.

Other than omapi configuration described in the wiki, what are the other
configs (dhcpd.conf) that needs to be done? (couldn't find it in the docs)

thanks,
-rsd

OMAPI and the smart proxy configuration files (dhcp.yml, dhcp_isc.yml)
are the only necessary configuration.

Add subnet stanzas and optionally pools to your ISC DHCP config for any
subnets you want it to offer leases to. The smart proxy will work for
any subnets defined in the ISC DHCP config.

More details about configuring subnets and pools can probably be found
in the ISC docs, it isn't specific to Foreman or the smart proxy.

··· On 19/01/17 12:23, Raul Dias wrote: > Hello, > > When configuring a smart proxy for external DHCP (isc), is very > different than letting Foreman handle DHCP internally. > > Other than omapi configuration described in the wiki, what are the other > configs (dhcpd.conf) that needs to be done? (couldn't find it in the docs)


Dominic Cleal
dominic@cleal.org

Yes. That's on the wiki.

What I am looking is the configuration for other stuff that Foreman does
when dhcpd is local.

For example, bootp, tftp, pxe…

··· On 23/01/2017 06:57, Dominic Cleal wrote: > On 19/01/17 12:23, Raul Dias wrote: >> Hello, >> >> When configuring a smart proxy for external DHCP (isc), is very >> different than letting Foreman handle DHCP internally. >> >> Other than omapi configuration described in the wiki, what are the other >> configs (dhcpd.conf) that needs to be done? (couldn't find it in the docs) > OMAPI and the smart proxy configuration files (dhcp.yml, dhcp_isc.yml) > are the only necessary configuration. > > Add subnet stanzas and optionally pools to your ISC DHCP config for any > subnets you want it to offer leases to. The smart proxy will work for > any subnets defined in the ISC DHCP config. > > More details about configuring subnets and pools can probably be found > in the ISC docs, it isn't specific to Foreman or the smart proxy. >


Att. Raul Dias

filename/next-server for PXE booting will be set by Foreman when
creating managed hosts for provisioning. There's nothing to do.

You can set those options too (pxelinux.0 is the usual filename) if you
want them to apply to non-Foreman managed hosts, but it isn't necessary.

··· On 23/01/17 13:29, Raul Dias wrote: > Yes. That's on the wiki. > > What I am looking is the configuration for other stuff that Foreman does > when dhcpd is local. > > For example, bootp, tftp, pxe...


Dominic Cleal
dominic@cleal.org

Sorry to insist.

Why it is not necessary?

Just for reference I am keeping foreman in a diferent subnet.

Thanks

··· On 23/01/2017 11:36, Dominic Cleal wrote: > On 23/01/17 13:29, Raul Dias wrote: >> Yes. That's on the wiki. >> >> What I am looking is the configuration for other stuff that Foreman does >> when dhcpd is local. >> >> For example, bootp, tftp, pxe... > filename/next-server for PXE booting will be set by Foreman when > creating managed hosts for provisioning. There's nothing to do. > > You can set those options too (pxelinux.0 is the usual filename) if you > want them to apply to non-Foreman managed hosts, but it isn't necessary. >


Att. Raul Dias

Setting PXE (filename/next-server) options for non-Foreman hosts isn't
required to use Foreman. Foreman will set filename/next-server for hosts
you're configuring with it for provisioning.

··· > On 23/01/2017 11:36, Dominic Cleal wrote: >> On 23/01/17 13:29, Raul Dias wrote: >>> For example, bootp, tftp, pxe... >> filename/next-server for PXE booting will be set by Foreman when >> creating managed hosts for provisioning. There's nothing to do. >> >> You can set those options too (pxelinux.0 is the usual filename) if you >> want them to apply to non-Foreman managed hosts, but it isn't necessary.

On 23/01/17 14:40, Raul Dias wrote:

Sorry to insist.

Why it is not necessary?


Dominic Cleal
dominic@cleal.org

Yes. I am looking for extra dhcpd.conf configuration explicitly for
provisioning.

··· On Mon, Jan 23, 2017, 12:54 Dominic Cleal wrote:

On 23/01/2017 11:36, Dominic Cleal wrote:

On 23/01/17 13:29, Raul Dias wrote:

For example, bootp, tftp, pxe…
filename/next-server for PXE booting will be set by Foreman when
creating managed hosts for provisioning. There’s nothing to do.

You can set those options too (pxelinux.0 is the usual filename) if you
want them to apply to non-Foreman managed hosts, but it isn’t necessary.

On 23/01/17 14:40, Raul Dias wrote:

Sorry to insist.

Why it is not necessary?

Setting PXE (filename/next-server) options for non-Foreman hosts isn’t
required to use Foreman. Foreman will set filename/next-server for hosts
you’re configuring with it for provisioning.


Dominic Cleal
dominic@cleal.org


You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.