Update Octavia parameters in tcp-qa env contexts
- Enable Octavia HA for several MCP deployment configs
- For 2.8 configs with Octavia HA enable ACTIVE_STANDBY
topology (for 2019.2.7 this parameter is not yet available)
- Enable spare_amphora_pool_size for some configs
Change-Id: I4dfafca04d3cb5525434906da518592b5a82dd6d
Related-Prod:#PROD-00000
diff --git a/tcp_tests/templates/bm-cicd-queens-ovs-maas/salt-context-cookiecutter-openstack_ovs.yaml b/tcp_tests/templates/bm-cicd-queens-ovs-maas/salt-context-cookiecutter-openstack_ovs.yaml
index b253972..b4d818d 100644
--- a/tcp_tests/templates/bm-cicd-queens-ovs-maas/salt-context-cookiecutter-openstack_ovs.yaml
+++ b/tcp_tests/templates/bm-cicd-queens-ovs-maas/salt-context-cookiecutter-openstack_ovs.yaml
@@ -854,7 +854,9 @@
octavia_health_manager_node01_address: 192.168.1.10
octavia_health_manager_node02_address: 192.168.1.11
octavia_health_manager_node03_address: 192.168.1.12
- octavia_manager_cluster: 'False'
+ octavia_manager_cluster: 'True'
+ octavia_loadbalancer_topology: 'ACTIVE_STANDBY'
+ spare_amphora_pool_size: 1
octavia_hm_bind_ip: 192.168.1.12
octavia_lb_mgmt_cidr: 192.168.1.0/24
octavia_lb_mgmt_allocation_pool_start: 192.168.1.2