DDI orchestrator synchronizes all data between the Kea DHCP servers and its database regularly. The default synchronization interval is 15 minutes.
Synchronization occurs based on the configuration to update the database and the Web Application. To prevent overwriting external changes before synchronization is complete, DDI orchestrator checks for conflicts with the Kea server’s in-memory configuration before writing changes to the server.
Example:
If a scope with subnet 1.3.3.0/29 is manually added to the Kea DHCP server's
configuration file, and config-reload is successfully called, the Kea
server will have parsed the change and added the scope to its in-memory data structure.
Synchronization with DDI orchestrator may not have been executed
yet, and the externally-added scope is not visible in DDI orchestrator.
If another user tries to add the same or an otherwise conflicting scope through DDI orchestrator, they receive a message stating that “A scope with address “1.3.3.0” already exists on the server”, because the configuration file is validated against the Kea DHCP server's in-memory configuration before each change is applied.