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>
This commit is contained in:
parent
c26da937d0
commit
33b192bfd9
|
@ -75,7 +75,7 @@ region_name = {{ magnum_nova_service_region }}
|
|||
endpoint_type = internalURL
|
||||
|
||||
[oslo_messaging_notifications]
|
||||
driver = {% if magnum_ceilometer_enabled %}messagingv2{% else %}noop{% endif %}
|
||||
driver = {{ (magnum_ceilometer_enabled | bool) | ternary('messagingv2', 'noop') }}
|
||||
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 %}
|
||||
|
||||
[oslo_messaging_rabbit]
|
||||
|
|
Loading…
Reference in New Issue