Vreman, Peter - Acision wrote:
>> The nodes in my network are all configured with static IPs.
The dhcp
>>
> (with fixed ip addresses) is only used for PXE boots.
>
> In this case I can't see a reason to use cobbler for DHCP management --
> the whole purpose of which is to do DHCP reservations (and to enable DNS
> assignment by knowing MAC->IP mappings). Just configure dhcp to provide
> a dynamic range.
>
We don't want to use dynamic ranges, because that requires the use of a separate
network only for deployment. This separate network also needs to be provisioned on the
switches and routers.
We are happy with the current situation where we can configure a DHCP with static
addresses that will also be configured static on the nodes.
>> Also for the objects you want to specify which networks will be
>>
> configured in the dhpcd.conf. That requires also a dhcp_enable flag.
>
> No, it won't. This will be handled in the templates, basically like
> $NETWORK('foo')
>
I was more thinking in the same way of blending as with distro/profile/system. But with
network/interface. In the interface you can specify the network (just like a profile in
the system record) from which you want to inherit the settings (like subnet, gateway and
static routes) from. But you can also override settings (like the IP address)
And in the dhcp.template I expected something like:
#for net in $networks
#if $net.dhcp_enabled
subnet $net.address netmask $net.subnet {
#if $net.gateway
option routers $net.gateway
#end if
#if $net.pool_start
option range dynamic-bootp $net.pool_start $net.pool_end
#end if}
#end if
#end for
Sorry, I'm a bit confused by this, but also have a lot going on ATM
trying to get a release out. I don't like the idea of adding a flag to
say that a system is not subject to DHCP management as that seems to be
only usable by a very small amount of sites and could confuse people.
A related question for this is, who is responsible for the dynamic allocation of the ip
in the following command?
cobbler system edit --name=foo --interface=eth0 --network=oam -ip_address=auto
Will cobbler assign the IP address or will it be done by dhcpd pools? With cobbler doing
it allows duplicate IP checks.
Cobbler will assign it out of a pool owned by the network object. I
suspect there will not even be a need for the "auto" syntax, but we have
to dig around and play
with that some before getting there. Haven't had time to do that yet.
For the IP address assignment I expected the following three
options:
- fixed
- auto
- dynamic (dhcp pool)
If it belongs on a network you will be able to specify it or it will be
defined by cobbler. Each network has a range of IPs that it can hand out.
Dhcp pools can be configured by editing the templates and such, and if
you want those, you can turn off cobbler DHCP management.
I really want to avoid making this too complicated if at all possible.
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.
_______________________________________________
cobbler-devel mailing list
cobbler-devel(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler-devel