yahoo-eng-team team mailing list archive

[Brian Haley <1864675@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

When a port is provisioned in the dhcp-agent, for example via a
port_create, it will just be added to the dhcp_ready_ports set and sent
to neutron-server in _dhcp_ready_ports_loop() by popping elements off
the list.  So although it was prioritized when it was received, it is
not prioritized when sent to the server to clear the provisioning block.

It seems like these ports should be sent first, then others behind it if
there is still room in the RPC message.  This could just be done with a
second set() perhaps, unless we want to make it more complicated by
using the priority sent from the server to place ports in different
queues.

This should decrease the time it takes to clear the port provisioning
block when an agent is restarted and gets a port_create message, as it
would help even if it was sent with PRIORITY_PORT_CREATE_HIGH to a
single agent, since the one it chose could still be in the middle of a
full sync.

** Affects: neutron
     Importance: Medium
     Assignee: Brian Haley (brian-haley)
         Status: New


** Tags: l3-ipam-dhcp

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

Title:
  DHCP agent should prioritize new ports when sending RPC messages to
  server

Status in neutron:
  New

Bug description:
  When a port is provisioned in the dhcp-agent, for example via a
  port_create, it will just be added to the dhcp_ready_ports set and
  sent to neutron-server in _dhcp_ready_ports_loop() by popping elements
  off the list.  So although it was prioritized when it was received, it
  is not prioritized when sent to the server to clear the provisioning
  block.

  It seems like these ports should be sent first, then others behind it
  if there is still room in the RPC message.  This could just be done
  with a second set() perhaps, unless we want to make it more
  complicated by using the priority sent from the server to place ports
  in different queues.

  This should decrease the time it takes to clear the port provisioning
  block when an agent is restarted and gets a port_create message, as it
  would help even if it was sent with PRIORITY_PORT_CREATE_HIGH to a
  single agent, since the one it chose could still be in the middle of a
  full sync.

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