openstack
/
charm-designate
Code Issues Proposed changes

reintroduce designate_notifications topic 

Change I709a6aca1843918a67d43bc4808a0013168fbc55, commit hash
1879b16ea5 introduced a
backwards-incompatible change in the fact that designate stopped
consuming messages using designate_notifications topic from nova and
neutron.

While designate.conf change in the mentioned commit is needed to make
sure Designate emits its own notifications on the topic that ceilometer
uses ("notifications"), for nova and neutron to designate notifications
a separate topic should be used as before.

A revert of the previous commit is not done as it addresses the previous
issue but introduces a new one.

Change-Id: I6b5fd1b5f9bae1cd4a1683fd476b456e81d6c79e
Related-Bug: #1710831
This commit is contained in:
Dmitrii Shcherbakov 2018-02-05 14:22:54 +03:00
parent 94f8c6e0a5
commit 269ba2bb1d
2 changed files with 2 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
src/templates/mitaka/nova_sink.cfg
View File

@ -1,6 +1,7 @@
{% if options.nova_domain_id %}
[handler:nova_fixed]
zone_id = {{ options.nova_domain_id }}
notification_topics = 'notifications_designate'
control_exchange = 'nova'
format = '{{ options.nova_record_format }}'
{% endif %}

1
src/templates/newton/nova_sink.cfg
View File

@ -1,6 +1,7 @@
{% if options.nova_domain_id %}
[handler:nova_fixed]
zone_id = {{ options.nova_domain_id }}
notification_topics = 'notifications_designate'
control_exchange = 'nova'
formatv4 = '{{ options.nova_record_format }}'
formatv6 = '{{ options.nova_record_formatv6 }}'