neutron

non-polling implementation for L3/forwarding floating ips

Bug #1037246 reported by dan wendlandt
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
neutron
Invalid
Medium
Jiajun Liu

Bug Description

needs same treatment as DHCP server to replace a polling loop with notifications/rpc. Currently L3 polling is entirely via the API though, so even now there's no issues with DB polling.

Revision history for this message
dan wendlandt (danwent) wrote :

this will not be done in Folsom.

anyone is free to try and take it on in Folsom.

Changed in quantum:
importance: Undecided → Medium
Revision history for this message
dan wendlandt (danwent) wrote :

errrr... I meant grizzly

Revision history for this message
Gary Kotton (garyk) wrote :

I think that the following needs to be done:
l3 agent - RPC/notification support
DHCP - polling support (in the event that RPC is not used - a similar solution to the L3 agent using the client is great).

Jiajun Liu (ljjjustin)
Changed in quantum:
assignee: nobody → ljjjustin (ljjjustin)
Revision history for this message
dan wendlandt (danwent) wrote :

just to be clear, this changeset will not be merged for Folsom. We'll be able to merge it into master for grizzly once the Folsom RC is branch on Sept. 10th.

Thierry Carrez (ttx)
Changed in quantum:
status: New → Confirmed
Revision history for this message
dan wendlandt (danwent) wrote :

this is now being tracked by a blueprint that is under review: https://blueprints.launchpad.net/quantum/+spec/rpc-for-l3-agent

Changed in quantum:
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.