venkata anil 90c24e9d26 Set HA network port to DOWN when l3 agent starts ... When l3 agent node is rebooted, if HA network port status is already ACTIVE in DB, agent will get this status from server and then spawn the keepalived (though l2 agent might not have wired the port), resulting in multiple HA masters active at the same time. To fix this, when the L3 agent starts up we can have it explicitly set the port status to DOWN for all of the HA ports on that node. Then we are guaranteed that when they go to ACTIVE it will be because the L2 agent has wired the ports. Closes-bug: #1597461 Change-Id: Ib0c8a71b6ff97e43a414f3db4882914b12170d53 (cherry picked from commit d730b10102)		2017-06-13 12:51:26 +00:00
..
rpc	Set HA network port to DOWN when l3 agent starts	2017-06-13 12:51:26 +00:00
v2	api: work around Routes cutting off suffix from resource id	2017-06-02 08:24:38 -07:00
views	Remove the useless vim modelines	2014-06-21 15:07:31 +08:00
__init__.py	Added API extensions to detect sorting/pagination features	2016-08-01 22:57:15 +02:00
api_common.py	Add filter check for quering	2017-01-18 16:01:28 +00:00
extensions.py	Broken extensions should not show up in the extension list	2016-08-12 18:20:46 +00:00
versions.py	Pecan: Allow unauthenticated version listing	2016-03-11 16:45:28 -08:00