yahoo-eng-team team mailing list archive

[mouadino <1191729@xxxxxxxxxxxxxxxxxx>]

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

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

Title:
  Multiple Floating IP Pools feature is broken

Status in OpenStack Neutron (virtual network service):
  Invalid

Bug description:
  Nova networking documentation claim that there is a support for having
  multiple floating ip pools in Grizzly
  (http://docs.openstack.org/grizzly/openstack-
  network/admin/content/adv_cfg_l3_agent_multi_extnet.html) but i
  believe that this feature is totally broken.

  I notice this after configuring my two l3 agents as described in the
  documentation (link above), i wasn't able to associate floating IPs
  with VMs, the quantum commands doesn't fail and no error is logged but
  still no IPs in namespace interface qg-..., no NAT rules, nothing !

  
  And after a bit of digging in the source code, i found that quantum doesn't allow having more than one l3 agent **per host**, and because of the lake of multi-host support in Grizzly, i believe that even thew we can run more than one l3 agent (each associate to it's unique external network), quantum will recognize only one l3 agent, and it get worst because of how status report work (https://github.com/openstack/quantum/blob/stable/grizzly/quantum/db/agents_db.py#L134) this agent will each time hold different information which lead to race condition problem ... .

  I will include a minimal patch soon of how i fixed this, which
  hopefully will give more insight of what wrong.

  Thanks,

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