Feature #748
closed
dhcpd leases
Description
at this time with the smart-proxy
the hosts adress reservations are wrotten to the dhcpd.leases
but it could be better to write them in files included in the dhcpd.conf
we could have to add one line in the dhcpd.conf :
"include foreman.dhcpd.conf"
in the foreman dhcpd.conf :
for each subnet managed sy smart-proxies
"include foreman.$subnet.dhcpd.conf"
and in each foreman.$subnet.dhcpd.conf
- the subnet properties
- all the hosts ip reservations
because the dhcpd.lease can be removed at anytime, and root is the owner of the dhcpd.conf
Updated by Ohad Levy over 13 years ago
- Status changed from New to Closed
that is by design.
the lease file is the actual db that isc dhcpd uses.
it contains many information that is important (such as leases timestamps etc) to the operation of your dhcp service.
the manipulation of the lease file is done via the official isc dhcp api (omshell).
what we probably can improve within foreman, is a way to reconstruct the leases if such a lease is removed.
(and the same for dns and other important services).
this sounds to me like a good discussion to have on the mailing list.
Updated by Arnaud Sourioux over 13 years ago
Yes I see that foreman was using omshell
and today I saw that xCat (IBM cluster management product)
was also working this way
but at this time there are no particular informations in the leases that foreman wrote (timestamps, etc)
another thing is that there are doubles leases when you modify a host ip.
I really would like to thank you (the whole team) again for the job you do :)