Workaround for Tacker in HA scenarios

JIRA: -

For Tacker service in HA mode, it only generates VIM fernet key on
one of the Tacker hosts. This may cause error when a request is
been routed to another host. We need to use Barbican and Mistral
components. But now OSA did not support Mistral yet. So we add
a workaround here to get over this issue.

Change-Id: I9aa228ec2ac7011cedb1eb503611ca24c7666caa
Signed-off-by: Yifei Xue <xueyifei@huawei.com>
(cherry picked from commit d7156c0b772ada65ff3d094bd70814bf5b0cb4e7)

diff --git a/plugins/odl_sfc/roles/setup-odl-sfc/tasks/control-tacker-1.yml b/plugins/odl_sfc/roles/setup-odl-sfc/tasks/control-tacker-1.yml
index 8fd1109..f63edea 100644 (file)
--- a/plugins/odl_sfc/roles/setup-odl-sfc/tasks/control-tacker-1.yml
+++ b/plugins/odl_sfc/roles/setup-odl-sfc/tasks/control-tacker-1.yml
@@ -5,3 +5,9 @@
     name: networking-sfc
     virtualenv: /openstack/venvs/tacker-{{ os_ver }}
   when: odl_sfc == "Enable"
+
+- name: stop the other two tacker servers
+  service:
+    name: tacker-server
+    state: stopped
+  when: inventory_hostname != groups['tacker_all'][0]