neutron/neutron/api
Oleg Bondarev 1eb40b49f3 Ensure l3 agent receives notification about added router
Currently router_added (and other) notifications are sent
to agents with an RPC cast() method which does not ensure that
the message is actually delivered to the recipient.
If the message is lost (due to instability of messaging system
in some failover scenarios for example) neither server nor agent
will be aware of that and router will be "lost" till next agent
resync. Resync will only happen in case of errors on agent side
or restart.
The fix makes server use call() to notify agents about added routers
thus ensuring no routers will be lost.
This also unifies reschedule_router() method to avoid code duplication
between legacy and dvr agent schedulers.

Closes-Bug: #1482630
Related-Bug #1404743
Change-Id: Id08764ba837d8f47a28649d081a5876797fe369e
(cherry picked from commit 30b121dfa4)
2015-12-03 15:17:50 +03:00
..
rpc Ensure l3 agent receives notification about added router 2015-12-03 15:17:50 +03:00
v2 Use pecan controllers for routing 2015-09-18 06:00:14 -07:00
views Remove the useless vim modelines 2014-06-21 15:07:31 +08:00
__init__.py Rename Quantum to Neutron 2013-07-06 15:02:43 -04:00
api_common.py Python 3: do not compare int and NoneType 2015-08-05 11:24:57 +02:00
extensions.py Use pecan controllers for routing 2015-09-18 06:00:14 -07:00
versions.py Python 3: encode unicode response bodies 2015-08-13 19:13:38 +09:00