When using the xxx.conf.ona files as configuration files for ISC-DHCP and BIND daemons, they are currently updated e.g. every 15 mins through a cron script (see Link).
I'm currently using ICROND to automatically reload DHCP and BIND daemons when changes in the xxxx.conf.ona happen, but the updating of these two files from the ONA database backend still needs to be done either manually via the build_bind and build_dhcpd scripts or via the CRON entries.
What would be very convenient is a feature which updates these files automatically after data has been updated in the GUI Interface of ONA. This would reduce the wait time for getting the changes into the daemons from 15mins in worst case to zero. Reducing the cron job time interval to very low values as an alternative is increasing the load of reloading/restarting the daemons on the system and may affect the availability of the services as well. So this is not an option.
When using the xxx.conf.ona files as configuration files for ISC-DHCP and BIND daemons, they are currently updated e.g. every 15 mins through a cron script (see Link).
I'm currently using ICROND to automatically reload DHCP and BIND daemons when changes in the xxxx.conf.ona happen, but the updating of these two files from the ONA database backend still needs to be done either manually via the build_bind and build_dhcpd scripts or via the CRON entries.
What would be very convenient is a feature which updates these files automatically after data has been updated in the GUI Interface of ONA. This would reduce the wait time for getting the changes into the daemons from 15mins in worst case to zero. Reducing the cron job time interval to very low values as an alternative is increasing the load of reloading/restarting the daemons on the system and may affect the availability of the services as well. So this is not an option.