summaryrefslogtreecommitdiffstats
path: root/mcp/reclass/classes/cluster/mcp-ovn-ha/openstack
diff options
context:
space:
mode:
authorAlexandru Avadanii <Alexandru.Avadanii@enea.com>2018-09-09 08:54:17 +0200
committerAlexandru Avadanii <Alexandru.Avadanii@enea.com>2018-09-09 09:02:02 +0200
commit36169a124d25dd77b7525cd5223525db4342c208 (patch)
treef75ade02b6748bd3bdcf0337b100e568e7d7ce26 /mcp/reclass/classes/cluster/mcp-ovn-ha/openstack
parentf33444e6792aaf617ea0bad5ee96b30d764a997b (diff)
[ovn-ha] ctl: neutron: Add msg cluster pillar
`system.neutron.control.cluster`, unlike `system.neutron.control.openvswitch.cluster` does not provide neutron:server:message_queue:members pillar data, letting it default to the wrong values (single rabbit instance on the same node). This led to neutron.conf on ctl nodes using: `transport_url=rabbit://openstack:***@172.16.10.35:5672//openstack` instead of `transport_url=rabbit://openstack:***@172.16.10.28:5672,...//openstack` Change-Id: Iad4b709d555b2bafafeb75fdecb831f7d4f5a504 Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
Diffstat (limited to 'mcp/reclass/classes/cluster/mcp-ovn-ha/openstack')
-rw-r--r--mcp/reclass/classes/cluster/mcp-ovn-ha/openstack/control.yml9
1 files changed, 9 insertions, 0 deletions
diff --git a/mcp/reclass/classes/cluster/mcp-ovn-ha/openstack/control.yml b/mcp/reclass/classes/cluster/mcp-ovn-ha/openstack/control.yml
index 795a7d892..64c16f031 100644
--- a/mcp/reclass/classes/cluster/mcp-ovn-ha/openstack/control.yml
+++ b/mcp/reclass/classes/cluster/mcp-ovn-ha/openstack/control.yml
@@ -33,8 +33,17 @@ parameters:
mechanism:
ovn:
driver: ovn
+ compute:
+ region: ${_param:openstack_region}
database:
host: ${_param:opnfv_openstack_database_address}
+ identity:
+ region: ${_param:openstack_region}
+ message_queue:
+ members:
+ - host: ${_param:openstack_message_queue_node01_address}
+ - host: ${_param:openstack_message_queue_node02_address}
+ - host: ${_param:openstack_message_queue_node03_address}
ovn_ctl_opts:
db-nb-create-insecure-remote: 'yes'
db-sb-create-insecure-remote: 'yes'