From: Marcin Siodelski Date: Thu, 10 May 2018 11:32:12 +0000 (+0200) Subject: [5478] Added section about sending lease updates setting. X-Git-Tag: trac5549a_base~34^2~3 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=729cbe046946eeec0ce8e3ca69ea37efc46f5c71;p=thirdparty%2Fkea.git [5478] Added section about sending lease updates setting. --- diff --git a/doc/guide/hooks-ha.xml b/doc/guide/hooks-ha.xml index 5c37ac548a..5824573068 100644 --- a/doc/guide/hooks-ha.xml +++ b/doc/guide/hooks-ha.xml @@ -820,6 +820,72 @@ hot standby and load balancing mode of operation. +
+ Controlling Lease Updates + The HA enabled server informs its active partner about allocated + or renewed leases by sending appropriate control commands. The partner + updates the lease information in its own database. This guarantees + consistency of the lease information between the servers and allows for + designating one of the servers to handle the entire DHCP traffic in + case the other server becomes unavailable. + + In some cases, though, it is desired to disable lease updates + between the active servers if the exchange of information about the + allocated leases is performed using some other mechanism. Kea supports + various types of databases to be used as a storage for leases, e.g. + MySQL, Postgres, Cassandra. Those databases include builtin solutions + for data replication which are often used by Kea users to provide + redundancy. + + The HA hook library supports such scenarios by allowing to + disable lease updates over the control channel, leaving the server + to rely on the database replication mechanism. This is controlled by + the send-lease-updates boolean parameter, which + value defaults to true: + + +{ +"Dhcp4": { + + ... + + "hooks-libraries": [ + { + "library": "/usr/lib/hooks/libdhcp_lease_cmds.so", + "parameters": { } + }, + { + "library": "/usr/lib/hooks/libdhcp_ha.so", + "parameters": { + "high-availability": [ { + "this-server-name": "server1", + "mode": "load-balancing", + "send-lease-updates": false, + "peers": [ + { + "name": "server1", + "url": "http://192.168.56.33:8080/", + "role": "primary" + }, + { + "name": "server2", + "url": "http://192.168.56.66:8080/", + "role": "secondary" + } + ] + } ] + } + } + ], + + ... + +} + + + +
+
Control Agent Configuration The describes in detail the