Shuichi Ihara wrote:
The following documentation would be useful.
https://fedorahosted.org/cobbler/wiki/UsingCobblerDhcpManagementWithMulti...
In addition to above example, I'm putting "group" and
"next-server" parameter in the
dhcp.template to control the tftp server for each clients.
Thanks
-Ihara
Chris Sarginson - Technical Support wrote:
> Hi Guys,
>
> Are there any plans to allow cobbler to manage the DHCP service to the
> extent that it would be able to add a host with additional custom DHCP
> options such as next-server 192.168.x.x so that instead of having to
> have multiple networks for installers everything could be combined into
> one, and then the TFTP server is specified as and when required.
>
_______________________________________________
cobbler mailing list
cobbler(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler
I should also mention that John Eckersberg is wanting to add the
understanding of networks to Cobbler, so you can do things like:
cobbler system add --name=foo --mac=AA:BB:CC:DD:EE:FF --profile=bar
--network=baz
And have a mac reservation come out of "baz" automatically, where baz
could be defined with a "cobbler network add --name= ...."
When we get to that level of support, the need for --dhcp-tag /should/
go away, I think. This should be good as --dhcp-tag is a bit of an
abstract concept. (We'll have to figure out how we want to manage
upgrades in that case.)
--Michael