yahoo-eng-team team mailing list archive

[John Davidge <john.davidge@xxxxxxxxxxxxx>]

Closing this bug in favor of [1], which has been opened to track the
creation of a new deployment scenario to cover this case.

[1] https://bugs.launchpad.net/openstack-manuals/+bug/1662478

** Changed in: openstack-manuals
       Status: Confirmed => Won't Fix

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

Title:
  dhcp should never be enabled for a router external net

Status in neutron:
  Invalid
Status in openstack-manuals:
  Won't Fix

Bug description:
  it doesn't make sense in the existing model, as the router IPs and the
  floating IPs allocated from an external net never make DHCP requests.

  I don't believe there is any significant additional harm caused by
  this though, other than unneeded CPU churn from DHCP agent and
  dnsmasq, and a burned IP address allocated for a DHCP port.

  One tricky issue is that DHCP is enabled by default, so the question
  is whether we should fail if the user does not explicitly disable it
  when creating a network, or if we should just automatically set it to
  False.  Unfortunately, I don't think we can tell the difference
  between a this value default to true and it being explicitly set to
  true, so it seems that if we want to prevent it from being set to true
  in the API, we should require it to be set to False.  We also need to
  prevent it from being set to True on an update.

  Another option would be to ignore the value set in the API and just
  have the DHCP agent ignore networks for which router:external =True.

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