yahoo-eng-team team mailing list archive

[Salvatore Orlando <1317654@xxxxxxxxxxxxxxxxxx>]

It should also be considered that a DHCP request initiated by the host
in most cases is the only way for reconfiguring the host upon IP, DNS or
static route changes.

At least from the neutron perspective, while 120 seconds is probably too little, 24 hours would probably be unpractical.
I think 10 minutes might be a reasonable default lease time for neutron; DHCP traffic would be a fifth of what it is today, and host reconfiguration upon IP changes would take no more than 10 minutes.

** Also affects: neutron
   Importance: Undecided
       Status: New

** Changed in: neutron
   Importance: Undecided => Low

** Changed in: neutron
   Importance: Low => Medium

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1317654

Title:
  default dhcp lease time of 120s is too short

Status in OpenStack Neutron (virtual network service):
  New
Status in OpenStack Compute (Nova):
  New

Bug description:
  The default dhcp lease time is fairly short (120s). Is this simply a
  hold-over from the time before force_dhcp_release was the default and
  dhcp_release was expected throughout or is there another reason for
  the default to be so brief?

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1317654/+subscriptions