9b809126a2
This patch introduces two new options for dnsmasq in neutron-dhcp-agent: * dhcp_renewal_time (T1): This option specifies the time interval from address assignment until the client transitions to the RENEWING state. * dhcp_rebinding_time (T2): This option specifies the time interval from address assignment until the client transitions to the REBINDING state. By allowing to set these timers we can configure both the renewal and rebinding times (options 58 and 59 as per RFC2132) and, for example allow to change some parameters (like MTU) on instances without having to wait or the lease time. The advantage of changing T1 over the lease time is that if the DHCP server becomes unreachable within the lease time, instances won't drop their IP addresses and won't cause a dataplane disruption. Change-Id: I29d417d459e92f36c1077962b92fa4c43dfaa97d Signed-off-by: Daniel Alvarez <dalvarez@redhat.com>
12 lines
559 B
YAML
12 lines
559 B
YAML
---
|
|
features:
|
|
- |
|
|
Allow configuration of DHCP renewal (T1) and rebinding (T2) timers in
|
|
``neutron-dhcp-agent``. By allowing these timers to be set (options 58
|
|
and 59 as per RFC2132) in ``dnsmasq`` it allows users to change
|
|
other parameters, like MTU, on instances without having to wait for
|
|
the lease time to expire. The advantage of changing T1 over the
|
|
lease time is that if the DHCP server becomes unreachable within
|
|
the lease time, instances will not drop their IP addresses and it
|
|
will not cause a dataplane disruption.
|