yahoo-eng-team team mailing list archive

[Assaf Muller <amuller@xxxxxxxxxx>]

Public bug reported:

In admin/instances, and project/instances, as well as the instance
details page, IP addresses are retrieved via Nova. However, floating IPs
are configured via Neutron (When Neutron is enabled*). Nova has a
mechanism where it polls Neutron for networking information, but it's
far from real-time.

The effect is that when a floating IP is associated or disassociated, it
isn't reflected in the GUI for up to a minute for a single operation, or
several minutes for consecutive floating IP operations.

There's several approaches to fix this bug:
1) Improve Nova's polling mechanism. It can be faster, but it will never be real time because of its polling nature, and it will never have the desired user experience because of it.
2) Make Neutron send out events when networking changes are made. Nova will listen to these events and update its DB. But do we really want to continue relying on Nova's cached networking information? It seems like a recipe for bugs.
3) My proposed solution: Since Horizon calls out to Neutron directly to configure floating IPs, it should get networking info from Neutron as well.

* This bug only happens with Neutron enabled. With Nova Networking, Nova
takes care to update its own DB when performing floating IP
associations/disassociations as expected.

** Affects: horizon
     Importance: Undecided
     Assignee: Assaf Muller (amuller)
         Status: In Progress

** Changed in: horizon
     Assignee: (unassigned) => Assaf Muller (amuller)

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

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1265032

Title:
  Floating IPs configured via Neutron, viewed via Nova, so floating IP
  info is out of date

Status in OpenStack Dashboard (Horizon):
  In Progress

Bug description:
  In admin/instances, and project/instances, as well as the instance
  details page, IP addresses are retrieved via Nova. However, floating
  IPs are configured via Neutron (When Neutron is enabled*). Nova has a
  mechanism where it polls Neutron for networking information, but it's
  far from real-time.

  The effect is that when a floating IP is associated or disassociated,
  it isn't reflected in the GUI for up to a minute for a single
  operation, or several minutes for consecutive floating IP operations.

  There's several approaches to fix this bug:
  1) Improve Nova's polling mechanism. It can be faster, but it will never be real time because of its polling nature, and it will never have the desired user experience because of it.
  2) Make Neutron send out events when networking changes are made. Nova will listen to these events and update its DB. But do we really want to continue relying on Nova's cached networking information? It seems like a recipe for bugs.
  3) My proposed solution: Since Horizon calls out to Neutron directly to configure floating IPs, it should get networking info from Neutron as well.

  * This bug only happens with Neutron enabled. With Nova Networking,
  Nova takes care to update its own DB when performing floating IP
  associations/disassociations as expected.

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