venkata anil 500b255278 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		2017-06-06 13:46:54 +03:00
..
rpc	Set HA network port to DOWN when l3 agent starts	2017-06-06 13:46:54 +03:00
v2	api: work around Routes cutting off suffix from resource id	2017-06-01 14:13:39 -07:00
views	Add a new configuration variable for api links.	2017-04-18 15:16:41 +00:00
__init__.py	Added API extensions to detect sorting/pagination features	2016-08-01 22:57:15 +02:00
api_common.py	Add a new configuration variable for api links.	2017-04-18 15:16:41 +00:00
extensions.py	Replace six.iteritems with dict.items(Part-2)	2017-04-18 18:56:46 +08:00
versions.py	Pecan: Get loaded by paste deploy	2017-02-17 14:54:27 -06:00