yahoo-eng-team team mailing list archive

[Harald Jensås <harald.jensas@xxxxxxxxx>]

Public bug reported:

When using Neutron Segments we would like dhcp agent to configure DHCP
servers to serve clients on remote(non-local) subnets. The remote(non-
local) subnet will need to have a DHCP-relay/forwarder configured. The
relay agent will run on ToR switch or router in the routed underlay
network and would be configured by the operator, it does not need to be
managed by neutron.

Currently the Neutron Segments implementation expect a DHCP agent to be
available on all segments, and thus non-local subnets are filtered in
dhcp_rpc to return only subnets local to the agent.

To support DHCP relay we need to return all subnets and inform the DHCP
agent wich subnets are local vs non-local so that the DHCP agent will
only bind port/ip-address to the subnets that is local.

Implementation of the dhpc_rpc part of this has been started with these reviews:
  https://review.openstack.org/#/c/459861/
  https://review.openstack.org/#/c/438171/
  https://review.openstack.org/#/c/462209
  

The discussion in comment 10 of this bug 1668145 is relevant:
  https://bugs.launchpad.net/neutron/+bug/1668145/comments/10

** Affects: neutron
     Importance: Undecided
         Status: In Progress


** Tags: l3-ipam-dhcp

** Changed in: neutron
       Status: New => In Progress

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

Title:
  [RFE] Neutron Segments DHCP-relay support

Status in neutron:
  In Progress

Bug description:
  When using Neutron Segments we would like dhcp agent to configure DHCP
  servers to serve clients on remote(non-local) subnets. The remote(non-
  local) subnet will need to have a DHCP-relay/forwarder configured. The
  relay agent will run on ToR switch or router in the routed underlay
  network and would be configured by the operator, it does not need to
  be managed by neutron.

  Currently the Neutron Segments implementation expect a DHCP agent to
  be available on all segments, and thus non-local subnets are filtered
  in dhcp_rpc to return only subnets local to the agent.

  To support DHCP relay we need to return all subnets and inform the
  DHCP agent wich subnets are local vs non-local so that the DHCP agent
  will only bind port/ip-address to the subnets that is local.

  Implementation of the dhpc_rpc part of this has been started with these reviews:
    https://review.openstack.org/#/c/459861/
    https://review.openstack.org/#/c/438171/
    https://review.openstack.org/#/c/462209
    

  The discussion in comment 10 of this bug 1668145 is relevant:
    https://bugs.launchpad.net/neutron/+bug/1668145/comments/10

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