>>> - Is it possible to add an option to keep
systems in Cobbler
>>> but disable them from DHCP?
>>>
>> The first one is not a good idea, I'll explain.
>>
>> We don't regenerate dhcpd.conf except when "cobbler sync" is
run....
>> why? It has to restart services, and we don't want to do that for
every
>> system. Assume you were modifying 200 systems, or just ten, one at a
>> time? We want to only restart the service when the user wants to.
>>
>> The second one? Yes, if you don't put their network interface
>> information in there, it won't be used, or you could flag those
>> interfaces as static, and they won't be in there.
>>
>
> I already use the static flag. The static flag means a static MAC-IP
relation instead of dynamic from a pool.
>
This I know, just throwing it out there.
> The IP assignment (static and dynamic) is independent if it shall be
stored in the dhcpd.conf.
>
If you're not using manage-dhcp, and it's not static, I don't see much
point in storing it in Cobbler.
When we teach manage-dhcp about network objects and assign networks to
multiple cobbler replicas, I can see it not being relevant for the local
cobbler server, but
other than that...
Urm, so, yes, I forgot something.
You could currently assign another --dhcp-tag to it, and then edit the
template to not include DHCP for systems with that tag.
That is intended to allow easier templating for multiple subnets in the
same dhcpd.conf, though very few people use this feature. (As it's a
little hard to explain).
Modelling networks will make it easier to explain.
> To exclude a system/interface record from the dhcpd.conf a new interface
(and network-object) field dhcp_enabled needs to be added.
>
That field would be highly confusing since it doesn't say what it is,
and what it is is a rather abstract concept -- so we're not going to add
this.
See above for one way you could handle it for now.
The nodes in my network are all configured with static IPs. The dhcp (with fixed ip
addresses) is only used for PXE boots.
The reason I ask this because I want to keep the provisioned node details in cobbler for
future deployments. I want to temporary disable the node in cobbler to allow a legacy
deployment method Cobbler to be used.
The dhcp enable flag can help with reducing the entries in the dhcpd.conf. It allows you
to better control on which interfaces are allowed to do a DHCP or PXE boot request.
Also for the objects you want to specify which networks will be configured in the
dhpcd.conf. That requires also a dhcp_enable flag.
Regards,
Peter
This e-mail and any attachment is for authorised use by the intended recipient(s) only. It
may contain proprietary material, confidential information and/or be subject to legal
privilege. It should not be copied, disclosed to, retained or used by, any other party. If
you are not an intended recipient then please promptly delete this e-mail and any
attachment and all copies and inform the sender. Thank you.