yahoo-eng-team team mailing list archive

[Mohammad Banikazemi <mb@xxxxxxxxxx>]

Public bug reported:

Here is how to reproduce the problem:

On a multi-node OpenStack instance with standard (legacy) l3 and no dvr:


Create a new tenant 
Create a network/subnet, and a router for the tenant
Connect the network to the router (with the external network set as the gateway as well)
Create a VM on the network and assign a floating ip to it
Ping the floating IP until the ping it successful
Time the process in step 2


Repeat the above step 2. As the number of tenants/networks/routers increases (to several hundreds) so does the time it takes for step 2 to complete.

Note that the test does not stress the messaging layer as each iteration
of step 2 is executed after the previous iteration has resulted in an
operational router and floating IP.

The breakdown of various l3 operations (which seem to contribute to the
above) show the possible bugs reported here:

https://bugs.launchpad.net/neutron/+bug/1494958
https://bugs.launchpad.net/neutron/+bug/1494959
https://bugs.launchpad.net/neutron/+bug/1494961
https://bugs.launchpad.net/neutron/+bug/1494963

** Affects: neutron
     Importance: Undecided
         Status: New

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

Title:
  Increase in time when a floating IP becomes operational

Status in neutron:
  New

Bug description:
  Here is how to reproduce the problem:

  On a multi-node OpenStack instance with standard (legacy) l3 and no
  dvr:

  
  Create a new tenant 
  Create a network/subnet, and a router for the tenant
  Connect the network to the router (with the external network set as the gateway as well)
  Create a VM on the network and assign a floating ip to it
  Ping the floating IP until the ping it successful
  Time the process in step 2

  
  Repeat the above step 2. As the number of tenants/networks/routers increases (to several hundreds) so does the time it takes for step 2 to complete.

  Note that the test does not stress the messaging layer as each
  iteration of step 2 is executed after the previous iteration has
  resulted in an operational router and floating IP.

  The breakdown of various l3 operations (which seem to contribute to
  the above) show the possible bugs reported here:

  https://bugs.launchpad.net/neutron/+bug/1494958
  https://bugs.launchpad.net/neutron/+bug/1494959
  https://bugs.launchpad.net/neutron/+bug/1494961
  https://bugs.launchpad.net/neutron/+bug/1494963

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