Pablo Iranzo Gómez wrote:
Hi all
Attached is a second patch which joins previous two patches and
adds another feature:
Parses /var/lib/dhcpd/dhpcd.leases and removes any "host" entry
using OMAPI as previous step to write the new ones, this is done to
ensure that hosts renamed, deleted or previous ones, still exist at
leases, that is... resets the state to cobbler known hosts.
Comments are still welcome :)
Regards!
Pablo
PD: Thist patch will get into ticket as previous
------------------------------------------------------------------------
_______________________________________________
et-mgmt-tools mailing list
et-mgmt-tools@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/et-mgmt-tools
Should be applied Thursday or so barring any other comments, and that
will make this easier for people to test. I also need to do a test
release for 0.9 soon (let's call this 0.9.1 ... there will be more test
releases with some other features likely being added prior to the 1.0).
Quick question -- Should omapi in settings be off by default? It only
works with modifications to the dhcp.template to enable it -- though we
/could/ enable that by default in the template and solve the problem.
Comments from folks who use Cobbler for DHCP management?
The main goal of this is to keep DHCP running throughout sync operations
-- but also to allow for less reasons to ever need to do "sync". Since
kickstart generation is now dynamic in 0.9/1.0, the only real reason to
run sync is to rebuild some of the tftpboot tree, the rest of the
"partial" data gets built each time you make a change to the associated
objects (and all descendents automatically update).
We can probably even make that less important as time goes on, by
knowing basic things like if we add a profile, we can also quickly
rebuild the pxemenus (since the number of profiles is going to be very
small, etc).
--Michael
_______________________________________________
et-mgmt-tools mailing list
et-mgmt-tools@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/et-mgmt-tools
