neutron

  1. Bug #1174591
  2. Comment #4

Comment 4 for bug 1174591

Revision history for this message
Sudhakar Gariganti (sudhakar-gariganti) wrote :

I share the same views as posted above by Miguel. Actually I also was trying to address this issue in the same way and was warned of the negative impacts which could arise with L3 rescheduling based on the agent status.

L3 VRRP Blueprint ( https://blueprints.launchpad.net/openstack/?searchtext=l3-high-availability ) will help address this a bit for the L3 agent case.