Browse Source

Correct notification driver

The notification driver setup was resulting in the driver and connection string
on the same line. This is caused by the case statement and how jinja formats
the template when a case statement is present. This change modifies how the
driver string is created using a ternary, which will eliminate the case
statement and render the value of the diver correctly.

Change-Id: I1c0296886a7cc37089233f241f79c92696ebac3a
Signed-off-by: Kevin Carter <kevin.carter@rackspace.com>
Kevin Carter 2 months ago
parent
commit
33b192bfd9
1 changed files with 1 additions and 1 deletions
  1. 1
    1
      templates/magnum.conf.j2

+ 1
- 1
templates/magnum.conf.j2 View File

@@ -75,7 +75,7 @@ region_name = {{ magnum_nova_service_region }}
75 75
 endpoint_type = internalURL
76 76
 
77 77
 [oslo_messaging_notifications]
78
-driver = {% if magnum_ceilometer_enabled %}messagingv2{% else %}noop{% endif %}
78
+driver = {{ (magnum_ceilometer_enabled | bool) | ternary('messagingv2', 'noop') }}
79 79
 transport_url = {{ magnum_oslomsg_notify_transport }}://{% for host in magnum_oslomsg_notify_servers.split(',') %}{{ magnum_oslomsg_notify_userid }}:{{ magnum_oslomsg_notify_password }}@{{ host }}:{{ magnum_oslomsg_notify_port }}{% if not loop.last %},{% else %}/{{ magnum_oslomsg_notify_vhost }}{% if magnum_oslomsg_notify_use_ssl | bool %}?ssl=1{% else %}?ssl=0{% endif %}{% endif %}{% endfor %}
80 80
 
81 81
 [oslo_messaging_rabbit]

Loading…
Cancel
Save